
Why Does My Site Fail WCAG Checks for Low Text Resize and Reflow at 400% Zoom?
Horizontal scrolling at 400% zoom is a WCAG 1.4.10 failure, not just a design quirk. Here's why it happens and the exact CSS fixes that resolve it.
Your site fails WCAG 1.4.10 (Reflow) when zooming the page to 400% forces horizontal scrolling to read a full sentence, or when text resizing breaks layout so badly that content overlaps, gets clipped, or disappears. The rule requires content to reflow into a single column at that zoom level, with no two-dimensional scrolling needed for normal reading.
This one can trip up sites that otherwise look pretty polished, even ones with an expensive agency design behind them. Fixed widths, pixel-locked containers, and "it looked fine on my monitor" testing are the usual suspects.
What is WCAG 1.4.10 Reflow, exactly?
WCAG 1.4.10 is a Level AA success criterion that requires content to be usable without scrolling in two directions, at a viewport width equivalent to 320 CSS pixels (roughly what you get when you zoom a 1280px-wide page to 400%). In plain terms: if someone with low vision zooms your site to read it comfortably, the page should restack into one column instead of forcing them to scroll sideways through a giant, un-shrunk layout.
There are a couple of carve-outs. Data tables, maps, and content where two-dimensional layout is genuinely essential (think a spreadsheet or a floor plan) are exempt. But your navigation bar, your pricing cards, your hero section with three side-by-side images? Those need to reflow.
The WebAIM Million survey — an annual scan of the top million home pages — has consistently found that the vast majority of sites carry detectable WCAG failures, and reflow/zoom issues show up often enough that they're worth testing for specifically, not just assuming your responsive breakpoints have you covered.
Why does my site break when I zoom to 400%?
Because most responsive design is tested against screen width, not actual zoom behavior — and those are not the same thing.
A developer sets breakpoints at 768px, 1024px, maybe 1440px. They test by resizing the browser window. It looks great. Then a user with a vision impairment sets their browser zoom to 400%, and suddenly the effective viewport is behaving like it's 320px wide — but the CSS was never told to treat it that way, because nothing actually changed the window size. Zoom and resize trigger different rendering paths in some older layouts, which is exactly why the two can behave so differently.
Likely culprits, in no particular order:
- Fixed-width containers. A div set to
width: 1200pxinstead ofmax-width: 1200px; width: 100%simply won't shrink. It just sits there, wider than the viewport, forcing a horizontal scrollbar. - Fixed-width tables used for layout. Not data tables — old-school layout tables, or modern tables that weren't built with any responsive behavior at all.
- Horizontal card rows and carousels that don't wrap. Three or four cards side by side look fine at 100% zoom and turn into a sideways-scrolling mess at 400%.
- Absolute positioning with hardcoded pixel values. Elements pinned at
left: 850pxdon't care that the viewport shrank. - Images and iframes without a max-width rule. A 1000px-wide embedded video with no
max-width: 100%will blow out the layout every time. - Long, unbreakable strings — URLs, code snippets, or long product SKUs — that don't wrap and push the container wider than it should go.
I worked with a SaaS client last year whose pricing page had three plan cards hardcoded at 380px each, sitting in a flex row with no wrap property. At 100% zoom on a desktop monitor, it looked clean. At 400%, the cards just kept marching off the right edge of the screen, forcing visitors to scroll sideways to see the Enterprise plan price. That's a reflow failure, and it's also, not incidentally, a lost sale for anyone who needs to zoom to read comfortably.
How do I test for reflow and text resize failures?
You don't need expensive software for this. Here's the actual process I use:
- Open the page in Chrome or Firefox. Set the browser zoom to 400% (Ctrl/Cmd and + a few times, or just type it into the zoom control).
- Check for horizontal scrolling. Try to read a full paragraph of body text. If you have to scroll left-right to finish a sentence, that's a failure.
- Resize the browser window to roughly 320px wide (DevTools' device toolbar makes this easy — set a custom viewport). This simulates the same effective width as 400% zoom on a standard display and tends to be faster for iterating through a whole site.
- Look for overlapping or clipped content. Not just scrolling — check whether text gets cut off by a fixed header, whether buttons overlap text, or whether a dropdown menu covers content it shouldn't.
- Test your forms specifically. Input fields with fixed widths are a frequent, easy-to-miss failure point.
If you want a faster sanity check across your whole site rather than page by page, running a free WCAG scan will flag reflow and resize issues alongside the other 32 checks it runs, so you're not hunting for this one in isolation.
What's the actual code fix for reflow failures?
Mostly it comes down to replacing fixed units with flexible ones, and making sure your layout uses wrap behavior instead of rigid rows. A few concrete examples:
Fixed-width container, before:
.container {
width: 1200px;
}
After:
.container {
max-width: 1200px;
width: 100%;
box-sizing: border-box;
}
Card row that doesn't wrap, before:
.card-row {
display: flex;
}
.card {
width: 380px;
}
After:
.card-row {
display: flex;
flex-wrap: wrap;
gap: 16px;
}
.card {
flex: 1 1 280px;
}
Media that blows out the layout, before:
img, iframe {
width: 1000px;
}
After:
img, iframe {
max-width: 100%;
height: auto;
}
For text resize specifically (a related but separate criterion, 1.4.4), the fix is usually about avoiding hardcoded pixel font sizes in places where a user's browser-level zoom should scale things proportionally, and making sure containers around text use em, rem, or percentage-based sizing rather than fixed pixel heights that clip overflowing text.
Does reflow affect anything beyond accessibility compliance?
Yes — and this is the part that gets overlooked. A layout that can't reflow cleanly is also a layout that's harder for a browser engine, and by extension an AI crawler, to parse into a clean linear structure. If your content's visual order depends entirely on fixed pixel positioning rather than logical source order, you're creating the same kind of structural ambiguity that trips up screen readers and confuses tools like ChatGPT or Perplexity when they try to extract your content accurately. Our guide on AI readability gets into this overlap in more detail — clean, logical structure tends to serve both audiences at once.
There's also a plain business case. Low vision affects an estimated 2.2 billion people worldwide according to WHO estimates, and browser zoom is one of the most common adaptive strategies people use — far more common than switching to a dedicated screen reader. If your checkout flow breaks at 400% zoom, you're not failing an audit in the abstract. You're losing real customers at the exact moment they're trying to give you money.
What's the difference between reflow failures and text resize failures?
Reflow (1.4.10) is about layout — whether content restacks into one column and avoids horizontal scrolling at a 320px-equivalent width. Text resize (1.4.4) is about whether users can scale text up to 200% using browser zoom without losing content or functionality. They're closely related and often fail together, but they're tested a little differently.
A site can pass text resize (text scales up fine, nothing clips) while still failing reflow (the layout doesn't restack, so you get horizontal scrolling). This combination is easy to end up with if you use responsive typography but never test your grid system past tablet width. Conversely, a site can have decent reflow behavior but still clip text in small fixed-height buttons or badges — the text scales, the box doesn't, and you end up with truncated labels. Worth testing both independently rather than assuming one guarantees the other.
How do I prevent this from happening again?
Build the 400% zoom check into whatever your normal QA process already is, not as a separate accessibility pass that happens once a year before an audit.
A few habits that actually stick:
- Default to
max-widthinstead ofwidthfor containers, as a team-wide convention. - Use
flex-wrap: wrapor CSS Grid'sauto-fit/auto-fillfor any row of repeating elements — cards, product tiles, testimonial blocks. - Test new page templates at 320px viewport width before they ever reach a staging review, not after.
- Avoid nesting fixed pixel widths more than one level deep in your component library — it compounds fast and gets hard to trace.
None of this is exotic. It's mostly just discipline about which CSS units you reach for by default, which honestly most teams can fix within a sprint once they know where to look.
Frequently Asked Questions
What zoom percentage does WCAG 1.4.10 actually require?
WCAG 1.4.10 requires content to work at a viewport equivalent to 320 CSS pixels wide, which corresponds to 400% zoom on a standard 1280px-wide desktop display. Mobile and narrow viewports are generally already close to this width, which is part of why mobile-first responsive sites often pass this check more easily than desktop-first ones.
Does horizontal scrolling always fail WCAG reflow checks?
Not always. Horizontal scrolling is permitted for content where a two-dimensional layout is essential to understanding — data tables, maps, diagrams, and similar content types are exempt. But horizontal scrolling on a standard page layout, navigation bar, or body text block is a failure under 1.4.10.
Can I fix reflow issues without a full redesign?
In most cases, yes. Reflow failures are usually CSS-level problems — fixed widths, missing flex-wrap properties, hardcoded pixel values on images or containers. These are targeted fixes, not structural redesigns, and a developer can typically resolve the common cases within a few hours per template.
Is reflow a WCAG Level A or Level AA requirement?
Reflow (1.4.10) is a Level AA success criterion. Most ADA-related legal settlements and state-level accessibility requirements in the US reference WCAG 2.1 Level AA as the practical compliance standard, so this one matters for legal exposure, not just user experience.
How is reflow different from responsive design?
Responsive design is a broader design approach; reflow is a specific, testable accessibility requirement within it. A site can be "responsive" in the general sense — it adapts at common breakpoints like tablet and mobile — while still failing reflow at the specific 400% zoom / 320px threshold WCAG tests for, especially if that exact width wasn't part of the original breakpoint plan.
Do screen readers care about reflow failures?
Not directly — reflow is primarily a low-vision and zoom-based need, not a screen reader issue. But the underlying causes (fixed widths, non-semantic layout structures) often overlap with problems that do affect screen readers and AI crawlers, like unclear reading order or content that's visually present but structurally disconnected from where it appears on the page.
Next step
Open your homepage right now, zoom your browser to 400%, and scroll down. If you hit a sideways scrollbar anywhere, you've found your first fix. For a broader pass across all 33 WCAG checks — including reflow, text resize, and the structural issues that also affect AI search visibility — run a free scan at AccessKnight and you'll get code-level fixes for whatever turns up, not just a list of what's broken.
Fix guides for this topic
Step-by-step fixes with copy-paste code for the checks this article covers.
- Viewport disables user scalingWCAG 1.4.4 · Level AAW3C: Understanding 1.4.4
Check your website's accessibility
Scan against all 33 WCAG 2.1 rules and get code-level fix suggestions — free.
Run a free scan →