W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2020

Re: How to test for WCAG 2.1 SC 1.4.10 Reflow - Level AA?

From: Alastair Campbell <acampbell@nomensa.com>
Date: Mon, 10 Feb 2020 17:45:03 +0000
To: "Newton, Brooks (TR Product)" <Brooks.Newton@thomsonreuters.com>
CC: "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Message-ID: <823226AB-2BD5-40C7-8261-E62176966B18@nomensa.com>
Hi Brooks,

If it helps, I tend to test reflow, text-size & text-spacing at the same time:

- Set the window to wider than the largest breakpoint (usually 1280 wide does that)
- Zoom until the effective width is 320px (which is 400% from 1280)
- Check for horizontal scrolling.
- Check for text that hasn't re-sized to at least 200%
- Check for any sticky headers/footers that block the view (not a fail, but we bring that up as a 'best practice' issue)
- Activate the text-spacing bookmarklet
- Gradually zoom out looking for areas of text that have been cut off, and check that menus & complex features work.

It's worth poking around features like hamburger menus and anything that isn't standard content as you go through those connotations, but once you've done it on one page of a site you can narrow down to the differences on other pages.



´╗┐On 10/02/2020, 17:11, "Newton, Brooks (TR Product)" <Brooks.Newton@thomsonreuters.com> wrote:

    Aha!  Nice workaround by docking the Chrome DevTools to the side.   That allows the Chrome browser viewport to be resized below 500 pixels.  Also, good advice on starting at 640 pixels in the browser viewport width, then zooming to 200% to test for Reflow.  Thank you, Patrick, for those tips.

Received on Monday, 10 February 2020 17:45:08 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:34 UTC