WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Benjamin.Hofer@telekom.de
Date: Jan 27, 2021 3:52AM

Hi Patrick,
thanks for coming back on this.
> (and just to clarify, when you say "copy the code example in a plain HTML file" ... of course, to actually work, you need more than just the HTML - you need actual JavaScript to implement the whole interaction of a tree view, expose/change the open/closed tree branches, etc ... it's not sufficient to just grab the HTML itself)

Of course, this is not enough to implement the whole tree so that the user can interact with it. It was only for testing if the screenreader is generally able to navigate such a tree; and we found that only the first element is accessible which was also the case with fully implemented trees like in Angular components.
We'll check the link.

Best
Ben


-----Ursprüngliche Nachricht-----
Von: WebAIM-Forum < <EMAIL REMOVED> > Im Auftrag von Patrick H. Lauke
Gesendet: Mittwoch, 27. Januar 2021 11:38
An: <EMAIL REMOVED>
Betreff: Re: [WebAIM] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows

On 27/01/2021 09:33, <EMAIL REMOVED> wrote:
> 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?

That wiki resource seems slightly out of date (still references OAA which has been defunct for ages). I'd recommend reviewing the examples from ARIA Practices https://www.w3.org/TR/wai-aria-practices-1.1/#TreeView

(and just to clarify, when you say "copy the code example in a plain HTML file" ... of course, to actually work, you need more than just the HTML - you need actual JavaScript to implement the whole interaction of a tree view, expose/change the open/closed tree branches, etc ... it's not sufficient to just grab the HTML itself)

P
--
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke