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