WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Screen reader accessible automated accessibility testing tools

for

From: Sailesh Panchang
Date: Jul 2, 2024 11:48AM

With axe, there is the source code snippet which may contain some text
that one can find and locate in the browser. The location or selector is
also available for the element in the axe UI.
Yes, if one wants to navigate back through the DOM to identify the parent
container, it does take time and as you say traversing DIVs at times. I do
it regularly ... do not use Braille.
Sailesh Panchang | +1 (571) 344-1765
Technical Solutions Architect

Email: <EMAIL REMOVED>
Deque Systems Inc | - Accessibility for Good | www.deque.com














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
>
>