Menu

Tap Targets Are Geometry, Not Taste: What WCAG 2.2's 24 Pixels Actually Measures
πŸ“°

Tap Targets Are Geometry, Not Taste: What WCAG 2.2's 24 Pixels Actually Measures

DEV Community: cssΒ·Design Den SolutionsΒ·about 10 hours ago
#wyTSOgGY
#devtocss#devto#dev#line#height
Reading 0:00
15s threshold

Conceptual AI illustration of touch-target size and spacing on a mobile screen. Generated with AI assistance and reviewed for accuracy by Design Den Solutions.

Every conversation about touch targets collapses into one of two camps. One side says "44px or you're failing". The other says "WCAG only requires 24, so we're fine". Both are reasoning about the wrong quantity. SC 2.5.8 is not a size rule. It is a spacing rule with a size floor , and the spacing half is a Euclidean distance test that most audits do not actually compute.

I measured it. Everything below is from a single machine, in a single Chrome build, and the limitations are at the end.

What the criterion actually says

WCAG 2.2, SC 2.5.8 Target Size (Minimum) , Level AA:

The target's bounding box is at least 24 by 24 CSS pixels , or

the Spacing exception applies: an imaginary 24 CSS pixel diameter circle centred on the target's bounding box must not intersect another such circle.

Two circles of diameter 24 do not intersect when and only when…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.