ADA Title II Deadline: April 24, 2026

Text Resize Accessibility Checker

WCAG 1.4.4 requires that text can be resized up to 200% without loss of content or functionality. Fixed pixel font sizes and overflow:hidden break this for millions of low-vision users.

No signup required. Results in under 60 seconds.

WCAG 2.1 AAAI Fix SuggestionsFree, No Signup

What WCAG 1.4.4 Requires

WCAG 1.4.4 (Resize Text, Level AA) requires that text can be resized up to 200% without assistive technology, and without loss of content or functionality. This means users should be able to use their browser's zoom or text-size settings to double the text size while the page remains usable — no clipped content, no overlapping text, no horizontal scrolling (for content that does not require it), and no loss of functionality. Related criterion WCAG 1.4.10 (Reflow, Level AA, added in WCAG 2.1) requires that content reflows at 400% zoom (320px CSS width) without horizontal scrolling. These criteria serve the approximately 246 million people worldwide with moderate to severe vision impairment who routinely zoom or enlarge text to read web content. Low-vision users represent a far larger population than screen reader users.

Common Text Resize Failures

Websites break at larger text sizes due to these patterns:

  • Fixed-height containers: <div style="height: 200px; overflow: hidden"> — when text grows, it gets clipped. Fix: use min-height instead of height, or overflow: visible
  • Absolute positioning of text: Text in absolutely positioned elements does not reflow with the rest of the page, causing overlap at larger sizes
  • Fixed-width containers with no wrapping: width: 400px; white-space: nowrap; overflow: hidden; — text is truncated. Fix: allow wrapping and use responsive widths
  • Text in images: Images of text cannot be resized by browser text-size settings. Use real text wherever possible (WCAG 1.4.5)
  • Viewport units for font size: font-size: 2vw alone ignores user text-size preferences. Fix: use font-size: clamp(1rem, 2vw, 1.5rem) to set minimum and maximum sizes that respect user settings

Best Practices for Resizable Text

Design and code for text resize from the start:

  • Use relative units: rem and em for font sizes, not px. While modern browsers can zoom pixel-sized text, rem respects the user's root font-size preference: font-size: 1rem (16px default, scales with user settings)
  • Flexible layouts: Use CSS Grid and Flexbox with fr units and minmax() to create layouts that accommodate larger text without breaking
  • Test at 200%: Open your site, press Ctrl+/Cmd+ until the browser shows 200% zoom. Check every page for clipped text, overlapping elements, and lost functionality
  • Avoid !important on font-size: User stylesheets and browser settings need to override your font sizes. !important can prevent this
  • Responsive breakpoints: Ensure your responsive design handles not just narrow viewports but also zoomed wide viewports where the effective viewport shrinks

How CompliScan Detects Text Resize Issues

CompliScan identifies patterns that commonly break at larger text sizes: fixed-height containers with overflow hidden that contain text, elements with white-space: nowrap combined with overflow clipping, and CSS that prevents text scaling. The scanner also checks for content that overflows its container at normal zoom levels — a strong indicator it will break at 200%. Each finding includes the specific CSS property causing the issue and an AI-generated fix suggesting responsive alternatives. Full 200% zoom testing requires manual verification — automatically rendering every page at multiple zoom levels is computationally expensive. CompliScan catches the code patterns most likely to fail and prioritizes them by severity. For complete WCAG 1.4.4 compliance, supplement with manual zoom testing of your most critical pages. This is required for the European Accessibility Act and ADA Title II deadline of April 24, 2026. Try a free scan to identify potential text resize failures.

Frequently Asked Questions

Should I use rem, em, or px for font sizes?

Use rem for most font sizes — it scales relative to the root element's font size, which respects user preferences. Use em for components where font size should scale relative to the parent (like nested elements). Avoid px for font sizes when possible. While modern browsers can zoom px-based text, rem and em provide better support for users who change their default font size in browser settings rather than using zoom.

Does browser zoom satisfy WCAG 1.4.4?

Yes, WCAG 1.4.4 allows text to be resized through any mechanism — browser zoom, text-only zoom, or operating system settings. The key requirement is that the result is usable: no content or functionality is lost at 200%. Modern browser zoom scales the entire viewport, which generally works well if your layout is responsive. However, some users use text-only zoom (a browser setting that scales text without scaling images or layout), which is more demanding of your CSS.

What about WCAG 1.4.10 Reflow?

WCAG 1.4.10 (Reflow, Level AA, added in WCAG 2.1) requires that at 400% zoom — equivalent to a 320px wide viewport — content can be accessed without horizontal scrolling (for vertically scrolling content). This is effectively a responsive design requirement. If your site works on a 320px mobile viewport without horizontal scroll, you meet 1.4.10. Exceptions exist for content that inherently requires two-dimensional layout (data tables, maps, diagrams).

Do I need to support text resize for images of text?

WCAG 1.4.5 (Images of Text, Level AA) requires that real text is used instead of images of text wherever possible. Images of text cannot be resized through browser text settings and cannot be customized by users. Exceptions exist for logos and text that is essential to the information being conveyed (like a font sample). For everything else, use CSS-styled real text. This inherently supports text resize.

Check Your Website Now

Enter your URL below and get a free accessibility report with AI-powered fix suggestions in under 60 seconds.

No signup required. Results in under 60 seconds.