WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Screen reader support

for

From: Dhananjay Bhole
Date: Apr 21, 2020 8:30AM

Hello Kalpeshkumar,

Sorry! I have misinterpreted your quary as I quickly when through the mail text.

I also didn't find any explicit mention in any compliance document
about least number of screen readers support and specific versions.
However Several Digital Accessibility training documents have
recommended to provide support for at least 2 popular screen reader
and browsers combinations. Specially considering your targeted
audience. Whole objective is to provide accessibility to wider range
of users.
If you are providing SR support of at least 1 popular screen reader
in the consideration of the targeted users
and organizational policy, then I think there will not be fear of any
litigation.

I would suggest that instead of considering legal penalty,
organizations should consider that how their products and services can
reach up to large number of users so that they can increase their
customer base and earn more revenue.

Regards




On 4/21/20, Karlen Communications < <EMAIL REMOVED> > wrote:
> We can't make things accessible to one adaptive technology. Even if we were
> to say "this is JAWS conforming" we have no idea exactly what that means.
> Which version of JAWS, which browser, which version of the browser, which
> device, which user settings?
>
> This is why we make digital content/applications accessible to international
> standards. We can test with screen readers, Text-to-Speech tools, voice
> recognition tools, alternate input devices to understand and confirm a level
> of accessibility but it is the international standard that provides the
> foundation for adaptive technologies to work with digital
> content/applications.
>
> For example, JAWS 17 would not read Alt text for images in PDF documents or
> Word documents...that feature was broken until JAWS 18. Did that mean that
> all correctly tagged PDF or accessible Word documents read with JAWS were
> not "accessible"? No, the documents were tagged and created correctly and
> the Alt Text was present. Likewise, if someone uses Read Out Loud to test
> PDF, Read Out Loud only reads the entire document or the page and does not
> have the capability of accessing the more granular information like tables
> cells with column and row title information...it hasn't evolved since
> Acrobat 5 or 6 when it was introduced as an example of what someone might
> hear if they used a screen reader or Text-to-Speech tool. Does that mean
> that the PDF is not "accessible"? Not if it is tagged correctly and passes
> both an automated testing tool and a manual testing process.
>
> Cheers, Karen
>
>