- Level
- AA
- Since
- WCAG 2.0
- Entries
- 11 / 193
1.4.4 Resize Text
Visitors have to be able to enlarge text to twice its size without losing content or functions.
/ What it requires
People with low vision enlarge text, most of them with nothing more than the browser's zoom. The page has to survive that up to 200 percent: all the text still there, nothing cut off or overlapping, every button and form still usable. When a site blocks zoom on a phone, or boxes with a fixed height swallow the enlarged lines, the visitor is left choosing between text too small to read and a page that no longer works.
The criterion says text can be resized up to 200 percent without assistive technology and without loss of content or functionality. It exempts captions and images of text. It does not require the layout to stay in one column: horizontal scrolling at 200 percent is not a failure here, and narrow viewports are the subject of 1.4.10 Reflow. Browser zoom that scales the whole page is an accepted way to meet it, provided the page neither prevents zoom nor breaks under it.
/ How pages fail it
- The viewport meta tag carries user-scalable=no or a maximum-scale below 2, which stops pinch zoom on phones.
- Text sits in containers with a fixed height and overflow: hidden, so enlarged lines are clipped.
- Font sizes are set in viewport units alone, such as font-size: 2vw, so the text does not grow when the page is zoomed.
- Enlarged text overlaps neighbouring content because elements are absolutely positioned at pixel offsets.
- Text inside form fields and on buttons stays the same size while the text around it grows.
/ How to check it yourself
- In a desktop browser press Ctrl and plus (Cmd and plus on a Mac) until the zoom reads 200 percent. Read every section and use every control.
- In Firefox switch on View, Zoom, Zoom Text Only and repeat the check. Only the text grows then, which exposes boxes with a fixed height.
- On a phone, pinch to zoom. If the page does not respond, open the source and read the content of the viewport meta tag.
- Look for clipped lines, overlapping blocks, text hidden behind other elements and buttons that have moved out of reach.
/ How to fix it
- Write the tag as meta name="viewport" content="width=device-width, initial-scale=1" and delete user-scalable=no and maximum-scale.
- Set font-size in rem or em. If you use viewport units, combine them with a rem value, for example clamp(1rem, 0.8rem + 1vw, 1.5rem).
- Replace height with min-height on anything that holds text, and let containers grow.
- Use a unitless line-height such as 1.5, so that line spacing scales with the text.
- Give form controls font: inherit, so their text follows the size of the page.
/ What our scanner checks
The static pass reads the viewport meta tag in the page source and reports it when the content contains user-scalable=no or maximum-scale=1. That is the whole check on the server: the page is not zoomed, so text that is clipped, overlapping or lost at 200 percent goes unnoticed, as does text sized in viewport units. Those faults are found by zooming the page by hand.
/ Who fails it, in our own measurements
| Body | Sector | Instances | Score |
|---|---|---|---|
| Bundesministerium des Innern | government · DE | 1 | 10 |
| Deutsche Nationalbibliothek | culture · DE | 1 | 23 |
| Deutsche Rentenversicherung | government · DE | 1 | 5 |
| Los Angeles County | government · US | 1 | 10 |
| Narodowy Instytut Dziedzictwa | culture · PL | 1 | 6 |
| PKP Intercity | transport · PL | 1 | 2 |
| Polski Instytut Sztuki Filmowej | culture · PL | 1 | 7 |
| Prezydent RP | government · PL | 1 | 12 |
| Statistisches Bundesamt | government · DE | 1 | 9 |
| Uniwersytet Jagielloński | education · PL | 1 | 1 |
| Warszawa | city · PL | 1 | 20 |
One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.
/ Questions about this criterion
Does user-scalable=no fail WCAG?
It is treated as a failure of 1.4.4 when it stops a visitor from enlarging text to 200 percent, which is its effect in mobile browsers that honour it. The same goes for a maximum-scale value below 2. Some browsers ignore both settings, but conformance cannot rest on that. Remove them: width=device-width and initial-scale=1 are all the viewport tag needs.
Is browser zoom enough to meet 1.4.4?
Yes, as long as the page works at 200 percent zoom. The criterion asks that text can be resized without assistive technology, and zoom is a feature of the browser, not an assistive tool. A site does not need its own text size buttons. What it must not do is block zoom, or lose content and functions when zoom is used.
What is the difference between 1.4.4 Resize Text and 1.4.10 Reflow?
1.4.4 is about size: text enlarged to 200 percent must stay complete and usable, and scrolling sideways is tolerated. 1.4.10 is about layout: at a width of 320 CSS pixels, which equals 400 percent zoom in a window 1280 pixels wide, content must fit without scrolling in two directions. A page can pass the first and still fail the second.
