Zoom / Text Resizing – Web Accessibility and WCAG 1.4.4
Text resizing is one of the core requirements for accessible websites: users must be able to resize text up to 200% without loss of content or functionality. This is mandated by WCAG criterion 1.4.4 at Level AA.
People with visual impairments rely on this function. They use the browser zoom or the operating system's font size settings to make text readable. Websites that prevent this, or that break visually when the font size is increased, actively exclude this user group.
Since 28 June 2025, WCAG 2.1 Level AA has been legally required for many businesses across the EU under the European Accessibility Act (EAA). Failing to implement text resizing correctly risks legal consequences, including warnings and regulatory proceedings.
Zoom / Text Resizing at a Glance
- WCAG criterion: 1.4.4 – Resize Text, Level AA
- Requirement: Text resizable to 200% without loss of content or functionality
- Font size: Use relative units (rem, em) instead of fixed pixel values
- Mobile: Pinch-to-zoom must not be disabled via the viewport meta tag
- Legal: Mandatory under the EAA across the EU since June 2025
What WCAG 1.4.4 Requires in Practice
The Resize Text criterion (1.4.4) falls under the WCAG principle of Perceivability. It requires that text can be resized up to 200% without assistive technology, without content being lost or functionality breaking. The only exceptions are captions and text embedded directly in images.
In practice, this means layouts must be flexible. Text must not be trapped inside fixed containers that overflow or clip when the font size increases. All interactive elements, including buttons, links, and form fields, must remain fully visible and operable at 200% text size.
Implementing Font Size Correctly
The most common mistake is using fixed pixel values for font sizes. Pixels ignore the base font size set by the user in their browser or operating system. Relative units scale with the user's preferences:
- rem: Relative to the root element's base font size, recommended for body text
- em: Relative to the parent element, well suited for component-based layouts
- %: Percentage of the parent font size, also scalable
- Avoid px: Or at minimum test whether the layout still renders correctly at 200% browser zoom
Zoom on Mobile Devices
On smartphones and tablets, users often rely on the pinch-to-zoom gesture to enlarge content. Many websites inadvertently disable this behaviour via the viewport meta tag, for example with user-scalable=no or maximum-scale=1.
This is a direct violation of WCAG 1.4.4. The viewport tag must not restrict user scaling. Modern browsers such as Safari and Chrome already partially ignore these restrictions, but relying on browser behaviour alone is not a compliant approach.
Text Resizing and WCAG Perceivability
WCAG 1.4.4 is part of the Perceivable principle: information and user interface components must be presented in ways users can perceive. Closely related criteria include 1.4.3 (Contrast) and 1.4.12 (Text Spacing), both of which also depend on flexible layouts.
For users with dyslexia or cognitive impairments, enlarged text is often not just a comfort feature but a prerequisite for understanding content at all. Accessibility at the font size level therefore benefits a far broader audience than people with visual impairments alone.
SiteCockpit Solution
easyMonitoring: Automatically detect text resizing violations
easyMonitoring automatically checks your website for WCAG violations, including issues with text resizing: fixed pixel font sizes, disabled viewport zoom, and layouts that break at 200% scaling. You receive a score from 0 to 100, plus a detailed report with exact locations, severity levels, and guidance on how to fix each issue.
Discover easyMonitoring →Frequently Asked Questions about Text Resizing
Does browser zoom count as text resizing under WCAG 1.4.4?
Yes. Browser zoom is the primary method addressed by WCAG 1.4.4. If a website loses content, overlaps text, or makes functions inaccessible at 200% browser zoom, it is non-compliant. The test is straightforward: set browser zoom to 200% and navigate through all key pages.
Do all texts need to be resizable, or are there exceptions?
WCAG 1.4.4 lists two exceptions: captions and text embedded directly in images. All other text, including body copy, headings, buttons, labels, and form fields, must be scalable to 200%.
Is it sufficient to offer text resizing through the easyVision widget?
The easyVision widget is a valuable addition and actively helps users adjust font sizes. However, it does not replace the technical requirement in WCAG 1.4.4 that native browser zoom must function correctly. Both measures complement each other effectively.
How do I test whether my website meets WCAG 1.4.4?
Set browser zoom to 200% and navigate through all key pages. Check whether text gets clipped, content overlaps, buttons or links become unclickable, or a horizontal scrollbar appears because the layout does not reflow correctly. Automated tools like easyMonitoring support systematic testing.
Does your website meet WCAG 1.4.4?
Have your website automatically checked for text resizing violations and other WCAG criteria. easyMonitoring delivers a detailed report with precise locations so you can fix issues efficiently.
Try for freeRelated Topics
- Perceivable (WCAG) – The WCAG principle that WCAG 1.4.4 belongs to
- WCAG Level AA – The legal minimum standard on which WCAG 1.4.4 is based
- Dyslexia – Why enlarged text matters for users with reading impairments
- Digital Accessibility – Overview of all requirements and measures