# Mobile Accessibility: WCAG on Phones and Tablets

Source: https://allyway.ai/glossary/mobile-accessibility

Mobile accessibility means that websites and apps work for people with disabilities on smartphones and tablets – with zoom, screen readers, switch and voice control, external keyboards, in portrait and landscape and without complex gestures.

Mobile accessibility is about one question: can someone with a disability use your website on a phone or tablet? Small screens, touch input, glare outdoors and holding the device in one hand make barriers bigger. A button that is easy to click with a mouse can be impossible to hit with a shaking hand, and a page that blocks zoom shuts out people with low vision.

## What it means

There are no separate mobile guidelines: [WCAG 2.2](https://allyway.ai/regulations/wcag-2-2) applies to mobile websites just like to desktop ones. W3C's Mobile Accessibility Task Force explains how in the draft note [Guidance on Applying WCAG 2.2 to Mobile Applications (WCAG2Mobile)](https://www.w3.org/TR/wcag2mobile-22/), which covers native apps, mobile web apps and hybrid apps. Several criteria added in WCAG 2.1 and 2.2 were written with phones in mind:

| Need on mobile | WCAG criterion | Level | Requirement |
|---|---|---|---|
| Hit buttons reliably | [Target Size](https://allyway.ai/glossary/target-size) 2.5.8 | AA | At least 24 × 24 CSS pixels, or enough spacing |
| Turn the device freely | [Orientation](https://allyway.ai/glossary/orientation) 1.3.4 | AA | Content works in portrait and landscape unless one is essential |
| Zoom without sideways scrolling | [Reflow](https://allyway.ai/glossary/reflow) 1.4.10 | AA | Works at 320 CSS pixels width |
| Enlarge text | [Resize Text](https://allyway.ai/glossary/resize-text) 1.4.4 | AA | Up to 200 % without losing content |
| Avoid complex gestures | [Pointer Gestures](https://allyway.ai/glossary/pointer-gestures) 2.5.1 | A | Swipes and pinches also work with a single tap |
| No shaking or tilting required | [Motion Actuation](https://allyway.ai/glossary/motion-actuation) 2.5.4 | A | A button alternative, and motion can be turned off |

People rely on a lot of built-in tools on their phones: VoiceOver on iPhone and TalkBack on Android read the screen aloud and use their own gestures, Switch Control and Voice Access replace touch entirely, and many users connect an external keyboard. All of them depend on correct names, roles and focus – the same code quality as on desktop.

> **Warning:** > **Never disable zoom**
> W3C's mobile guidance says restrictive values for `user-scalable` and `maximum-scale` in the viewport meta tag should be avoided. Use `<meta name="viewport" content="width=device-width, initial-scale=1">` and nothing that stops pinch-zoom.

## Examples

```html title="Example"
<meta name="viewport" content="width=device-width, initial-scale=1">

<style>
  /* Tap targets: at least 24 × 24 CSS px, comfortably 44 × 44 */
  .icon-button { min-width: 44px; min-height: 44px; }

  /* Don't lock orientation with CSS */
  @media (orientation: landscape) { .gallery { grid-template-columns: repeat(3, 1fr); } }
</style>

<!-- Carousel: swipe works, but buttons are there too -->
<button type="button" aria-label="Previous slide">‹</button>
<button type="button" aria-label="Next slide">›</button>

<!-- The right keyboard for the data -->
<label for="phone">Phone</label>
<input id="phone" type="tel" autocomplete="tel">
```

**Do:** Do

Build responsive layouts that reflow into one column, keep tap targets big enough with space between them, offer buttons for every swipe or drag, support both orientations, use input types like `tel` and `email` for the right on-screen keyboard and keep labels visible above fields.

**Don't:** Don't

Block zoom, lock the page to portrait, hide functions behind multi-finger gestures, place tiny icons right next to each other, or show a different, reduced mobile site that leaves out content.

## How to check mobile accessibility



## Questions

Q: Does WCAG apply to mobile websites?
A: Yes. WCAG is technology-neutral and applies to websites on every device. The W3C draft note WCAG2Mobile explains how WCAG 2.2 also applies to native and hybrid mobile apps.

Q: How big should tap targets be on mobile?
A: WCAG 2.2 criterion 2.5.8 (Level AA) requires at least 24 × 24 CSS pixels or enough spacing around smaller targets. Level AAA criterion 2.5.5 asks for 44 × 44 CSS pixels, which is also a comfortable size for most people.

Q: Is a responsive website automatically accessible on mobile?
A: No. Responsive design helps with reflow, but you still need large enough tap targets, alternatives for gestures, working zoom, both orientations and correct names for screen readers.

Q: Which screen readers are used on phones?
A: VoiceOver is built into iPhone and iPad, TalkBack into Android. Both read the screen aloud and use their own touch gestures, so test with them on a real device.

Q: How can I find mobile accessibility issues quickly?
A: Combine a manual test on a real phone with an automated check. The free [WCAG scanner](https://allyway.ai/free-wcag-accessibility-scanner-for-websites) checks your homepage for common issues such as missing labels and low contrast.
