WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Screen reader accessible automated accessibility testing tools

for

From: Birkir R. Gunnarsson
Date: Jul 2, 2024 12:06PM

With Axe I use the inspect button on the individual issue to open the DOM
tree on the node where the issue occurs. It does a very good job with that.
Then I copy the code into Notepad for inspection and/or mess with it
directly in the dev tools to see if I can introduce the fix on the fly, but
that's more into how screen reader users debug accessibility more so than
how accessible different accessibility testing tools are.


On Tue, Jul 2, 2024 at 1:30 PM Steve Green < <EMAIL REMOVED> >
wrote:

> Thanks, Birkir,
>
> Once you have found an issue with Axe, presumably you want to see that
> part of the code in the DOM Inspector. There is a link to do that, but how
> do you work out what part of the code you are in if you are working on a
> website you are not familiar with? It's easy for sighted people to quickly
> look at the previous and subsequent elements, but I imagine that must be
> more difficult for screen reader users, especially when each element has
> lots of attributes that may or may not be relevant and your element is
> nested inside a dozen or more div elements that don't do anything. Do you
> need Braille for that too? On badly coded websites it can take me a long
> time to work out what a line of code is doing, so I imagine it is even more
> difficult if you can't see it.
>
> Steve
>
>