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

NVDA reads wrong item number on submenus #345

Closed
nvaccessAuto opened this issue Jan 1, 2010 · 3 comments
Closed

NVDA reads wrong item number on submenus #345

nvaccessAuto opened this issue Jan 1, 2010 · 3 comments
Labels
Milestone

Comments

@nvaccessAuto
Copy link

Reported by katsutoshi on 2009-07-02 08:26
When I read submenu items with up or down cursor keys, NVDA reads wrong item number.

How to reproduce

  • Press Nvda+N to open NVDA menu
  • Press down arrow 4 times to go to Revert to saved configuration(NVDA says "revert to saved configuration 5 of 8")
  • Press down arrow two more times to go to Exit (NVDA says "Exit 8 of 8")

There are 6 items available on this NVDA menu but, NVDA counts there are 8 items.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2009-07-02 12:19
The item count is obtained by counting the items in the container. This includes separators, which are not accessible via the keyboard but are indeed present. For example, in the NVDA menu, there is a separator between "Save configuration" and "Exit". You can see this using object navigation.

The only fix is to not include item counts at all for standard Windows menus, as counting items manually and skipping separators is far too slow. However, some may prefer an item count including separators as opposed to no item count at all.

We need to make a final policy decision on this and either remove the item counts for menus or close this as wontfix.
Changes:
Milestone changed from 0.6 to None

@nvaccessAuto
Copy link
Author

Comment 2 by mdcurran on 2011-06-24 04:08
NVDA now no longer reads item counts for places where it has to guess (such as menus) by default. However the possibly incorrect counting can be turned back on with a settings preference. Closing as fixed as for default installs the incorrect numbers are no longer announced.
Changes:
State: closed

@nvaccessAuto
Copy link
Author

Comment 3 by jteh on 2011-06-28 02:10
Changes:
Milestone changed from None to 2011.1

@nvaccessAuto nvaccessAuto added this to the 2011.1 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant