E-mail List Archives

Re: Testing screen reader compatibility with browsers.


From: Patrick H. Lauke
Date: Nov 24, 2017 9:35AM

On 24/11/2017 00:59, <EMAIL 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
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.

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