Resize Text: Readable and Usable at 200%
Also called: Text resizing, Text zoom, 200% zoom, Scalable text
Definition
Resize Text is WCAG success criterion 1.4.4. Except for captions and images of text, text must be resizable up to 200 percent without assistive technology and without loss of content or functionality.
Resize Text is the WCAG requirement that people can make text twice as large without the page falling apart. Many visitors increase the font size or zoom in because the default text is too small for them – and they should still see every word and be able to use every button. Text resizing is mostly the browser's job; the website only has to stop getting in the way.
What it means
WCAG 1.4.4 Resize Text is a Level AA criterion of WCAG 2.2: "Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality."
Key points from W3C:
| Topic | What applies |
|---|---|
| Target | 200% – twice the width and height of the text |
| Method | At least one scaling method that browsers support, e.g. page zoom or text-only zoom |
| Steps in between | Every step from 100% to 200% must also work |
| Exceptions | Captions and images of text |
| Not covered | Browser-controlled parts such as native tooltips and file pickers |
| Responsive sites | Every layout variant must reach 200% |
W3C explains that the criterion mainly helps people with milder visual impairments, who can read the page without a screen magnifier once the text is bigger. Above 200%, dedicated zoom tools usually work better – the layout side of high zoom levels is covered by reflow.
The three failures W3C documents are F69 (text, images or controls clipped, truncated or obscured at 200%), F80 (text-based form fields that do not grow with the text) and F94 (font sizes set only in viewport units such as vw, which do not respond to text zoom).
Because 1.4.4 is part of EN 301 549 (clause 9.1.4.4), it also applies to websites covered by the European Accessibility Act.
Examples
<style>
/* Good: relative font sizes and containers that grow with the text */
html { font-size: 100%; }
body { font-size: 1rem; line-height: 1.5; }
.button { padding: 0.5em 1em; min-height: 2.75em; }
input, select, textarea { font: inherit; }
/* Bad: a fixed-height box cuts off enlarged text (F69) */
.teaser { height: 120px; overflow: hidden; }
/* Bad: text only in viewport units ignores text zoom (F94) */
h1 { font-size: 4vw; }
/* Better: combine with rem so zoom still works */
h1 { font-size: calc(1.5rem + 2vw); }
</style>Use relative units (rem, em, %) for fonts, padding and container heights, let form controls inherit the font size, use min-height instead of height for boxes with text, and test with both page zoom and text-only zoom.
Set fixed heights with overflow: hidden on text boxes, size headings only with vw, disable pinch-zoom in the viewport meta tag, or put important text into images – images of text are an exception here but cannot be enlarged sharply.
How to test resize text
Questions
What does WCAG 1.4.4 Resize Text require?
Text must be resizable to 200% without assistive technology and without losing content or functionality. Captions and images of text are excluded. It is a Level AA criterion.
Is browser zoom enough to pass resize text?
Usually yes. W3C accepts any scaling method browsers support, and full-page zoom is one of them. The page passes if nothing is cut off, hidden or unusable at 200%.
Which units should I use for font sizes?
Relative units such as rem, em or percentages. Pixel font sizes ignore the default font size visitors choose in their browser settings, and viewport units alone (vw) do not respond to text zoom (W3C failure F94).
Does disabling pinch-zoom violate WCAG?
user-scalable=no and a low maximum-scale prevent mobile visitors from enlarging text and are widely reported as an accessibility error. Remove them from the viewport meta tag – search the page source for user-scalable to find them.
What is the difference between resize text and reflow?
Resize text asks for 200% text size without loss of content. Reflow asks that the whole layout works at 400% zoom – 320 CSS pixels wide – without horizontal scrolling.
Related terms
Reflow: Content That Fits at 400% Zoom
Reflow is WCAG success criterion 1.4.10. Content must work without loss of information or functionality and without scrolling in two directions at a width equal to 320 CSS pixels – or a height of 256 CSS pixels for horizontally scrolling content.
Read definition: Reflow: Content That Fits at 400% ZoomText Spacing: Room to Adjust Lines and Letters
Text Spacing is WCAG success criterion 1.4.12. When users set line height to 1.5, paragraph spacing to 2, letter spacing to 0.12 and word spacing to 0.16 times the font size, no content or functionality may be lost.
Read definition: Text Spacing: Room to Adjust Lines and LettersColor Contrast: WCAG Ratios and How to Check Them
Color contrast is the difference in brightness between text or interface elements and their background, measured as a ratio from 1:1 to 21:1. WCAG requires at least 4.5:1 for normal text and 3:1 for large text.
Read definition: Color Contrast: WCAG Ratios and How to Check ThemImages of Text: Use Real Text Instead
Images of Text is WCAG success criterion 1.4.5. If the technology can achieve the same visual presentation, information is conveyed with real text rather than with text rendered into an image – unless the image can be customized or the presentation is essential.
Read definition: Images of Text: Use Real Text Instead