E-mail List Archives
Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows
From: Benjamin.Hofer
Date: Jan 27, 2021 2:33AM
- Next message: Patrick H. Lauke: "Re: Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- Previous message: Jared Smith: "WebAIM Discussion List back online"
- Next message in Thread: Patrick H. Lauke: "Re: Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- Previous message in Thread: None
- View all messages in this Thread
Hello WebAIM Community,
I'm new in this list and hope you can give advice on that specific question.
We've basically implemented an ARIA tree in the way W3C recommends, please see cocde example in this link: https://www.w3.org/WAI/GL/wiki/Using_ARIA_trees
Many samples and templates (e.g. official ones from Angular) are based on these recommendations.
If you copy the code example (see link above) in a plain HTML file and open it with Firefox and Chrome, screenreaders can only access the first tree element (in this example "Fruits") and its child elements. Other elements at the first level are not accessible in the virtual mode of screenreaders.
This was tested using NVDA and JAWS screenreaders as well as Firefox and Chrome browsers.
Is this a known issue? Does t depend on specific product versions (screenreaders, browsers)?
Did anyone manage to solve the problem?
Best,
Benjamin
Benjamin Hofer | Deutsche Telekom
- Next message: Patrick H. Lauke: "Re: Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- Previous message: Jared Smith: "WebAIM Discussion List back online"
- Next message in Thread: Patrick H. Lauke: "Re: Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows"
- Previous message in Thread: None
- View all messages in this Thread