RE: WCAG v2.1 for mobile website evaluation

Screen reader testing is part of WCAG compliance as many users who need alternative accommodations use screen readers to access the web.  We’ve found that many of the requirements for 1.3.1, Info and Relationships, are more easily tested using screen readers.

We begin with programmatic testing, then keyboard-only to catch the more obvious issues, and then test with an assortment of desktop and mobile screen readers.  To save time on the mobile view, you can tab through the mobile version in an emulator using a keyboard, to make sure the tab order is correct.  Once you catch the major issues there, go through it again on the device using a screen reader.


From: Salazar, Joshua Allen [mailto:salaz3j@cmich.edu]
Sent: Friday, August 17, 2018 10:38 AM
To: Matt Elton <mattelton35@gmail.com>; w3c-wai-ig@w3.org
Subject: RE: WCAG v2.1 for mobile website evaluation

We test on as many devices and screen readers as possible when doing accessibility testing simply because each of them have their own quirks. Here at CMU, we provide students with JAWS so we make sure to, at the very least, test on that. I would look at what your users are using and go from there. If your users are not easily identifiable, WebAIM has some nice data<https://webaim.org/projects/screenreadersurvey6/> that could help you out.

Keep in mind your goal is to be WCAG compliant. Screen reader testing is secondary and should follow suit if WCAG compliant.

[cid:image001.png@01D43619.606D38C0]

Joshua Salazar
UI / UX Designer & Developer
Office of Information Technology
PA Council Academic Division
P: 989-774-3424



From: Elizabeth Linnetz <elizabeth.linnetz@theprimacy.com<mailto:elizabeth.linnetz@theprimacy.com>>
Sent: Friday, August 17, 2018 10:23 AM
To: Matt Elton <mattelton35@gmail.com<mailto:mattelton35@gmail.com>>; w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>
Subject: RE: WCAG v2.1 for mobile website evaluation

Hi Matt,

You’ll find different issues on a mobile vs. desktop view – even if most of the elements are the same, frequently the menu renders differently on mobile vs. desktop.  Tabs may render as accordions and need to be tested, and other elements may change as well. You’ll want to make sure that anything hidden in mobile renders properly on desktop and remains hidden from screen readers.  VoiceOver, TalkBack, JAWS, and NVDA all have different quirks as well.


From: Matt Elton [mailto:mattelton35@gmail.com]
Sent: Friday, August 17, 2018 10:07 AM
To: w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>
Subject: WCAG v2.1 for mobile website evaluation

Hi everyone,

I hope you can help me with a question I have been thinking about for a while.

The updated WCAG v2.1 guidelines seem to be device independent but I was wondering if all the non-compliant issues would be discovered if someone was to conduct an assessment of a mobile version of a responsive site using just an iPhone (and VoiceOver). Is this sufficient or should the desktop version also be assessed (using a desktop screen reader like JAWS or NVDA).

Thank you very much for your help.

Cheers,
Matt