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
reporting of menus #4278
Comments
Comment 1 by jteh on 2014-07-13 01:42
|
Comment 3 by blindbhavya on 2014-07-13 05:51 |
@jcsteh (LOL on re-reading 3 years younger me) Since you mentioned that the reported issue is worth investigating again at some stage, could you please assign a priority you deem appropriate? Investigating this deserves a P2 IMHO, but actually attempting to resolve it may be prioritized differently. |
@jcsteh I don't know if it is an ilusion from my side, but when navigating through the menu bar in Firefox 64, NVDA seems to Report the menu item too fast, giving it priority over reporting menu cathegory. When I am navigating from "undo" in "edit" menu to the right, NVDA sometimes reports the first to letters of the view menu but the the menu item interupts the reporting. I don't really know if this is only my Impression. |
@Adriani90: No, that is really what happens. NVDA deliberately interrupts the reporting of the menu when the menu item gets focus. See my comment above for an explanation of why NVDA does this currently. |
Reported by blindbhavya on 2014-07-12 13:43
Lets take an application for example Firefox.
Press Alt and you will reach File menu.
Press down arrow to open the menu and in our application example Firefox the option is New Tab (which is not a submenu).
Press right arrow to go to the first option of the next menu, in our case the next menu is Edit and first option in it is Undo.
So when we pressed right arrow to go to first option of next menu NVDA did not announce which new menu we had entered (in our case Edit).
Therefore I propose that when the user changes menus, the name of the new menu should be announced and then the option inside it.
Blocking #4281
The text was updated successfully, but these errors were encountered: