E-mail List Archives
Thread: Testing screen reader compatibility with browsers.
Number of posts in this thread: 3 (In chronological order)
From: mhysnm1964
Date: Thu, Nov 23 2017 5:59PM
Subject: Testing screen reader compatibility with browsers.
No previous message | Next message →
Team,
Does anyone have or know of a resource for testing screen reader
compatibility against a browser to identify bugs with the Assistive Tech? I
am just starting my research into this area and have found some resources
from PowerMapper, but wonder if there was a GIT depositary out there that I
could clone which could be used to isolate Screen reader problems from
accessibility faults with a browser or the design of the page.
I hope the above makes sense.
Sean
Sean
From: Patrick H. Lauke
Date: Fri, Nov 24 2017 9:35AM
Subject: Re: Testing screen reader compatibility with browsers.
← Previous message | Next message →
On 24/11/2017 00:59, = EMAIL ADDRESS REMOVED = wrote:
> Team,
>
> Does anyone have or know of a resource for testing screen reader
> compatibility against a browser to identify bugs with the Assistive Tech? I
> am just starting my research into this area and have found some resources
> from PowerMapper, but wonder if there was a GIT depositary out there that I
> could clone which could be used to isolate Screen reader problems from
> accessibility faults with a browser or the design of the page.
One step necessary to check if something's a browser or AT issue is to
use a tool that shows you what the browser is actually exposing via the
accessibility API. On Windows for instance, you could use things like
Inspect
https://msdn.microsoft.com/en-us/library/windows/desktop/dd318521%28v=vs.85%29.aspx?f%5&MSPPError=-2147217396
or aViewer https://developer.paciellogroup.com/resources/aviewer/
(disclosure: I work for TPG)
This gives you an insight into whether or not a browser is exposing
stuff correctly or not. When just testing browser+AT combinations, one
of the problems is that you'll get AT also using heuristics and
error-correcting if browsers aren't exposing the correct stuff, so it
won't help you easily identify if a discrepancy of how one AT works with
a browser compared to another AT is a sign of the AT having issues, or
if it's the browser not exposing correct stuff and then ATs simply
having different heuristics to cope with that situation.
P
--
Patrick H. Lauke
www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke
From: mhysnm1964
Date: Fri, Nov 24 2017 7:15PM
Subject: Re: Testing screen reader compatibility with browsers.
← Previous message | No next message
Patrick,
Thanks, that was one of the items on my test list to include. I am using Inspect and accessibility probe as I find Aview does not work well with screen readers. I also found the ARIA Git pattern from w3c which could be a starting point.