accessibility
Target size
What is target size in accessibility?
Target size is the size of a tappable or clickable element. If it’s too small or too crowded, people may miss it - due to larger fingers, limited dexterity, tremor, motion, or a small screen - and a control they can’t reliably hit is effectively broken. Space around a target reduces accidental activation, but that space isn’t part of the target unless it’s clickable too.
Also known as: touch target size, tap target
Prefer to watch?
Watch the recap 0:39
The demo
Tap the highlighted button each round. Try it with tiny, crowded targets, then with properly sized ones - and feel how much the margin for error matters.
Tap the highlighted button:
Hits: 0 · Misses: 0
Tap the highlighted target - mind your aim in tiny mode.
What this demo shows (text version)
A row of five adjacent buttons with one highlighted as the target to tap; the target moves each round. In "tiny" mode the buttons are small and packed tightly together, so it is easy to miss and hit a neighbour. In "adequate" mode they are around 44 pixels with comfortable spacing, and hitting the right one is effortless.
A tally counts hits and misses. The control and the task are identical; only the size and spacing change. The lesson is that target size and spacing decide how much margin for error people have - critical for touch, small screens, and anyone with reduced motor control. WCAG 2.2 sets a 24-pixel minimum, with 44-48 pixels recommended.
A control that’s too small or too crowded gets mis-tapped - by larger fingers, limited dexterity, tremor, motion or a small screen - and for those people it may as well be broken. WCAG 2.2 sets a minimum of 24 by 24 CSS pixels at AA (subject to exceptions) and 44 by 44 at AAA. Give tappable elements a generous size and a little breathing room - spacing cuts accidental taps even though it isn’t part of the target itself.
With the tiny targets you fumbled and hit the wrong one; size them up and the same task became effortless. Nothing changed but the box you had to land on. That margin for error - or the lack of it - is what target size buys, and it's invisible until it fails someone.
The numbers worth knowing: WCAG 2.2 sets a minimum of 24 by 24 CSS pixels at level AA (subject to exceptions - for example inline links in text, or controls sized by the browser), and 44 by 44 at level AAA, which most mobile platforms echo. Spacing counts as much as size - small controls packed tight are worse than small controls with breathing room, because the danger is hitting the neighbour.
It isn't only for touch. Anyone with reduced motor control, a tremor, or a trackpad on a train benefits from a bigger target - this is [Fitts's law](/entries/fittss-law/) as an accessibility floor, not a nicety. Put generous size and spacing on anything people tap often, and never shrink a destructive action into a trap beside a safe one.
Target size matters because small controls can’t be reliably tapped by users with larger fingers, tremor, or on small screens - and our interactive demo lets you test this in real time. Spacing around a target reduces accidental taps, but only the clickable area counts as target size
try adjusting our demo to see the difference.
Target size matters because small or crowded controls can’t be reliably tapped - especially for users with tremor, limited dexterity, or on small screens. Try our interactive demo to see how size and spacing affect real interaction. WCAG 2.2 recommends 24x24px at AA and 44x44px at AAA - but real-world testing with our demo shows how context and spacing matter more than pixels alone.
Target size ux isn’t just about pixels - it’s about how reliably users can tap without error, especially on small screens or with limited dexterity. Try the interactive demo on this page to see how target size ux affects real interaction. The key to good target size ux is giving users enough space to tap without accidentally triggering nearby controls - even if that space isn’t clickable.
Target size ux is about making tappable elements large enough to hit reliably - especially for users with tremor, limited dexterity or small screens. You can test this concept yourself in the interactive demo on this page - no screenshots or external tools needed.
Target size ux isn't just about pixels - it's about how reliably users can tap without error, especially on small screens or with tremor. You can test target size ux yourself in the interactive demo on this page, adjusting size and spacing to see how it affects interaction.