E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 3 (In chronological order)

From: Ajeesh Thomas
Date: Mon, Jan 20 2025 7:46AM
Subject: Screen Reader Testing Approach for Responsive Components – WCAG Compliance
No previous message | Next message →

Dear Web AIM Community,

I am currently conducting NVDA-based screen reader testing on a web
application, specifically on laptops; mobile testing is not included in
this assignment.
I seek guidance on setting up a right testing approach from a WCAG
conformance perspective.

Could you please provide clarity on the following aspects:

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.
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?
3. What do WCAG conformance documents state regarding this topic?

Please help me with your insights. Additionally, if there are any relevant
artifacts or references, kindly share them.

Thank you for your support.




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

From: Patrick H. Lauke
Date: Mon, Jan 20 2025 8:29AM
Subject: Re: Screen Reader Testing Approach for Responsive Components – WCAG Compliance
← Previous message | Next message →

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

From: Ajeesh Thomas
Date: Wed, Jan 22 2025 8:11AM
Subject: Re: Screen Reader Testing Approach for Responsive Components – WCAG Compliance
← Previous message | No next message

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

On Mon, Jan 20, 2025 at 9:07 PM Patrick H. Lauke < = EMAIL ADDRESS 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. "