WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: testing with JAWS and NVDA

for

From: Bryan Garaventa
Date: Apr 11, 2013 8:55AM

I'm sorry, I have to disagree.

Strict adherence to a particular standard cannot be used as an excuse for a
feature that is not accessible to screen reader users. I have a complex
example of this that I'll be sharing on Monday.

JAWS is the foremost screen reader as reported by the WebAim survey,
followed by NVDA, and deliberately not making something accessible when it's
known not to work in one or the other cuts out a significant percentage of
the market.

Regarding the link issue, that sounds like a role mapping issue relating to
an incorrect usage of ARIA, which I have seen before. This is actually quite
easy to correct.

Please share the page or code and it will be much clearer.

----- Original Message -----
From: "Karlen Communications" < <EMAIL REMOVED> >
To: "'WebAIM Discussion List'" < <EMAIL REMOVED> >
Sent: Thursday, April 11, 2013 3:33 AM
Subject: Re: [WebAIM] testing with JAWS and NVDA


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