Protocol
Make enlarged text fit the task, not just the screen
A larger sentence is not helpful when its ending disappears.
When it fits
- Readers enlarge the interface and lose controls or part of the text.
When to avoid it
- Tables, maps and other genuinely two-dimensional content need specific treatment. Do not infer full accessibility from one successful zoom setting.
Why it matters
Test a narrow viewport and substantial zoom with realistic content. Inspect reading order, wrapping and controls, not just font size. WCAG’s reflow criterion includes a 320 CSS pixel width condition and exceptions; use its full wording when assessing conformance.
Steps
- Open a content-heavy page and its important form or dialog.
- Check whether text and controls remain available without unnecessary horizontal travel.
- Repeat with long labels, validation messages and translated text.
An example
At high zoom, a card’s actions cover its final paragraph. The defect is lost content, not an unattractive layout.
Check your result
Can the reader understand the content and complete the task at the tested enlargement?
Keep this limit in mind
- Tables, maps and other genuinely two-dimensional content need specific treatment. Do not infer full accessibility from one successful zoom setting.
Connected ideas
Useful withTest the target and its neighbours, not just the icon
Evidence and sources
Supports
WCAG 1.4.10 addresses loss of content or functionality and two-dimensional scrolling at specified narrow viewport dimensions, with exceptions.
Some content genuinely requires a two-dimensional layout; passing one viewport test is not full conformance.
Understanding Success Criterion 1.4.10: Reflow · Success criterion, 320 CSS pixel width and examples.