How do I use my mobile browser to zoom? Measured on a phone, with the method

How do I use my mobile browser to zoom? Two controls, one threshold (200%)

You have a casino rules page open on your phone, and the small print is too small to read. How do I use my mobile browser to fix that? Pinch the page with two fingers, or raise the browser’s own zoom setting.

Either way, the test is the same. At 200%, nothing on the page should be lost.

That threshold is not ours. It comes from WCAG 2.2, the W3C’s web accessibility standard, and we read it again on 23 September 2026.

Below are the controls for Safari on iPhone and Chrome on Android, in the words of Apple’s and Google’s own help pages. Every check here runs on public pages, logged out. No operator is measured or ranked.

Sources: W3C: Resize Text; Apple: Safari settings on iPhone; Google: Chrome zoom on Android.

Safari on iPhone — Page Zoom, 3 taps from the page

Apple’s iPhone User Guide puts the control next to the address. Tap the button on the left side of the search field, then tap Page Zoom. Tap the large A to make the text bigger, or the small A to make it smaller.

Apple files these steps under making content larger or smaller for a website. So the change is for the site you are on, not every site. A small indicator shows briefly when the size returns to 100%.

That is 3 taps to the first step up. We counted them from the steps as Apple publishes them. It is not a timed run on a phone.

Sources: Apple: Safari settings on iPhone.

Chrome on Android — Default zoom for every page, Page Zoom for one

Google’s Chrome help gives two routes. For every page, open Chrome and tap More at the top right. Then tap Settings, then Accessibility, and move the slider next to Default zoom until the preview text is easy to read.

For one site, tap More, then Zoom, and use the slider. Google’s tip says the level will be saved for that site and will not affect other sites. The Zoom item only appears in the menu after you turn on Show zoom option in main menu, on the same Accessibility screen.

That screen holds one more switch. Google’s wording is: ‘To zoom in on pages that prevent zoom, turn on Force-enable zoom.’ It matters for one reason, and a later section explains it.

Sources: Google: Chrome zoom on Android.

Font size or the whole page — 2 kinds of zoom, 2 results

The two browsers do not enlarge the same thing. Apple’s steps describe Page Zoom as a way to increase the font size. Google’s page describes Chrome’s zoom as a way to make everything on a web page larger or smaller.

W3C’s notes on text size name both kinds. They list zoom of the whole page, magnification, text-only resizing and a set size for text as ways a browser can scale content.

So the same casino page can pass on one phone and fail on another. A layout that copes with bigger text may still break when every box grows with it. Record which kind of zoom you used, every time.

Sources: Apple: Safari settings on iPhone; Google: Chrome zoom on Android; W3C: Resize Text.

Text size — 200% (threshold from WCAG 1.4.4)

The first threshold is about text. It is short enough to quote in full, and the quotation below does so.

W3C’s own notes say that scaling content is mainly the job of the user agent. In plain terms, that means the browser. So the zoom controls above are the right tools for this test.

The pass line is simple. At 200%, every sentence and control that was there at 100% must still be there and still work. Text that is cut off, lines that overlap, or a button that has gone is a fail.

Sources: W3C: Resize Text.

Page width — 320 CSS px with no sideways scrolling (WCAG 1.4.10)

WCAG 2.2’s reflow criterion addresses content at a width equivalent to 320 CSS pixels for vertically scrolling pages, with exceptions for content that needs a two-dimensional layout.

W3C gives the scale. A width of 320 CSS pixels is the same as a window 1280 CSS pixels wide at 400% zoom. Our phone view is 390 CSS pixels wide, so the page must still work when narrowed further.

The exceptions matter on a casino site. W3C’s list names maps, diagrams, video, games and data tables.

A game board may raise different layout questions from its surrounding rules or account information. State which part of the page was examined.

Sources: W3C: WCAG 2.2; W3C: Reflow.

Zoom blocked — the viewport tag decides (2 expectations)

