FluxPress ![[user-scalable=no] maximum-scale Viewport](https://fluxpress.io/wp-content/uploads/2026/06/user-scalableno-maximum-scale-Viewport.png)
This warning means your viewport meta tag disables pinch-to-zoom, which blocks low-vision users from enlarging text. Fix it by removing user-scalable=no and any maximum-scale below 5 from the viewport tag, leaving width=device-width, initial-scale=1 so visitors can zoom freely.
The Lighthouse accessibility warning “[user-scalable=no] is used in the <meta name=viewport> element” — or a related note that maximum-scale is less than 5 — flags a small piece of code with a real-world cost: it stops people from zooming in on your pages. This guide explains why that fails accessibility and how to fix it in WordPress.
What the warning means
Every responsive site has a viewport meta tag in its <head> that tells mobile browsers how to size the page. Some themes and plugins add attributes that disable zooming, either with user-scalable=no or by capping maximum-scale at a low value like 1. The intention is usually to make the site “feel like an app.” The problem is that disabling zoom prevents low-vision users from enlarging text and content to read it — a significant accessibility barrier, which is why Lighthouse and the WCAG guidelines flag it.
What a correct viewport tag looks like
A problematic viewport tag looks like one of these:
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no">
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">The fix is to remove the zoom-blocking parts, leaving a clean, accessible tag:
<meta name="viewport" content="width=device-width, initial-scale=1">This still makes your site fully responsive — it simply lets visitors pinch-to-zoom if they need to. If you must set a maximum, keep it at 5 or higher so meaningful zoom is still possible.
Where it comes from in WordPress
You probably did not write this tag yourself. It usually originates from:
- Your theme’s
header.phpor a theme setting that outputs the viewport tag. - Page builders — some mobile/responsive settings inject
user-scalable=no. - Older plugins aiming for an “app-like” mobile feel.
Because the tag is generated by the theme or a plugin, the durable fix is not to hack a template that an update will overwrite, but to correct the output cleanly.
How to fix it in WordPress
- Find the source. Check your theme’s header template and your page-builder’s responsive settings for a viewport tag containing
user-scalable=noor a lowmaximum-scale. - If it is a theme setting, change it to allow scaling, or override the viewport tag from a child theme.
- If it is injected by a plugin or builder, look for the option that controls it, or use a tool that corrects the viewport output site-wide.
- Re-run Lighthouse and test on a phone — you should now be able to pinch-to-zoom.
Easy Optimizer includes a viewport accessibility fix that corrects the viewport meta tag automatically, re-enabling zoom without editing theme files — so the warning clears even when the offending tag comes from a theme or builder you cannot easily change.
Part of a bigger accessibility picture
The viewport warning is one of a small set of Lighthouse accessibility issues common to WordPress sites. Clearing it alongside buttons without an accessible name and links without a discernible name resolves the bulk of them in one pass. And because a zoomable, well-structured page is easier for everyone — including the AI agents that now read your site — to use, these fixes feed directly into accessibility for AI agents too.
What does the “user-scalable=no” warning mean?
It means your viewport meta tag disables pinch-to-zoom on mobile, which prevents low-vision users from enlarging your content to read it. Lighthouse and WCAG flag it because zoom must remain available for accessibility.
Why is disabling zoom bad for accessibility?
Many people rely on zooming to read small text comfortably. Blocking it with user-scalable=no or a low maximum-scale removes that ability, creating a barrier for users with low vision. Allowing zoom is a basic accessibility requirement.
What’s the correct viewport meta tag?
Use content=”width=device-width, initial-scale=1″ without user-scalable=no. This keeps your site responsive while letting visitors pinch-to-zoom. If you set a maximum-scale, keep it at 5 or higher so meaningful zoom is still possible.
Will allowing zoom break my responsive design?
No. width=device-width, initial-scale=1 keeps your layout fully responsive. Removing user-scalable=no only restores the ability to zoom — it doesn’t change how your site lays out at normal scale.
Where is the viewport tag set in WordPress?
Usually in your theme’s header template or a theme setting, and sometimes injected by a page builder’s responsive options or an older “app-like” plugin. Correct it at the source or override it rather than editing a template that updates will overwrite.
Can a plugin fix the viewport warning automatically?
Yes. Easy Optimizer’s viewport accessibility fix corrects the viewport meta tag to re-enable zoom without editing theme files, clearing the warning even when the tag comes from a theme or builder you can’t easily change.
