WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Screen reader support

for

From: Birkir R. Gunnarsson
Date: Apr 21, 2020 8:36AM

Yeap, what Jonathan said.
Look at the "accessibility supported" conformance requirement for
WCAG, this is in addition to meeting the success criteria.
The defintion of "accessiblity supported" is pretty vague but
basically suggests you verify that your content is accessible with at
least one popular combination of a browser and an assistive technology
application, a screen reader is the logical choice.
Coding to standards should mean your page is 98% accessible, sadly
browsers and assistive technology vendors don't always uphold their
bargain in supporting content coded to standards.
I won't go on that rant here. ;)
If your page is plain and well coded you barely need to test with a
screen reader.
If your page contains complex or custom objects like tabs, menus,
custom date pickers, live regions and other complex scripted
components, this is where you need to test the page with at least one
screen reader/browser combo.
NVDA is the logical choice, because it is free, open source and does
very little second guessing so if there is a problem, you will notice
it (Jaws tries to fill in the blank, good for users bad for testers).
Use the WebAIM survey when deciding what combination to test with.
For mobile apps, just use the built-in screen reader and other
assistive technology features, at least the Zoom, on the device.


On 4/21/20, Jonathan Avila < <EMAIL REMOVED> > wrote:
> Checkout the Understanding Conformance document from WCAG 2.1 for
> accessibility supported.
> https://www.w3.org/WAI/WCAG21/Understanding/conformance
>
> Jonathan
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> <EMAIL REMOVED>
> Sent: Tuesday, April 21, 2020 7:29 AM
> To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] Screen reader support
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know the
> content is safe.
>
>
> Kalpeshkumar Jain
>
> As far as I am aware, there is no legal or standard that states what screen
> reader or what number of screen readers or what versions you have to
> support. You have to consider your customers user base if you know it and
> should be a company policy. Also when testing web sites, using a single
> screen reader like VoiceOver for example. If a window screen reader user
> comes along, the site might not work correctly. AS the screen reader
> technology will work differently. From a QA point of view, this should be
> taking into account.
>
> There are organisations which state what screen readers they have test their
> web sites against. In other words, the screen reader and web browser
> combination they support.
>
> Sean
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> Kalpeshkumar Jain via WebAIM-Forum
> Sent: Tuesday, 21 April 2020 9:24 PM
> To: <EMAIL REMOVED>
> Cc: Kalpeshkumar Jain < <EMAIL REMOVED> >
> Subject: [WebAIM] Screen reader support
>
> Hi All,
> Is there any official statement or document which states that you should
> support maximum or the least one screen reader?
> I went through the W3 articles, however could not find any such artefact
> validating the matter.
>
> While it is wise to cover as much screen reader support as possible, even if
> you support one, you would not attract any litigation.
>
> Can anyone help me in finding any evidence for the above statement?
>
>
> *Kalpeshkumar Jain*
>
> Technical Lead - Mobile Application Development | LearningMate
>
> This mail is governed by the LearningMate Privacy Policy and Disclaimer at
> http://www.learningmate.com/disclaimer.html
>
> --
>
>
> This mail is governed by the LearningMate Privacy Policy and Disclaimer at
> http://www.learningmate.com/disclaimer.html
> <http://www.learningmate.com/disclaimer.html>;
>
>
> > > http://webaim.org/discussion/archives
> >
> > > http://webaim.org/discussion/archives
> > > > > >


--
Work hard. Have fun. Make history.