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

Confusing/not adequate verbosity in ARIA-enabled menus #773

Closed
nvaccessAuto opened this issue Jul 21, 2010 · 3 comments
Closed

Confusing/not adequate verbosity in ARIA-enabled menus #773

nvaccessAuto opened this issue Jul 21, 2010 · 3 comments

Comments

@nvaccessAuto
Copy link

Reported by kennpetri on 2010-07-21 20:40
When navigating ARIA-enabled menu widgets, NVDA properly announces that the cursor is on a menu and properly announces the number of menu items and position within the bar. When enter is pressed to enter the sub-menu/menu items, NVDA announces "menu [of numbers" but in navigating via arrow key does not announce the name of the menu item. That is, we hear "2 of 3" but not the actual name of/label for the menu item itself. Also, occasionally, NVDA pulls in extraneous information. For example, that the sub-menu was implemented in a "table."

By contrast, JAWS 11 verbosity is more helpful. When entering the menu bar, JAWS says "Menu bar. To navigate, press right/down and left/up arrow keys." JAWS also accurately reads the menu item labels/names and uses an audio tone to indicate the user is "in" the menu.

Note: testing done using Firefox 3.6

Please see http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/test_Menu.html for a model implementation.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2010-07-21 23:53
We're getting very broken information from Firefox here for some reason. I've definitely seen ARIA menu implementations that work fine with NVDA, but this one is misbehaving quite badly indeed. I'll need to debug this further. Among other things, Firefox is throwing exceptions when we query for the name and attributes of the menu items, which is very bad. Note that NVDA uses a different API to query Firefox than does JAWS, which perhaps explains the different behaviour. In any case, I'll debug this more when I get some time and file bugs against Firefox if appropriate.

@LeonarddeR
Copy link
Collaborator

I'm not sure whether I can still reproduce this. Many things have been changed since this was reported 7 years ago.

@derekriemer
Copy link
Collaborator

Closing as worksfome, because it seems that this is fixed after all these years. Please reopen if it isn't so.

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

No branches or pull requests

4 participants