Mobile & Touch
Touch Target Sizing
Tap targets need to be big enough, and spaced enough, to hit reliably with a finger.
Where it comes from
It's grounded in WCAG 2.2's target-size criteria and platform guidelines. WCAG 2.2 sets a 24×24px minimum at Level AA (with a spacing exception), the stricter AAA criterion asks for 44×44px, and Apple's guidelines recommend 44×44pt.
Why it matters for your website
Fingers aren't cursors. Targets that are too small or too tightly packed cause mis-taps and frustration on mobile. WCAG 2.2 sets a 24×24px minimum at Level AA (with a spacing exception), the stricter AAA criterion asks for 44×44px, and Apple's guidelines recommend 44×44pt — so 44px-plus, with breathing room, is the safe target for anything important.
A fingertip is a blunt instrument — roughly a centimetre across — and nothing like a precise cursor. Targets that are too small, or packed too tightly together, cause mis-taps and frustration on mobile, and a missed tap on an important control is a lost action.
The standards converge on a practical rule: while WCAG 2.2 AA permits 24×24px with adequate spacing, the safer target for anything important is 44px-plus with breathing room around it, matching the stricter AAA criterion and Apple's long-standing guidance.
Wrong vs right
Tap targets sized at 24px or less, packed tightly together, causing frequent mis-taps on mobile.
Targets of 44px or more with clear spacing between them, easy to hit reliably with a finger.
An important mobile action sized like body text, too small to tap accurately.
Primary actions given generous, finger-friendly size and spacing.
Multiple small links crowded together, where the wrong one is easily tapped.
Adequate spacing between targets so each can be hit without catching its neighbour.
Understanding Touch Target Sizing
Touch target sizing is the principle that tap targets must be large enough, and spaced enough, to hit reliably with a finger. It's a direct consequence of physiology: a fingertip is roughly a centimetre of contact, far less precise than a mouse cursor, so targets that work on a designer's monitor can be near-impossible on a phone.
The standards give concrete numbers, and they differ. WCAG 2.2 sets a minimum of 24×24px at Level AA (with an exception where there's enough spacing); the stricter AAA criterion asks for 44×44px; and Apple's human-interface guidelines have long recommended 44×44pt. They converge on a safe practical rule: 44px-plus, with breathing room, for anything important.
Getting this wrong is a common and costly mobile failure. Targets that are too small or too tightly packed cause mis-taps and frustration, and a missed tap on a 'Buy' or 'Continue' button is an action — sometimes a sale — you nearly had. It's a direct application of Fitts's Law to touch, and it connects to the thumb zone and accessibility.
How Kweri checks it
Touch target sizing is one of the more directly measurable principles, and Kweri assesses it concretely: it can measure the rendered size of tap targets and the spacing between them, and flag those that fall below the recommended minimums or sit too close together to hit reliably. There's relatively little judgement involved — the metric is observable in the rendered page. So Kweri reliably catches undersized and crowded touch targets against the WCAG 2.2 and platform thresholds, making this one of the clearer automated checks, with the caveat that which targets are 'important' enough to need the larger size is a design call.
FAQ
How big should touch targets be?
WCAG 2.2 sets a 24×24px minimum at Level AA (with a spacing exception), the AAA criterion asks for 44×44px, and Apple recommends 44×44pt. The safe practical target for anything important is 44px-plus, with breathing room around it.
Why do touch targets need to be larger than cursor targets?
Because a fingertip is far less precise than a mouse cursor — roughly a centimetre of contact. Targets that are easy to click with a cursor can be near-impossible to tap accurately with a finger, especially on a small screen.
What's the WCAG 2.2 requirement for target size?
Success Criterion 2.5.8 (Target Size Minimum, Level AA) requires targets to be at least 24×24px, unless there's sufficient spacing around them. The stricter AAA criterion (2.5.5) asks for 44×44px.
What happens if touch targets are too small?
They cause mis-taps and frustration on mobile, and people hit the wrong control or miss it entirely. A missed tap on an important action — a buy or continue button — is a lost action, sometimes a lost sale.
How is touch target sizing related to Fitts's Law?
It's a direct application. Fitts's Law says the time to hit a target depends on its size and distance; on touch, where there's no precise cursor, adequate size and spacing are the difference between a control that works and one that frustrates.
Related principles
The time to hit a target depends on its size and distance — small, far targets are hard to reach.
Primary actions should sit where the thumb naturally reaches on a phone held one-handed.
Web accessibility is organised around four principles: content must be Perceivable, Operable, Understandable, and Robust — failure on any one principle makes content inaccessible to some users.
Attribution & sources
Identified by W3C (WCAG 2.2) and platform guidelines. Catalogued from W3C — WCAG 2.2 Understanding SC 2.5.8: Target Size (Minimum).
Based on WCAG 2.2 target-size criteria and Apple's interface guidelines; the linked W3C page is the reference used here.
See Touch Target Sizing on your own site
Run a free Kweri audit — a plain-English review of your site’s speed, accessibility, SEO and design, ranked by what to fix first. No login, no jargon.
Run a free audit →