WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows

for

From: glen walker
Date: Jan 27, 2021 9:32AM

Yes, I was thinking the same thing, Peter, but the example on
https://www.w3.org/TR/wai-aria-practices/examples/treeview/treeview-2/treeview-2a.html
has all three top level tree items in the DOM. The child elements have
display:none. So I expected to be able to navigate to "Vegetables" and
"Grains". They're in the DOM and accessibility tree. But even navigating
character by character (right arrow in NVDA), it only walks through 'F',
'r', 'u', 'i', 't', 's' and then goes to the 'A' in "Accessibility
Features" in the heading following the tree.

On Wed, Jan 27, 2021 at 9:24 AM Peter Krautzberger < <EMAIL REMOVED> >
wrote:

>
> One reason I can think of is that trees might not have all their children
> present in the DOM - e.g., in a cloud storage system, a folder view tree
> might fetch the subdirectory structure asynchronously.
>
> Slightly related: the ARIA Working Group has had a couple of deep-dive
> meetings in recent months about trees, cf.
> https://github.com/w3c/aria/issues/1311
>
> Best regards,
> Peter Krautzberger.
>
>