1. Choose representative pages and states
Select an article, a directory or results page, a form, and any important navigation or dialog state the site uses. Include long labels and realistic content rather than only the neatest sample. Write down which templates and states the review covers so omissions remain visible.
Record the browser, starting viewport, zoom or text-size method, and the page version. Keep a simple task list such as reading the introduction, opening navigation, selecting a filter, and reaching the form result. This makes the review about usable content rather than whether a screenshot happens to fit.
2. Check text enlargement
W3C’s explanation of WCAG 2.2 criterion 1.4.4, Level AA, addresses text resizing up to 200% without loss of content or functionality, except captions and images of text. Its guidance also covers intermediate enlargement steps when the browser provides them.
Check headings, body text, button labels, field instructions, and messages at the relevant sizes. Record clipped words, overlapping content, and controls that cannot be reached. Verify the intended text enlargement actually occurs; changing a viewport alone does not demonstrate that the text became larger.
Sources: [1]
3. Check reflow as a separate task
Criterion 1.4.10 addresses reflow at a width equivalent to 320 CSS pixels for vertically scrolling content, or a height of 256 CSS pixels for horizontally scrolling content. W3C’s 1280-pixel-wide viewport at 400% zoom is an equivalence example, not a universal starting setup for every test.
Record the actual dimensions and inspect the reading order, visible information, and available functions. For ordinary paragraphs, note whether reading each line requires movement in both directions. Check that content moved into a menu or stacked layout remains available and understandable rather than simply disappearing.
Sources: [2]
4. Inspect overlays and any exception
W3C allows a reflow exception for parts that require a two-dimensional layout for meaning or use. That exception does not automatically cover the whole page. Identify the specific component and why its layout is necessary, while checking the surrounding content on its own.
Operate menus and forms in the reviewed layout. Inspect fixed headers, banners, and dialogs for content they may cover, including error messages and action buttons. Use a controlled test environment for submissions. Keep a screenshot and a short reproduction sequence for a defect so another reviewer can reproduce the same state.
Sources: [2]
5. Recheck repairs and describe the scope
After a repair, revisit the affected state and a representative sample of other pages using the same component. Record whether the problem was corrected and any new issue introduced by the change. Keep source inspection, browser operation, and assistive-technology testing as distinct evidence.
Do not describe a breakpoint check, a pinch-zoom gesture, or one passing page as a complete accessibility assessment. Save the environments and states actually reviewed and the ones still pending. These checks should feed the broader accessibility work alongside keyboard access, structure, contrast, forms, and meaningful content.
Your quick checklist
- Representative templates and states are selected.
- The browser, dimensions, and enlargement method are recorded.
- Text enlargement and reflow have separate results.
- Exceptions apply only to specifically justified content.
- Repairs are rechecked without claiming full conformance.
Sources & scope
W3C supports the two criteria, dimensions, and exception scope. The sampling and defect-record workflow is ATN editorial guidance. No browser rendering or accessibility certification of ATN is claimed by this article.
- W3C: Understanding Resize Text (opens in a new tab)Source checked October 10, 2026
- W3C: Understanding Reflow (opens in a new tab)Source checked October 10, 2026
Published October 10, 2026. No affiliate links or paid placements in this guide.
