WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Is Voiceover more similar to NVDA or JAWS with respect to the accessibility tree?

for

From: glen walker
Date: Jun 3, 2020 5:13PM

Yes, Sean, of course the accessibility tree wins. My point was that in
using a screen reader as a testing tool, it's much faster for me to tab
through a dozen form elements and hear "blank" for all of them than it is
for me to inspect the accessibility tree for those same dozen elements and
see if an accessible name exists. But if you use a tool that tries to
compensate for a bad accessibility tree, then that tool is not as useful.


On Wed, Jun 3, 2020 at 4:53 PM Murphy, Sean <
<EMAIL REMOVED> > wrote:

>
> What is in the browser accessibility tree is what should be used as the
> deal breaker. If the name property of the accessibility tree is null, in my
> mind that is a failure regardless of the screen reader from a WCAG point of
> view. As aria-label and similar attributes should be populating this
> property for the assistive technology. This applies to all the different
> accessibility tree properties of importance such as role, value, etc. The
> accessibility tree will populate the accessibility API of the OS. In
> relation to other components like tables, I would still look at the
> accessibility tree first to make sure it is correctly populated.
>
> Sean
>