How to Fix "Zooming Disabled" in the Viewport Meta Tag
This check fails when your page's viewport meta tag stops visitors from pinch-zooming, either with user-scalable=no or with a maximum-scale value below 5. By the end of this guide you will have found every viewport tag your site outputs, replaced it with a zoom-friendly version, and fixed the iOS input auto-zoom issue that often caused the restriction.

Why it matters
People with low vision rely on pinch-zoom to read text and tap small controls on phones. 4 (Resize Text) requires that content can be enlarged to 200%. A viewport tag with user-scalable=no or maximum-scale=1 blocks this on Android browsers and on many in-app browsers.
axe and Lighthouse flag the tag directly, so it lowers your accessibility score. It is also one of the easiest items for accessibility complaints and legal demand letters to point to. The fix is one line and has no effect on your layout.
What you need
Step-by-step fix
Find every viewport tag on the page
Open a page on your site, open DevTools (F12) and run the snippet below in the Console. It lists every viewport meta tag in the rendered DOM. This catches tags added by themes, plugins, apps and JavaScript, not just the ones in your source files.
Run it on your home page, a product or article page, and any landing page built with a different template.
document.querySelectorAll('meta[name="viewport"]').forEach(m => console.log(m.outerHTML));Identify the values that fail
Look at the content attribute of each tag. The check fails if any of these are true:
- user-scalable=no (or user-scalable=0) is present
- maximum-scale is below 2, which is a serious failure
- maximum-scale is below 5, which is a best-practice failure that this audit also flags
The minimum-scale, width and initial-scale values do not affect this check.
Locate the template that outputs the tag
Search your codebase or theme files for the string viewport. html or a layout partial in static-site generators. If the tag is not in your templates, a plugin, app embed or script is injecting it.
To find it, disable plugins one at a time, or search your JavaScript bundles for user-scalable.
grep -rn "user-scalable\|maximum-scale" ./ --include=*.{html,php,liquid,js,jsx,ts,tsx}Replace it with the zoom-friendly viewport
Swap the failing tag for the standard version below, inside the <head> of every page template. Simply leaving out maximum-scale and user-scalable is the cleanest fix. If you have a reason to keep maximum-scale, set it to 5 or higher.
<!-- Inside <head> on every template --> <meta name="viewport" content="width=device-width, initial-scale=1">
Fix the iOS input zoom without blocking zoom
Many sites added maximum-scale=1 to stop iPhone Safari from zooming in when a user taps a form field. Safari only does this when the input's font size is below 16px. Set form controls to at least 16px and the auto-zoom stops, with no need to block pinch-zoom.
input, select, textarea {
font-size: 16px; /* or 1rem; prevents iOS focus zoom */
}Check for scripts that rewrite the viewport
Some sliders, map widgets, chat widgets and older mobile-menu scripts change the viewport tag at runtime with setAttribute('content', ...). Reload the page, open a menu or modal, then re-run the Console snippet from step 1. If the content changed, update or configure that script so it stops setting user-scalable or maximum-scale.
Clear caches and re-test the page
Purge your page cache, CDN cache and any theme or plugin minification cache so the new <head> is served. Then run Lighthouse (DevTools → Lighthouse → Accessibility) or axe DevTools on the same URLs you checked in step 1. Finally, pinch-zoom on a real Android phone to confirm the page enlarges.
curl -s https://example.com/ | grep -i 'name="viewport"'
Platform-specific notes
WordPress
The viewport tag usually comes from your theme's header.php, not from SEO plugins. Copy header.php into a child theme (Appearance → Theme File Editor, or via SFTP) and edit the tag there, so theme updates don't undo the fix. With block themes such as Twenty Twenty-Four, WordPress core outputs a correct viewport tag. If yours is wrong, a plugin or page builder is adding it. Search plugin settings for "viewport" or "disable zoom"; some page builders and AMP or mobile plugins have a toggle for this.
Shopify
Go to Online Store → Themes → … → Edit code → layout/theme.liquid and edit the viewport meta tag inside <head>. Also check other layout files, such as layout/password.liquid and any custom alternate layouts. If the tag is correct in the theme but still fails, an app embed may be injecting it. Check Theme settings → App embeds and disable apps one by one to find it.
Next.js
Next.js outputs width=device-width, initial-scale=1 by default. In the App Router (13.4+), look for `export const viewport` or `generateViewport` in layout.tsx or page.tsx and remove the `maximumScale` and `userScalable` properties. In the Pages Router, search _app and _document for a viewport tag inside next/head and edit it there.
Webflow
Webflow adds its own correct viewport tag. If the check fails, someone has pasted a second viewport tag into Site settings → Custom code → Head code, or into a page's custom code. Delete that tag and republish.
Wix
Wix controls the viewport tag and you cannot edit it directly. If the check fails, look for a custom code snippet under Settings → Custom Code, or a third-party embed that injects a viewport tag. Remove it and republish the site.
Check that it worked
✅ How to verify
- Run Lighthouse's Accessibility category. The audit "[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5" should now be in the Passed list.
- Run axe DevTools on each page template. There should be no results for the meta-viewport or meta-viewport-large rules.
- Run the Console snippet from step 1 after the page fully loads. You should see exactly one viewport tag, with no user-scalable=no and no maximum-scale below 5.
- On an Android phone in Chrome, pinch-zoom the page to confirm it enlarges well past 200%.
⚠️ Common mistakes
- Fixing the tag in one template while another layout, such as a checkout, blog or landing-page template, still outputs the old one.
- Adding a new correct viewport tag without deleting the old one, which leaves a failing duplicate in the <head>.
- Changing maximum-scale=1 to maximum-scale=2 or 3. That clears the serious failure but still fails the below-5 best-practice check.
- Replacing the meta tag restriction with CSS touch-action: none or gesture-blocking JavaScript, which still prevents zoom.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
Does iOS Safari ignore user-scalable=no?
Since iOS 10, Safari mostly lets users pinch-zoom even when user-scalable=no is set. Chrome on Android, many in-app browsers and other platforms still honour it, and automated audits flag it either way. Remove it.
Will removing maximum-scale break my mobile layout?
No. maximum-scale only limits how far a user can zoom in. Your responsive layout depends on width=device-width and initial-scale=1, which you keep. The page looks the same until someone chooses to zoom.
How do I stop iPhone from zooming into form fields without disabling zoom?
Set the font-size of input, select and textarea elements to 16px or larger. iOS Safari only auto-zooms on focus when the field's text is smaller than 16px.
Is maximum-scale=5 acceptable?
Yes. A maximum-scale of 5 or higher passes both the meta-viewport and meta-viewport-large checks. Leaving maximum-scale out entirely is simpler and passes as well.
How to Fix Positive tabindex Values for Keyboard Users
How to Fix "Frames Have Titles": Add Iframe Title Attributes
How to Fix Missing Video Captions on Your Website
How to Fix List Structure Errors in HTML (ul, ol, dl)
How to Fix WCAG 2.2 AA Accessibility Violations on Your Site
How to Fix Duplicate Element IDs for Accessibility