Is Your Website Accessible on a Phone? A Non-Developer's Guide to Mobile Web Accessibility

Here is a number that surprises a lot of business owners: for most small websites, well over half of all visitors arrive on a phone. For some industries — restaurants, local services, retail — it is closer to 70 or 80 percent. Yet when people worry about accessibility, they almost always picture someone at a desktop computer. The reality is that the majority of your visitors with disabilities are also on phones, using a small touchscreen, sometimes with a screen reader turned on, sometimes with the text cranked up to twice its normal size, sometimes with shaky hands or limited fine motor control.

Mobile accessibility is not a separate, more advanced version of accessibility. It is the same set of ideas — can people perceive your content, operate your buttons, and understand your pages — applied to the device where most of your traffic actually happens. The good news is that you do not need to be a developer to spot the most common mobile problems. You just need to know what to look for and how to test it on the phone that is almost certainly in your pocket right now.

Why mobile gets missed

Websites are usually designed and reviewed on big monitors. A designer builds a page on a 27-inch screen, it looks great, everyone approves it, and nobody thinks to check what happens when that same page is squeezed onto a 6-inch phone held by someone who taps with one thumb while walking. The desktop version can be perfectly accessible while the mobile version quietly falls apart.

The other reason mobile gets missed is that automated scanners — the free tools that give you a score — typically test a desktop-sized version of your page. They are useful, but they will not tell you that your buttons are too small to tap reliably, that your menu traps a screen reader, or that a visitor cannot zoom in to read your fine print. Those are things a human has to check on an actual phone.

The seven mobile problems that matter most

You do not need to memorize the whole accessibility standard. On mobile, a handful of issues cause the overwhelming majority of real-world frustration. Here they are in plain English.

1. Tap targets that are too small or too close together

If your buttons, links, and icons are tiny, people with larger fingers, tremors, or limited dexterity will miss them and tap the wrong thing. The accessibility guidelines (WCAG 2.2, criterion 2.5.8) recommend that interactive targets be at least 24 by 24 pixels, and most usability experts push for 44 by 44 — roughly the size of a fingertip. Watch out especially for clusters of small links jammed together, like social media icons in a footer or a row of tiny “x” close buttons.

How to check: On your phone, try tapping every important button using only your thumb, quickly, the way a real person does. If you keep hitting the wrong one, they are too small or too close.

2. Content that will not reflow — so you have to scroll sideways

A well-built mobile page stacks its content into a single column that fits the screen. A poorly built one keeps a desktop layout and forces you to scroll left and right to read a single sentence. Horizontal scrolling is miserable for everyone and genuinely disabling for people who zoom in. WCAG calls this “reflow” (criterion 1.4.10): content should adapt to a narrow screen without requiring two-directional scrolling.

How to check: Load your site on a phone and read a few pages. If you ever have to swipe sideways to see the rest of a line of text or a button, you have a reflow problem.

3. Pinch-to-zoom disabled

Some sites deliberately switch off the ability to pinch and zoom, usually because a developer thought it made the layout look tidier. For a person with low vision, that is like locking the magnifying glass in a drawer. Blocking zoom is one of the most common and most harmful mobile accessibility mistakes, and it is entirely avoidable.

How to check: Open a page and try to pinch-zoom into the text. If nothing happens, zoom has been disabled and needs to be turned back on. (We cover this in depth in our guide on disabled pinch-zoom.)

4. Text that cannot grow

Phones let people increase the system text size for readability. Good websites respect that setting and grow with it. Fragile ones either ignore it or break — text overflows its box, gets cut off, or overlaps other content.

How to check: In your phone settings, turn the text size up to a large setting, then reload your site. Everything should still be readable and nothing should be clipped or overlapping.

5. Menus and pop-ups that trap you

The mobile “hamburger” menu (the three-line icon) and pop-ups like newsletter offers and cookie banners are the two places where mobile accessibility most often collapses. A menu that a screen reader user cannot open, or a pop-up with a close button too small to tap or impossible to reach with the keyboard, can stop a visitor cold.

How to check: Open your menu and every pop-up on a phone. Can you clearly find and tap the close button? Does anything cover the whole screen with no obvious way out?

6. Forms that fight your thumbs

Filling out a form is hard enough on a phone. It gets harder when fields are tiny, labels disappear as soon as you tap in, error messages show up far away from the field that caused them, or the wrong keyboard pops up (a text keyboard when you are typing a phone number). Since forms are usually where the money is — checkout, booking, contact — mobile form problems cost you real customers.

How to check: Complete your own contact or checkout form on a phone, start to finish. Note anywhere you squint, mis-tap, or get confused by an error.

7. Things that only work by swiping or tilting

Some features rely on gestures that not everyone can perform — a carousel you can only advance by swiping, a control that only responds to shaking or tilting the phone. WCAG (criteria 2.5.1 and 2.5.4) says these need a simple alternative, like visible arrow buttons. If a feature can only be operated one way, some people cannot use it at all.

How to check: For any slider, carousel, or gesture-based feature, look for buttons that do the same job with a plain tap. If tapping is not an option, that is a barrier.

A 15-minute mobile test anyone can run

You do not need special software. Pick up your phone and do this:

  1. Turn your text size up in your phone’s settings, then load your homepage and two key pages (a product or service page, and your contact or checkout page).
  2. Try to pinch-zoom on each page. It should work.
  3. Read each page top to bottom. You should never have to scroll sideways.
  4. Tap every important button with your thumb, quickly. Note anything you miss or hit by accident.
  5. Open your menu and every pop-up. Find and tap the close button on each.
  6. Fill out your main form completely and submit it.
  7. Turn on your phone’s screen reader — VoiceOver on iPhone, TalkBack on Android — and swipe through your homepage listening. Do the buttons and links announce something meaningful, or do you hear silence, “button,” or a jumble? (Our guide to testing with VoiceOver, no coding required, walks through this step by step.)

Write down everything that felt awkward. That list is your mobile accessibility to-do list, in priority order, and you built it in a quarter of an hour without a single line of code.

iPhone and Android are not the same

One more thing worth knowing: the two phone ecosystems handle accessibility slightly differently. iPhones ship VoiceOver on every device and behave very consistently, which makes them the easiest platform to test against. Android, with its many manufacturers and versions, is more varied — a page that reads perfectly on one Android phone might stumble on another. If your audience leans one way or the other, test on that platform first, but ideally check at least one of each. We compare the two in detail in iOS vs Android accessibility.

What to hand your developer

If your test turns up problems you cannot fix yourself, you do not have to diagnose the code. Just hand your developer or web builder the specific, plain-English list: “The close button on the newsletter pop-up is too small to tap.” “I can’t pinch-zoom on the pricing page.” “The phone number field brings up a letter keyboard instead of a number pad.” “The menu doesn’t announce anything with VoiceOver.” Concrete observations tied to a real device are far more actionable than “make it accessible,” and they let a good developer go straight to the fix.

Mobile accessibility is not a niche concern or a nice-to-have. It is where most of your visitors — and most of your visitors with disabilities — actually meet your business. The barriers are usually small, specific, and fixable, and you can find most of them yourself in the time it takes to drink a coffee.

We’re building a simple accessibility checker for non-developers — no DevTools, no jargon. Join our waitlist to get early access.