Disabled Pinch-to-Zoom: Why maximum-scale=1 Should Never Ship

Pinch-to-zoom is a core accessibility feature built into every mobile browser — it's how someone with low vision enlarges text that's otherwise too small to read, with zero effort from the site itself. A small number of viewport meta tag configurations disable this entirely, and every one of them fails WCAG for no real benefit.

This is WCAG Success Criterion 1.4.4 (Resize Text), Level AA.

The failure pattern

<!-- Disables pinch-to-zoom entirely -->
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">

Both user-scalable=no and maximum-scale=1 (or any maximum-scale value too close to initial-scale) block zooming. This pattern was common in early mobile web development as a way to prevent accidental zoom on double-tap, but it comes at the direct cost of locking out anyone who needs to zoom intentionally.

The fix

Simply remove the zoom-disabling parameters:

<!-- Allows zooming, still sets a sensible initial scale -->
<meta name="viewport" content="width=device-width, initial-scale=1">

There is essentially no modern use case where disabling zoom is worth the accessibility cost — if double-tap-to-zoom is causing a genuine UX problem in your app (common in some highly interactive web-app-style interfaces), the fix is addressing the specific interaction issue directly (for example, via touch-action: manipulation on the relevant elements), not disabling zoom sitewide.

Why this is such a clean pass/fail

Unlike most WCAG checks, this one has no gray area — either the viewport meta tag blocks scaling or it doesn't, and there's no legitimate design reason to block it. This is a one-line fix in a single shared template, with essentially zero downside, and it's one of the highest-leverage single-line changes available on a first audit for any mobile-responsive site still carrying this older pattern.

Official references

• Deque University: meta-viewport