A page can stop pinch-zoom with one line of code. It is called the viewport meta tag, and it sits in the page’s header where you cannot see it.

W3C has a test rule for it, called Meta viewport allows for zoom. It fails a tag that sets user-scalable to no. It also fails a tag that sets maximum-scale below 2, because that caps zoom under 200%.

A tag with maximum-scale=2.0 passes, and the rule uses it as one of its own examples.

The rule is careful in one respect. A page that fails it may still meet the 200% and reflow criteria by other means. So a blocked tag is a finding to record, not a verdict on its own.

On Android, Chrome’s Force-enable zoom is the way round a blocked tag. The Safari help page we read does not describe a matching switch. On an iPhone, the phone’s own Zoom is the fallback, and the next section covers it.

Sources: W3C: viewport zoom rule; Google: Chrome zoom on Android; Apple: Safari settings on iPhone.

When the page will not zoom — the phone’s own Zoom (iPhone)

There is one more tool if a page blocks pinch-zoom on an iPhone. Apple’s iPhone User Guide describes a Zoom feature that can magnify the screen no matter what you are doing.

Go to Settings, then Accessibility, then Zoom, and turn it on. Then double-tap the screen with three fingers. You can magnify the entire screen or just part of it with a movable lens, and you move around by dragging with three fingers.

This enlarges the screen, not the page. The page does not rewrap its text, so it is a fallback for reading, not a pass on the 200% test.

Sources: Apple: Zoom on iPhone.

What should survive the zoom — the reading task

A mobile review can begin with an ordinary task: find the game’s rules, enlarge the text, and return to the same place. Check whether a heading, a payout condition, and the close control remain available.

The purpose is to understand how the interface behaves, not to assume that a polished opening screen guarantees usable detail pages.

Rules pages matter for a reason set in regulation. RTS 3 (one of the Gambling Commission’s remote technical standards) says an explanation of the rules must be easily available to the customer before they commit to gamble. If you need 200% to read it, zoom is how you reach it.

Sources: Gambling Commission: RTS 3.

The deposit-limit link at 200% — visible or not

One control deserves its own check. RTS 12, the Commission’s technical standard on financial limits, says financial limit facilities ‘must be provided via a direct link on the homepage and be clearly visible and accessible’.

The same standard says the system ‘must minimise the number of clicks or pages customers make in order to access financial limit facilities’. Zoom can undo that. At 200%, a menu may fold away or move the link off the screen.

So open the public homepage, zoom to 200%, and look for the link. Record whether it is visible and where it leads when tapped. Logged out, it may lead to a sign-in page; record that and stop there.

How many taps a control takes matters most on the night you need it. If that night is now, GamCare is on 0808 8020 133 and GamStop is at gamstop.co.uk.

Sources: Gambling Commission: RTS 12; Gambling Commission: self-exclusion; GamStop.

Method: repeat this on your own phone

If you have been asking how do I use my mobile browser to read small print, the six steps below are the whole answer. They use only the phone and the browser already on it, and each step ends with something written down.

What the result means: a pass says the page kept its words and controls at your size, on that day, on that phone. A fail names the item that was lost. Neither result says anything about the games or the operator’s licence.

Keep a precise record — one row per measure

Note the viewport, zoom setting, orientation, and any obscured text or control. Distinguish a design limitation from an issue you could not reproduce.

A reader can learn more from one clearly documented example than from an unexplained mobile score attached to an entire casino. The sheet below keeps each finding as one row, with its threshold and where that threshold comes from.

What this inspection did not cover

This note measures the browser. It does not test text size inside an installed app, where the phone’s own text setting does that job. The scored app-versus-browser sheet covers both routes side by side.

Button size is measured separately, with its own threshold. So is one-handed reach, the question of which controls sit under your thumb.

No operator was measured for this note, so it names none and ranks none. When the lab publishes a zoom result, it will carry the filled-in sheet and the date.