WCAG 2.2 checklist →
Where target size fits in the standard.
Free tool
Tap Target Size Checker
Enter a button or link’s width and height to check it against the WCAG 2.2 minimum target size (24×24px). Small, cramped controls are a common — and newly testable — failure.
24 × 24
px target
2.5.8 · AA (24px)—
2.5.5 · AAA (44px)—
How target size works
- WCAG 2.5.8 (AA, new in 2.2): targets should be at least 24×24 CSS pixels, unless there’s enough spacing around them, they’re inline in text, or an equivalent control exists elsewhere.
- WCAG 2.5.5 (AAA): the stricter goal is 44×44px — a good default for primary mobile actions.
- The spacing exception: a smaller target can still pass 2.5.8 if a 24px-diameter circle centered on it doesn’t overlap a neighbor’s circle. This tool flags that case so you can verify it.
See where this sits in the full standard in the WCAG 2.2 checklist.
Frequently asked questions
- What is the minimum tap target size for WCAG?
- WCAG 2.5.8 (Level AA, added in WCAG 2.2) sets a minimum of 24×24 CSS pixels, with exceptions for adequately spaced, inline, or duplicated controls. WCAG 2.5.5 (AAA) recommends 44×44 pixels.
- My buttons are smaller than 24px — do they automatically fail?
- Not necessarily. The spacing exception means an undersized target can still pass if there’s enough room around it (no overlap of 24px-diameter circles centered on adjacent targets). Enter the spacing in this tool to check that case.