Level AAWCAG 2.0

1.4.4 Resize Text

Text can be resized without assistive technology up to 200 percent without loss of content or functionality.

Last reviewed: September 9, 2026

Understanding 1.4.4

This criterion serves people with low vision who need larger text but do not use dedicated screen magnification software. It requires that ordinary browser zoom or OS text-resizing features work correctly, so content must reflow, remain readable, and stay fully operable at up to 200% magnification rather than being clipped, overlapping, or becoming unusable.

How to Meet It

Use relative units (em, rem, %) rather than fixed pixel values for font sizes and containers where practical, avoid disabling browser zoom (do not set user-scalable=no or maximum-scale=1 in the viewport meta tag), and test the page at 200% browser zoom to confirm text isn't cut off, doesn't overlap other content, and doesn't push interactive controls off-screen.

Code Examples

INCORRECT

<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">

CORRECT

<meta name="viewport" content="width=device-width, initial-scale=1.0">

Frequently Asked Questions

Does this mean pinch-to-zoom must be supported on mobile too?

The criterion itself is normally tested via desktop browser zoom, but blocking pinch-to-zoom on mobile (user-scalable=no) removes the user's ability to resize text at all, which also fails 1.4.10 Reflow, so mobile zoom should not be disabled either way.

Is a separate "large text" toggle on the site enough to pass this?

A toggle can help users, but it doesn't exempt the page from supporting standard browser or OS zoom. This criterion is about the page not breaking when the user applies their own zoom or text-size setting, not about the site providing its own resize widget.

Related Success Criteria

1.4.1 Use of Color 1.4.2 Audio Control 1.4.3 Contrast (Minimum)1.4.5 Images of Text

Quick Facts

Criterion1.4.4
LevelAA
IntroducedWCAG 2.0

Automate Compliance

AccessiSight automatically scans and identifies 1.4.4 issues in your codebase.

Try Scanner Free