Open msftedad opened 2 years ago
Similar bug is repro on tablist and filter on https://scc-storybook.azurewebsites.net/?path=%2Fstory%2Ftemplates-workbenchpage--default&viewid=listPage.
This is reproducible in every browser. In general, NvDA seems not to render the number of elements in browse mode at all. in many cases. List items are for example also not counted in browse mode.
If not all elements are in the DOM, you could try using aria setsize atribute to overwrite the item count which is automatically calculated by the browser itself. But in focus mode this codepen seems to work properly, so Aria setsize is not needed in this case because all elements are in the DOM. And even using aria setsize atribute, NVDA will very probably announce the item count only in focus mode, not in browse mode. See this link for more details: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-setsize
@jcsteh just out of curiosity, what was the reason for not considering item position in browse mode when this was implemented?
Steps to reproduce:
Actual behavior:
Command Bar menu bar menu item Add domain menu item Buy domain menu item collapsed Sharing menu item Refresh. In browse mode, NVDA does not announcing position of menu items (Add domain, Buy domain..etc)
Expected behavior:
In browse mode, NVDA should announce position of menu items (Add domain, Buy domain..etc) Ex: It should announce as "Add domain menu item 1 of 6"
System configuration
Code pen: https://codepen.io/testaccount01/pen/jOxLRrz OS build Version: 21H2 (22000.978) Edge: Version 105.0.1343.42 (Official build) (64-bit) Screen reader: NVDA
NVDA installed/portable/running from source:
Installed
NVDA version:
2022.2.3
Windows version:
Win 11
Name and version of other software in use when reproducing the issue:
N/A
Other information about your system:
N/A
Other questions
N/A
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
No
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes