E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 13 (In chronological order)

From: Steve Green
Date: Tue, Jul 02 2024 10:21AM
Subject: Screen reader accessible automated accessibility testing tools
No previous message | Next message →

A screen reader user with reasonable coding knowledge just asked me if I could recommend an automated accessibility testing tool that he would be able to use. He didn't say if he was looking for something simple like a browser extension or something more comprehensive like SortSite, but I think he would be grateful for anything that can help him. Can anyone suggest anything?

Regards,
Steve Green
Managing Director
Test Partners Ltd
020 3002 4176 (direct)
0800 612 2780 (switchboard)
07957 246 276 (mobile)
020 7692 5517 (fax)
Skype: testpartners
= EMAIL ADDRESS REMOVED =
www.testpartners.co.uk
 
Connect to me on LinkedIn - http://uk.linkedin.com/in/stevegreen2

From: Birkir R. Gunnarsson
Date: Tue, Jul 02 2024 10:35AM
Subject: Re: Screen reader accessible automated accessibility testing tools
← Previous message | Next message →

Most of the browser add-ons are pretty accessible.
* Axe, just press ctrl-sift-i to go to developer tools, find the tab,
activate it, run the scan, then navigate by headings to explore results.
* ARC (last time I tested), same thing as I recall
* Wave - the icons have alt text so you don't even have to go to developer
tools necessarily
* Evinced - I don't remember the details, but it's similar, I could use it
without much trouble

These re the ones I can recall of the top of my head.
As for CICD type tools, those are trickier and depend on other factors such
as automation framework, access to command line, I need braille for all
such work, etc.



On Tue, Jul 2, 2024 at 12:21 PM Steve Green < = EMAIL ADDRESS REMOVED = >
wrote:

> A screen reader user with reasonable coding knowledge just asked me if I
> could recommend an automated accessibility testing tool that he would be
> able to use. He didn't say if he was looking for something simple like a
> browser extension or something more comprehensive like SortSite, but I
> think he would be grateful for anything that can help him. Can anyone
> suggest anything?
>
> Regards,
> Steve Green
> Managing Director
> Test Partners Ltd
> 020 3002 4176 (direct)
> 0800 612 2780 (switchboard)
> 07957 246 276 (mobile)
> 020 7692 5517 (fax)
> Skype: testpartners
> = EMAIL ADDRESS REMOVED =
> www.testpartners.co.uk
>
> Connect to me on LinkedIn - http://uk.linkedin.com/in/stevegreen2
>
> > > > >


--
Work hard. Have fun. Make history.

From: Steve Green
Date: Tue, Jul 02 2024 11:30AM
Subject: Re: Screen reader accessible automated accessibilitytesting tools
← Previous message | Next message →

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

From: Jared Smith
Date: Tue, Jul 02 2024 11:30AM
Subject: Re: Screen reader accessible automated accessibility testingtools
← Previous message | Next message →

We believe WAVE to be very accessible to screen reader users. We have documentation to help screen reader users activate WAVE and navigate the interface at https://wave.webaim.org/accessibility If you're not familiar with WAVE, our introduction video provides an overview - https://www.youtube.com/watch?v=ITUDiTgAZY0

Thanks,

Jared Smith
WebAIM

From: Sailesh Panchang
Date: Tue, Jul 02 2024 11:48AM
Subject: Re: Screen reader accessible automated accessibility testing tools
← Previous message | Next message →

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 ADDRESS REMOVED =
Deque Systems Inc | - Accessibility for Good | www.deque.com














On Tue, Jul 2, 2024 at 1:30 PM Steve Green < = EMAIL ADDRESS 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
>
>

From: Dean.Vasile
Date: Tue, Jul 02 2024 12:00PM
Subject: Re: Screen reader accessible automated accessibility testingtools
← Previous message | Next message →

I use wave.
And I have a lot of great success with accessibility insights.
I find that to be an excellent tool to also assist with manual testing it offers codes snippets it has a fast pass. Where can give a quick look to see what it finds wrong with the page.
I have a lot of luck with that one.
Dean Vasile


617-799-1162

