Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tooltip text not read in Office ribbon sub-menu items #6743

Open
Qchristensen opened this issue Jan 17, 2017 · 5 comments
Open

Tooltip text not read in Office ribbon sub-menu items #6743

Qchristensen opened this issue Jan 17, 2017 · 5 comments

Comments

@Qchristensen
Copy link
Member

When navigating sub-menu items in Office (2016 at least), tool tip information is only available by moving the mouse to the current navigator object (or physically). The only way to have NVDA read the information is then to physically move the mouse over the tooltip.

To reproduce:
Open Excel (Word has several examples of this, but Excel has more)
Press alt+m to open the formula ribbon
Open any of the sub-menus, I pressed E to open "time and date"
Down arrow through the items. NVDA reads the function names but no tooltip appears.
Press NVDA+numpad Divide (laptop: NVDA+SHIFT+M) to move the mouse to the current item (I was on "DAYS".
Physically move the mouse slightly down and to the right to have NVDA read the tooltip.
Press NVDA+numpad Multiply to navigate to the object under the mouse.

I then captured the following with NVDA+F1:

"nput: kb(desktop):NVDA+numpadMultiply
IO - speech.speak (14:24:13):
Speaking [LangChangeCommand ('en'), u'Move navigator object to mouse']
IO - speech.speak (14:24:13):
Speaking [LangChangeCommand ('en'), u'Returns the number of days between the two dates. text read only']
IO - inputCore.InputManager.executeGesture (14:24:15):
Input: kb(desktop):NVDA+f1
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (14:24:15):
Developer info for navigator object:
name: u'Returns the number of days between the two dates.'
role: ROLE_STATICTEXT
states: STATE_READONLY
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.IAccessible.IAccessible object at 0x04D25470>
Python class mro: (<class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: None
location: (543, 593, 424, 74)
value: None
appModule: <'appModuleHandler' (appName u'excel', process ID 10116) at address 4e68210>
appModule.productName: u'Microsoft Office 2016'
appModule.productVersion: u'16.0.7571.2109'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 591614
windowClassName: u'NetUIHWND'
windowControlID: 0
windowStyle: 1442840576
windowThreadID: 12180
windowText: u''
displayText: u'Returns the number of days date)between the two dates.ber in '
IAccessibleObject: <POINTER(IAccessible) ptr=0x72db98 at 50b4cb0>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=591614, objectID=None, childID=0
IAccessible accName: u'Returns the number of days between the two dates.'
IAccessible accRole: ROLE_SYSTEM_STATICTEXT
IAccessible accState: STATE_SYSTEM_READONLY, STATE_SYSTEM_VALID (64)
IAccessible accDescription: None
IAccessible accValue: None"

@Adriani90
Copy link
Collaborator

@Qchristensen the tooltipps seem to be reported properly now. Could you please test with NVDA 2019.1 please?
I have tested just now in Office 2016 and 365 and I can not reproduce this issue.

@Adriani90
Copy link
Collaborator

In Office 2010 NVDA 2019.1 reports them also properly.

@Qchristensen
Copy link
Member Author

In my example, the date and time formulas, the first one is DATE. NVDA Reads:
DATE (Year, month, day)

If you hover the mouse over it however, it displays that text in bold in a tooltip. In the same tooltip, it also says:
Returns the number that represents the date in Microsoft Excel date-time code.

@Adriani90
Copy link
Collaborator

Adriani90 commented May 18, 2019

Ok when testing this in Excel 365 I don't get the information mentioned by Quentin. So it seems this issue is still reproducible.

@LeonarddeR
Copy link
Collaborator

I wonder whether #8124 is somehow related to this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants