What is the right viewport meta tag?

Use width=device-width with initial-scale=1, and nothing that restricts zoom: . Do not add user-scalable=no or a maximum-scale below 2. That gives a responsive layout while leaving pinch-to-zoom fully available.

How do I let users zoom again?

Remove user-scalable=no and any maximum-scale value from the viewport meta tag, leaving width=device-width, initial-scale=1. Then test on a phone by pinching to zoom, and confirm text reaches at least 200% without content being cut off or overlapping.

Disabling Zoom: Why user-scalable=no Fails Accessibility and How to Fix It

By Site Brace Research · Published June 15, 2026

A page can switch off pinch-to-zoom with one setting in its viewport meta tag - user-scalable=no, or a maximum-scale below 2. When it does, a person with low vision who needs to enlarge the text simply cannot. That fails WCAG Success Criterion 1.4.4 Resize Text (Level AA), which requires text to scale up to 200% without losing content or function. We found it on 20 of the 299 large US home pages we scanned, with law firm sites the worst at one in five. It is one line of code, and removing the restriction is the entire fix.

This is one of the more frustrating failures, because it is almost always pointless. Disabling zoom does nothing for most sites; it is a habit left over from app-style mobile design, or a default copied into a template years ago. But for a user who relies on zoom, the cost is total: they pinch the screen and nothing happens. This page covers what the setting is, who it shuts out, how common it is, and how to remove it for good.

What disabling zoom looks like

The viewport meta tag in a page's <head> controls how the page scales on mobile. The accessible version sets the width and an initial scale and stops there. The inaccessible version adds restrictions:

<!-- Blocks zoom: fails WCAG 1.4.4 -->
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no, maximum-scale=1">

<!-- Accessible: responsive, and zoom stays available -->
<meta name="viewport" content="width=device-width, initial-scale=1">

user-scalable=no turns pinch-to-zoom off entirely. A maximum-scale of 1 (or anything below 2) caps how far a user can enlarge the page, below the level WCAG asks for. WCAG Success Criterion 1.4.4, at Level AA, requires that text resize up to 200% without loss of content or functionality, and MDN's own guidance is blunt about it: disabling zoom "prevents people experiencing low vision conditions from being able to read and understand page content."

Who this shuts out

People with low vision, most directly and most completely. Zoom is how they read text that is too small at its default size. Switch it off and there is no workaround on the page itself.
Older readers, whose near vision and contrast sensitivity decline with age, and who lean on zoom to read comfortably.
Anyone on a small screen reading something dense - a table, fine print, a map label - where enlarging a corner is the natural move.

Unlike a contrast or alt-text problem, which a screen reader or another tool can sometimes work around, a disabled zoom is a hard stop. The capability the user needs has been removed.

How common is it?

In our State of Web Accessibility 2026 study of 299 large US home pages, 20 (7%) blocked zoom in their viewport tag. It clustered on law firm sites, where 9 of 46 (20%) disabled it - the highest of any large sample we measured - and it turned up across other sectors too. The common thread is templates: a theme or a framework default that shipped with user-scalable=no baked in, carried onto site after site without anyone deciding it was needed.

How to fix it

Find the viewport tag. Run a scan, or look in <head> for a <meta name="viewport"> with user-scalable=no or a low maximum-scale.
Remove the restrictions. Delete user-scalable=no and any maximum-scale, leaving content="width=device-width, initial-scale=1".
Check it is not re-injected. Themes, page builders, and some mobile frameworks add the tag themselves. If it comes back after you edit the template, find the setting that adds it.
Test by pinch-zooming on a phone. Confirm the page actually enlarges now.
Confirm 200%. Zoom the text to at least 200% and check nothing is cut off or overlapping, then re-scan.

There is no upside to keep here and no overlay that fixes it - it is a one-line change in your own template. (Overlay widgets do not address it either, and the Federal Trade Commission fined the overlay vendor accessiBe one million dollars in 2025 over its compliance claims. We cover why overlays fall short separately.)

What a scan can and cannot tell you

This is one of the most reliable things an automated scan catches: the zoom setting is right there in the markup, so a tool flags it with no ambiguity. The part that still needs a person is the next step - actually zooming to 200% to confirm the layout reflows cleanly, which is a Reflow and resize check a human does by eye. We report the automated slice; the manual zoom test is part of a full audit.

Common questions

Does user-scalable=no fail WCAG? Yes - it blocks zoom and fails 1.4.4 Resize Text (Level AA).

What is the right viewport tag? <meta name="viewport" content="width=device-width, initial-scale=1">, with nothing that restricts zoom.

Why do sites disable zoom? Habit and copy-paste, usually from app-style templates. It rarely serves a purpose.

How do I let users zoom? Remove user-scalable=no and maximum-scale, then test by pinching on a phone.

Check your own site

Run a free check on your home page and it will tell you in about a minute whether your viewport tag blocks zoom. For the whole site, see what a full audit covers, and how monitoring catches the setting if a theme update slips it back in. For the data behind this page, read the State of Web Accessibility 2026; its companion failures are low color contrast, links without discernible text, and missing alt text.