meta-viewport · WCAG 1.4.4 Resize Text · Level AAHow to fix the “meta-viewport” accessibility issue
The axe-core meta-viewport rule fails when the viewport meta tag disables zoom with user-scalable=no or a low maximum-scale. That blocks pinch-zoom on mobile, which low-vision users rely on. WCAG 2.2 (1.4.4, Level AA) requires text to be resizable.
What axe-core checks
axe-core fails a <meta name="viewport"> containing user-scalable=no, user-scalable=0, or maximum-scale below 2.
Which standard this maps to
| WCAG 2.2 | 1.4.4 Resize Text (Level AA) |
| EN 301 549 | 9.1.4.4 |
| BFSG / EAA | BFSG § 12 via EN 301 549 · EAA Annex I |
| Category | Zoom & Reflow |
Why it matters
Many shops copy a viewport tag that locks zoom to stop “layout jumps”. The side effect is that a low-vision shopper on a phone cannot enlarge the price or the small print — an AA failure that is invisible until someone needs it.
Common causes
user-scalable=nocopied from an old templatemaximum-scale=1locking zoom- A framework default that disables scaling
- Disabling zoom to “fix” an input-focus zoom on iOS
How to fix it
Remove user-scalable=no and any maximum-scale below 2 (or 5). Let users zoom.
<!-- Fails -->
<meta name="viewport" content="width=device-width, user-scalable=no">
<!-- Passes -->
<meta name="viewport" content="width=device-width, initial-scale=1">FAQ
A responsive layout should reflow under zoom. If zoom breaks it, the layout — not zoom — is the bug to fix.
Set the input font-size to at least 16px; that stops iOS auto-zoom without disabling user zoom.
Find every issue like this on your site
Run a free WCAG 2.2 AA scan — real axe-core engine, no signup. Or get a timestamped evidence report for €29.