Goal
Allow users to increase text size without breaking content or functionality.
Success Criterion · WCAG 1.4.4
Resize Text
Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.
Level AAWCAG 2.0Perceivable1.4 · Distinguishable
Copy button ready
What to do
Ensure text can be resized up to 200% without loss of content or functionality.
Why it matters
People with low vision often increase text size; fixed layouts can cause overlap, clipping, or hidden content.
Success criterion
What WCAG 1.4.4 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.
Intent
Why WCAG created this requirement
- Text resizing supports low vision users without requiring specialized assistive technology.
- The requirement focuses on loss of content or functionality, not pixel-perfect layout.
- Captions and images of text are excluded because they cannot be resized reliably as text.
Benefits
Who gains when you pass
- Low vision users can read comfortably without horizontal scrolling for every line.
- Users with age-related vision changes can increase text for readability.
- Users on small screens can zoom while still completing tasks.
- Users with cognitive disabilities may benefit from larger, clearer text.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Text may overlap or become unreadable when users zoom to 200%.
Controls may become unreachable if containers clip content.
Users may be unable to complete forms or read instructions when text resizing breaks the UI.
Exception guidelines
Use the WCAG 1.4.4 exceptions correctly
Document the rationale for each exception and note which alternative support you provide.
Captions
Closed captions are often rendered by user agents and may not scale like page text.
Requirement
Captions are exempt from the resizing requirement.
Images of text
Text that is rendered as an image does not resize as text.
Requirement
Images of text are exempt (but see 1.4.5/1.4.9).
Overview
Users must be able to zoom text up to 200% (e.g., browser zoom or text-size settings) without content becoming cut off, overlapping, or unusable. Avoid fixed-height containers, absolute positioning that breaks at zoom, and designs that hide content when text grows.
- Use responsive layouts and relative units (rem/em) instead of fixed pixel sizes for text.
- Avoid fixed heights for text containers; allow content to grow.
- Ensure buttons/inputs can expand for larger text without clipping.
- Test at 200% zoom and with increased default font size settings.
Reference: All summaries and highlights originate from Understanding WCAG 1.4.4 and the W3C quick reference.
Fast facts
- Conformance level
- Level AA
- WCAG version introduced
- WCAG 2.0
- Principle
- Perceivable
- Guideline
- 1.4 · Distinguishable
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Button label
Pass
Button grows in height and wraps text as needed at 200% zoom.
Fail
Button has fixed height; label is clipped or overlaps icon at 200% zoom.
Form layout
Pass
Labels wrap and fields stack vertically when space is constrained.
Fail
Fields overlap and error text is hidden when zoomed.
Card content
Pass
Card expands vertically; text reflows without truncation.
Fail
Card uses fixed height and hides overflow, cutting off content.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document typography and layout guidelines that support zoom and text resizing.
- Capture screenshots of core templates at 200% zoom as regression references.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Understanding 1.4.4
Official W3C interpretation, techniques, and intent for Resize text.
Quick Reference 1.4.4
Filterable list of sufficient techniques and failures.
Technique G142
Using a technology that has commonly-available user agents that support zoom.
Technique C28
Specifying font sizes in relative units.
Failure F69
Failure due to fixed container sizes causing text to be clipped at 200%.
Implementation checklist
Capture progress and blockers
- Use relative units for typography (rem/em) and spacing that adapts with font size.
- Avoid fixed-height containers for headings, buttons, and labels.
- Ensure layouts reflow gracefully when text size increases.
- Check that form fields and error messages remain visible and readable at 200% zoom.
- Avoid text truncation (ellipsis) for critical content; provide wrapping or expansion.
- Test in multiple browsers with zoom and OS text scaling settings.
Testing ideas
Prove conformance with evidence
- Set browser zoom to 200% and verify no content/functionality is lost.
- Increase base font size (e.g., browser settings) and verify layouts still work.
- Check for clipped text in buttons, inputs, and cards.
- Verify modals, menus, and toasts remain usable at increased text sizes.
- Complete key tasks (sign up, checkout, search) at 200% zoom.
Related success criteria
More from Distinguishable (1.4)
WCAG 1.4.1Use of ColorLevel AWCAG 1.4.2Audio ControlLevel AWCAG 1.4.3Contrast (Minimum)Level AAWCAG 1.4.5Images of TextLevel AAWCAG 1.4.6Contrast (Enhanced)Level AAAWCAG 1.4.7Low or No Background AudioLevel AAAWCAG 1.4.8Visual PresentationLevel AAAWCAG 1.4.9Images of Text (No Exception)Level AAAWCAG 1.4.10ReflowLevel AAWCAG 1.4.11Non-text ContrastLevel AAWCAG 1.4.12Text SpacingLevel AAWCAG 1.4.13Content on Hover or FocusLevel AA