WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Screen Reader Testing Approach for Responsive Components – WCAG Compliance

for

From: Ajeesh Thomas
Date: Jan 22, 2025 8:11AM

Excellent , Thank you very much for your detailed clarification ...

On Mon, Jan 20, 2025 at 9:07 PM Patrick H. Lauke < <EMAIL REMOVED> >
wrote:

>
>
> On 20/01/2025 14:46, Ajeesh Thomas wrote:
> [...]
> > 1. How should screen reader testing be conducted to ensure the
> > accessibility of components that change behaviour based on screen
> size
> > adjustments? For example, Navigation Links /Site Map may become the
> > Navigation Menu once the Screen size is modified.
>
> Test it at all different variations, separately.
>
> > 2. Is it necessary to perform screen reader testing at 200% and 400%
> > zoom levels to confirm the accessibility of components that undergo
> changes
> > upon resizing?
>
> Yes. There's a whole spectrum of screen reader users. For instance,
> users with low vision may use a combination of zoom/magnification (which
> triggers responsive variations) and screen readers. Hence, you need to
> test all variations.
>
> > 3. What do WCAG conformance documents state regarding this topic?
>
> Per 5.2.2 Full Pages note 3 https://www.w3.org/TR/WCAG22/#cc2 all
> success criteria (unless clearly limited/marked as such) apply to
> theoretically *all* possible variations based on screen sizes - so
> you'll need to test all variations (generally, check what major
> breakpoints a site/web app has, and test each variant).
>
> P
> --
> Patrick H. Lauke
>
> * https://www.splintered.co.uk/
> * https://github.com/patrickhlauke
> * https://flickr.com/photos/redux/
> * https://mastodon.social/@patrick_h_lauke
>
> > > > >


--
Thanks and regards,
Ajeesh Chacko Thomas,

Senior Engineer/S M E Web/Apps Accessibility Testing
IBM Consulting, Bangalore
Phone: 812 33 812 22, 87 220 221 21

"I have promises to Keep,
And miles to go before I sleep. "