Fix guide · Zoom turned off

How to fix “Zooming and scaling must not be disabled”

By · Updated

The page's viewport tag stops people from zooming in on a phone. Remove user-scalable=no and any maximum-scale below 2 from the meta viewport tag.

axe rule
meta-viewport
WCAG
1.4.4 Resize text (Level AA)
Lighthouse
Google Lighthouse and PageSpeed Insights report it as “[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.”

What it means

The meta viewport tag tells phones how to size the page. Some themes add user-scalable=no or maximum-scale=1 to stop the page from zooming, which also stops people who need bigger text from pinching to zoom.

W3C's Resize Text criterion asks that text can be enlarged to 200 percent without losing content. axe fails the tag when zoom is off or maximum-scale is under 2. Google Lighthouse is stricter and flags anything under 5, so the simplest fix is to leave maximum-scale out.

Who it affects

People with low vision, older visitors, and anyone reading small print on a phone.

How to find it

  1. Run the free checker. If it fails, it fails once for the page.
  2. Or view the page source and search for name="viewport".

How to fix it

  1. Change the tag to the standard line below.
  2. If the tag is written by your theme, it's in the theme's header template. Change it in a child theme or ask the theme's maker, so an update doesn't undo it.

The viewport tag

Before · fails
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
After · fixed
<meta name="viewport" content="width=device-width, initial-scale=1">

What a scanner can and can’t tell you

Fixing this clears one automated check. It doesn’t mean the page is accessible, and it doesn’t settle any legal question. Automated tests catch only part of the problems. W3C puts it plainly: evaluation tools “can not determine accessibility, they can only assist in doing so.” The rest takes a person working through the site with a keyboard and a screen reader.

Source: W3C WAI, Selecting Web Accessibility Evaluation Tools. Not legal advice.

Sources

All checked November 8, 2026. The rule wording is axe-core 4.14.0’s own.

Related fixes

Every fix guide →

Check a page for free

Scan any page of your site against WCAG 2.1 AA in about 30 seconds. You get the problems automated testing finds, in plain words, with a link to a fix guide for the common ones.

Run the free checkno sign up · one page at a time

Rather have someone fix it for you? Tell me about your site.