WCAG 2.2 - Success Criterion
1.4.4 Resize Text
Description
Text must be resizable up to 200 percent without assistive technology and without loss of content or functionality. Many users with low vision use browser zoom or operating system text size settings to increase text size to a readable level. If a website is built in a way that causes content to become hidden, truncated, or broken when text is enlarged, those users lose access to the content.
How To Test
- Open the page in a browser and navigate to the browser's text size settings.
- Increase the text size to 200% (or use Ctrl/Cmd + + to zoom to 200% in browsers where text zoom equals page zoom).
- Read through all sections of the page and verify no text is clipped, hidden, or overlapping.
- Verify all interactive controls (buttons, links, form inputs, menus) remain visible and operable.
- Scroll horizontally if necessary and check that content has not been pushed off-screen or made inaccessible.
- Test modal dialogs, tooltips, dropdown menus, and other dynamic content at 200% zoom.
- Inspect the CSS for fixed-height containers with
overflow: hiddenthat may clip enlarged text.
Testing Tools
- Color Contrast Analyser (CCA) — Free desktop app. Download from GitHub, install, use the eyedropper tool to measure contrast ratios on the demo. Read the ratio value and compare to AA (4.5:1) or AAA (7:1) standards.
- Lighthouse — Built into Chrome DevTools. Open DevTools (F12), go to Lighthouse tab, select "Accessibility", and run the audit. Review contrast violations and pass criteria in the results.
- axe DevTools — Browser extension for Chrome/Firefox. Install from official page, open DevTools, go to axe tab, run scan, and see detailed contrast violations with remediation advice.
Demo 1: Fixed-height container overflow
The card below has a fixed height: 72px; overflow: hidden. Increase your browser font size (Ctrl + or Cmd +) to see text become clipped.
Same card with min-height: 72px; overflow: visible. Increasing font size expands the container - no content is clipped.
Your subscription renews automatically on the 15th of each month. To cancel at any time, visit Account Settings and select Manage Subscription.
Code
Demo 2: Responsive text sizing with flexible units
Layout uses fixed pixel sizes - breaks at larger font sizes:
Option A
Fixed widths and pixel font sizes cause text to wrap unpredictably.
Option B
Columns may become too narrow or stack unexpectedly.
Layout uses relative units - adjusts gracefully at larger font sizes:
Option A
Relative units (em, rem, %) scale smoothly with user font size changes.
Option B
Columns remain proportional and readable at all zoom levels.
Code
Labels use position:absolute with fixed heights. At large text sizes, labels overlap the values below. Found in real-world checkout form audits.
Simulates ~200% text: labels and values overlap because of fixed container height.
Labels stack above values using normal flow. Container uses min-height and relative units — no overlap at any text size.
Labels and values stack naturally. min-height allows growth.
Code
Fail Explanation
A failure occurs when enlarging text to 200% causes content to be cut off, overlap other content, become hidden, or make functionality unavailable. Common failure patterns include fixed-height containers that clip overflowing text, absolutely positioned elements that overlap when text grows, navigation menus that collapse or break at larger text sizes, and text in buttons or labels that becomes truncated. Using viewport units or fixed pixel values for container heights without overflow: auto or min-height settings are common technical causes.
Pass Explanation
A passing implementation uses relative units (such as em, rem, or percentages) for font sizes and container dimensions, and avoids fixed-height containers that would clip enlarged text. The layout is tested at 200% text zoom to confirm all content remains visible and readable and all interactive components remain operable. CSS min-height instead of height, and overflow: visible or overflow: auto rather than overflow: hidden, are practical implementation techniques.
Notes
This criterion specifically addresses text resize, not full-page zoom. However, in modern browsers, browser zoom also enlarges text, so testing with browser zoom at 200% is a practical and widely accepted testing method. The related criterion 1.4.10 Reflow covers the requirement that content must remain usable at 400% zoom without horizontal scrolling.
Techniques
WCAG techniques used in this demo: C12, C28, G179
Suggested Solutions & References
Curated from 32 real-world audit findings and official WCAG guidance.
Official W3C / WAI
- Understanding SC 1.4.4: Resize Text
- Technique C28: Specifying text size in em units
- Technique G179: No loss of content at 200% text size