-
-
Notifications
You must be signed in to change notification settings - Fork 618
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
Web Accessibility: ARIA trees not accessible with NVDA and Firefox or Chrome #12012
Comments
I confirm this bug.
Happens here with latest alpha as well on edge, chrome and firefox.
…On 1/27/21, behofer ***@***.***> wrote:
<!-- Please read the text in this edit field before filling it in.
Please thoroughly read NVDA's wiki article on how to fill in this template,
including how to provide the required files.
Issues may be closed if the required information is not present.
https://github.com/nvaccess/nvda/wiki/Github-issue-template-explanation-and-examples
Please also note that the NVDA project has a Citizen and Contributor Code of
Conduct which can be found at
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md. NV Access
expects that all contributors and other community members read and abide by
the rules set out in this document while participating or contributing to
this project. This includes creating or commenting on issues and pull
requests.
-->
### Steps to reproduce:
1. Get ARIA tree code example (W3C recommendation) from W3C official
website: https://www.w3.org/WAI/GL/wiki/Using_ARIA_trees
2. Copy Code Example into a plain HTML file
3. Open the HTML file from step 2 in Chrome or Firefox on Windows 10 with
NVDA screenreader enabled
4. Navigate the tree with NVDA screenreader in browse mode
### Actual behavior:
NVDA will read the first tree element and its children (in the example
"Fruits") properly whereas the following elements (example: "Vegetables")
are not accessible at all/are skipped.
So, only information on the first tree element (Level 1) is passed to a
screenreader.
### Expected behavior:
NVDA should be able to navigate the whole tree with all its elements in
Chrome.
### System configuration
#### NVDA installed/portable/running from source:
installed
#### NVDA version:
2020.3
#### Windows version:
Windows 10 Enterprise - Version 10.0.17763 Build 17763
#### Name and version of other software in use when reproducing the issue:
Firefox 79, Chrome 86
#### Other information about your system:
None
### Other questions
#### Does the issue still occur after restarting your computer?
Yes
#### Have you tried any other versions of NVDA? If so, please report their
behaviour?
No.
#### If addons are disabled, is your problem still occuring?
Yes
#### Did you try to run the COM registry fixing tool in NVDA menu / tools?
Yes
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#12012
|
Could be related to #12350. |
This is reproducible in all browsers, it seems even in focus mode the navigation in the test code is broken. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce:
Actual behavior:
NVDA will read the first tree element and its children (in the example "Fruits") properly whereas the following elements (example: "Vegetables") are not accessible at all/are skipped.
So, only information on the first tree element (Level 1) is passed to a screenreader.
Expected behavior:
NVDA should be able to navigate the whole tree with all its elements in Chrome.
System configuration
NVDA installed/portable/running from source:
installed
NVDA version:
2020.3
Windows version:
Windows 10 Enterprise - Version 10.0.17763 Build 17763
Name and version of other software in use when reproducing the issue:
Firefox 79, Chrome 86
Other information about your system:
None
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviour?
No.
If addons are disabled, is your problem still occuring?
Yes
Did you try to run the COM registry fixing tool in NVDA menu / tools?
Yes
The text was updated successfully, but these errors were encountered: