WCAG 1.4.4 Resize Text
WCAG 1.4.4 Resize Text explained: body text must scale to 200% without clipping content or breaking controls. Exceptions, failures and how to test.
Table of contents
WCAG 1.4.4 Resize Text is a Level AA success criterion, from WCAG 2.0. This page is part of the WCAG 2.2 success criteria guide. It explains the rule in plain English, who it helps, what passing and failing code look like, and how to test it by hand and with AccessBell, a website accessibility monitoring tool. AccessBell is not an overlay.
What WCAG 1.4.4 Resize Text requires
Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.
That sentence is the heart of the criterion. The exceptions and notes are in the WCAG 2.2 Recommendation and the Understanding document for 1.4.4 Resize Text.
What WCAG 1.4.4 means in plain English
People enlarge text from the browser, usually with Ctrl and plus, or the Zoom command. WCAG 1.4.4 Resize Text says the page still has to work at 200% zoom. Text cannot disappear into a fixed-height box, overlap other text, or hide a button someone needs.
The criterion is about the browser’s own zoom, not a separate widget that changes font size. Captions and images of text are excepted, because captions have their own rules and an image of text does not scale the way real text does. Pinch-zoom on a phone is the same idea: a viewport setting of user-scalable=no or maximum-scale=1 blocks it, and that fails 1.4.4.
Who WCAG 1.4.4 helps
People with low vision who read at a larger size and do not use a screen reader. Also anyone who zooms a page on a small laptop or in bright light. It is separate from 1.4.10 Reflow, which asks the layout to fit a narrow window without sideways scrolling.
Pass and fail examples
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
.card { height: 120px; overflow: hidden; } <meta name="viewport" content="width=device-width, initial-scale=1">
.card { min-height: 8rem; } How to test WCAG 1.4.4
- In a desktop browser, set zoom to 200% (Ctrl and plus, or Command and plus). Do not only change the font in an extension.
- Read the page from top to bottom. Look for text cut off by a fixed height, overlapping columns, or buttons pushed out of view.
- On a phone, try to pinch-zoom. If the page refuses to zoom, inspect the viewport meta element for user-scalable=no or maximum-scale=1.
- Repeat on a page with a menu, a form and a dialog. Open the dialog at 200% and confirm every control is still reachable.
Testing WCAG 1.4.4 with AccessBell
A website accessibility monitoring tool can flag a viewport meta element that disables scaling. That is the axe-core rule when it applies. Zooming the page and checking that nothing is clipped still needs a person, because a scanner does not decide whether text at 200% is usable.
AccessBell's scanner runs axe-core, which includes 1 rule that catch code-level failures of this criterion. Automated checks help you spot issues quickly. A person still needs to review what they cannot judge.
meta-viewport: Ensure <meta name="viewport"> does not disable text scaling and zooming (details (opens in a new tab))
This criterion is included in: WCAG 2.2 AA Checker, WCAG 2.1 AA Checker, ADA Compliance Checker, Section 508 Checker, EN 301 549 Checker.
Check your site for this with a free scan of one public page. AccessBell is a website accessibility monitoring tool, not an overlay.
Common failures on Shopify, WordPress, Wix and Squarespace
These are patterns in how the builders work. They are not counts from AccessBell scans. Where a platform hosts the screen, a merchant may not be able to change it, and an unscanned page is not a pass.
Shopify
Theme CSS often sets a fixed height on announcement bars, product cards and predictive-search panels. At 200% zoom the text inside is clipped. The theme, not the hosted checkout, is where a merchant can change that. Scan the storefront with the Shopify checker.
WordPress
A theme or page builder that sets a card, hero or menu item to a fixed pixel height will clip text at 200%. Some older themes also emit a viewport tag with maximum-scale=1. Check both the meta element and the layout in the WordPress checker.
Wix
Text in strips and slideshows can sit in a box that does not grow. The Wix checklist is the manual pass for layout; the Accessibility Wizard does not measure 200% zoom on every element. Confirm pinch-zoom still works on the published site, then run the Wix checker.
Squarespace
Fluid Engine blocks can overlap when the page is zoomed, and a fixed-height text block clips a longer heading. Squarespace’s inclusive design guidance is summarized in the Squarespace checklist. Test the published page at 200%, not the editor preview, then scan it with the Squarespace checker.
Level and conformance
Level AA, in WCAG since 2.0, under Distinguishable. A site that claims WCAG 2.2 Level AA has to meet 1.4.4 wherever it uses real text. It does not require text to reflow into a single column. That is 1.4.10 Reflow, also Level AA, added in WCAG 2.1.
Conforming at Level AA means meeting every Level A and Level AA criterion that applies, not only the ones labeled AA. See the WCAG 2.2 conformance requirements. This page explains the technical rule. It is not a legal opinion. Read the disclaimer.
Related WCAG criteria
- 1.4.3 Contrast (Minimum) (Level AA, WCAG 2.0)
- 1.4.10 Reflow (Level AA, WCAG 2.1)
- 1.4.11 Non-text Contrast (Level AA, WCAG 2.1)
- 1.4.5 Images of Text (Level AA, WCAG 2.0)
Every criterion is listed in the WCAG 2.2 success criteria guide.
Frequently Asked Questions
What level is WCAG 1.4.4 Resize Text?
Level AA. It has been in WCAG since 2.0, so it applies when the target is WCAG 2.0, 2.1 or 2.2 at Level AA.
Is browser zoom the test for 1.4.4 Resize Text?
Yes. The W3C wording says text can be resized without assistive technology up to 200 percent. The usual test is the browser’s zoom, not a plugin that only changes the font.
Does a “text size” widget meet WCAG 1.4.4?
Not by itself. The page still has to work when someone uses the browser’s own zoom up to 200%. A widget can be an extra help. It does not replace that.
Can AccessBell prove a page passes 1.4.4 Resize Text?
No. The free scan can catch a viewport setting that blocks scaling. A person still has to zoom to 200% and check that content and controls are still there.
Sources
- W3C: Understanding 1.4.4 Resize Text (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.