WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: testing with JAWS and NVDA

for

From: Karlen Communications
Date: Apr 11, 2013 4:33AM

We depend on the standards and make sure that the code or tagging is to the
standard. Even with a technology that might read things correctly when you
start a document or web page, the mechanical tool/screen reader or
Text-to-Speech may grow tired and read things incorrectly. We can't define
accessibility as being AT centric and we can't fail digital content if there
is a glitch or bug in the AT. This would mean testing every page against
every setting and version of both AT and browsers for "compliance."

I use AT and I do use it to test but if the code is right and the AT is
reading it incorrectly, this is not a failure of the coding or tagging or
the accessibility of a document, we need to be able to separate the quirks
of the AT from our testing and what we define is "accessible."

Is the coding or tagging correct for the content?

Cheers, Karen