> On Jul 2, 2024, at 12:23 PM, Steve Green < = EMAIL ADDRESS REMOVED = > wrote:
>
> A screen reader user with reasonable coding knowledge just asked me if I could recommend an automated accessibility testing tool that he would be able to use. He didn't say if he was looking for something simple like a browser extension or something more comprehensive like SortSite, but I think he would be grateful for anything that can help him. Can anyone suggest anything?
>
> Regards,
> Steve Green
> Managing Director
> Test Partners Ltd
> 020 3002 4176 (direct)
> 0800 612 2780 (switchboard)
> 07957 246 276 (mobile)
> 020 7692 5517 (fax)
> Skype: testpartners
> = EMAIL ADDRESS REMOVED =
> www.testpartners.co.uk
>
> Connect to me on LinkedIn - http://uk.linkedin.com/in/stevegreen2
>
> > > >

From: Birkir R. Gunnarsson
Date: Tue, Jul 02 2024 12:06PM
Subject: Re: Screen reader accessible automated accessibility testing tools
← Previous message | Next message →

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

From: Steve Green
Date: Wed, Jul 03 2024 1:08AM
Subject: Re: Screen reader accessible automated accessibilitytesting tools
← Previous message | Next message →

Thanks, Birkir,

That's really helpful. If you ever do a demo on how screen reader users debug accessibility I would very much like to see it.

Steve

From: shankar shan
Date: Thu, Jul 04 2024 5:12AM
Subject: Re: Screen reader accessible automated accessibility testing tools
← Previous message | Next message →

Hi,
I am a screen reader user and willing to learn the automation for
desktop/standard apps.
and please suggest to me the accessible automation tool for screen reader
users.

On Wed, Jul 3, 2024 at 12:38 PM Steve Green < = EMAIL ADDRESS REMOVED = >
wrote:

> Thanks, Birkir,
>
> That's really helpful. If you ever do a demo on how screen reader users
> debug accessibility I would very much like to see it.
>
> Steve
>
>

From: Dean.Vasile
Date: Thu, Jul 04 2024 5:34AM
Subject: Re: Screen reader accessible automated accessibilitytesting tools
← Previous message | Next message →

Hello
I am also a screen reader user.
I have good luck with
Wave and accessibility insights.
Other people like lighthouse
But I guess it's a little preference you need to play with them in order to become comfortable with them
Dean Vasile


617-799-1162

> On Jul 4, 2024, at 7:13 AM, shankar shan < = EMAIL ADDRESS REMOVED = > wrote:
>
> Hi,
> I am a screen reader user and willing to learn the automation for
> desktop/standard apps.
> and please suggest to me the accessible automation tool for screen reader
> users.
>
>> On Wed, Jul 3, 2024 at 12:38 PM Steve Green < = EMAIL ADDRESS REMOVED = >
>> wrote:
>>
>> Thanks, Birkir,
>>
>> That's really helpful. If you ever do a demo on how screen reader users
>> debug accessibility I would very much like to see it.
>>
>> Steve
>>
>>

From: Akash Kakkar
Date: Thu, Jul 04 2024 2:32PM
Subject: Re: Screen reader accessible automated accessibility testing tools
← Previous message | Next message →

Hi Shanku,

Accessibility Insights is the best thing to go with the desktop apps.

I have good experience with it, please let me know if you need any help.


Best,

Akash

On 7/4/2024 4:42 PM, shankar shan wrote:
> Hi,
> I am a screen reader user and willing to learn the automation for
> desktop/standard apps.
> and please suggest to me the accessible automation tool for screen reader
> users.
>
> On Wed, Jul 3, 2024 at 12:38 PM Steve Green < = EMAIL ADDRESS REMOVED = >
> wrote:
>
>> Thanks, Birkir,
>>
>> That's really helpful. If you ever do a demo on how screen reader users
>> debug accessibility I would very much like to see it.
>>
>> Steve
>>
>>

From: David Engebretson Jr.
Date: Thu, Jul 04 2024 6:13PM
Subject: Re: Screen reader accessible automated accessibilitytesting tools
← Previous message | Next message →

Me too!

From: Kevin Prince
Date: Sun, Jul 07 2024 3:53PM
Subject: Re: Screen reader accessible automated accessibilitytesting tools
← Previous message | No next message

Absolutely.

Kevin Prince
Accessibility Consultant
Access Advisors

Phone: +64212220638
Web: https://accessadvisors.nz/


If you have any access needs why not join our research panel where you can be paid to help improve digital accessibility in New Zealand.
I work flexibly and am sending this message now because it suits my work schedule. However I don't expect that you will read, respond to or action it outside of your regular working hours.