01 — Purpose

Targets you can hit

Touch targets affect usability constantly on mobile — interactive targets should remain large enough to activate reliably.

Tiny links, packed icon rows, and overlapping tap zones cause missed taps, frustration, and accidental activation. Prefer a hit area of at least 44×44 CSS pixels for buttons and other standalone controls. This is our design target; WCAG's minimum depends on the conformance level and applicable exceptions.

WCAG 2.2 SC 2.5.8 (AA) requires 24×24 CSS pixels, subject to exceptions. The 44×44 CSS pixel requirement belongs to SC 2.5.5 (AAA), which also has exceptions. Meeting either size criterion alone does not establish conformance with the whole standard.

See mobile navigation and responsive strategy.

02 — Principles

Reliable interaction zones

Interaction should feel reliable — not delicate.

  • adequate spacing — gap between adjacent targets, not edge-to-edge icons
  • comfortable target size — aim for 44×44 CSS pixels, including padding
  • predictable interaction zones — whole row tappable where users expect it

03 — Practice

Good touch target standards

Touch usability affects motor-impaired users, mobile users, and temporary impairments.

For the AA spacing exception, centre an imaginary 24 CSS pixel diameter circle on each undersized target's bounding box. It must not intersect another target or the circle around another undersized target. A fixed gap such as 8px is not the test.

Other AA exceptions cover equivalent controls on the same page, inline targets in text, unmodified browser controls, and essential target sizes. Check the criterion before claiming an exception; inline links can still benefit from readable line spacing.

  • expand hit area with padding — visual icon can be smaller if tap zone is sufficient
  • size primary actions generously — submit, add to cart, menu toggle
  • avoid nested tappable elements — button inside link causes mis-taps
  • test on real devices — thumb reach and one-handed use on narrow viewports
  • pair with visible focus for keyboard — see keyboard navigation

04 — Avoid

Tiny, packed controls

Accidental activation and missed taps erode trust on mobile.

  • tiny buttons — 24px icons with no padding in toolbars
  • tightly packed controls — delete next to edit with no spacing
  • accidental activation risk — destructive action too close to primary tap
  • hover-sized desktop targets shipped unchanged on mobile
  • text links in dense paragraphs with no line-height or padding relief

05 — Close

Measure the tap zone, not just the icon

If you struggle to hit it on a phone, your users struggle too.

Audit navigation, forms, and data tables on a phone. Flag controls below the preferred 44×44 CSS pixel target for a usability review. Assess WCAG size and spacing separately, including any applicable exceptions. Fix repeated problems in design tokens and component defaults.

See mobile navigation, zoom and reflow, and accessibility QA checklist.