diagnostic · one of 45 free, no counter
Tap targets
Which buttons on this page are too small to tap?
WCAG 2.5.8 sets a floor of 24 by 24 CSS pixels for anything you can press, unless the target has enough clear space around it - and a lighthouse score does not tell you which controls fall under it. This measures every button, link, field and control on the page, applies the spacing exception, and lists the undersized ones smallest and most crowded first, with the 44px size platform guidance asks for listed beside it.
Reach it Press ⌘ + K on any tab and type tap targets. Ctrl + K on Windows and Linux
in the panel · free, no counter
What this actually is
every control under 24px or 44px, with the wcag spacing exception appliedBefore a mobile release, after an icon-button redesign, and whenever a support ticket says "I keep hitting the wrong thing". It is the check that finds the close button on a modal that is 16 pixels square.
Asked about this diagnostic
3 of themWhat is the spacing exception?
A target under 24px still passes if a 24px circle centred on it does not touch another target. The tool uses a square rather than a circle, so it reports slightly more than a strict reading would - on the safe side.
Why are links in text not measured?
WCAG exempts them: a link inside a sentence is as tall as the line it sits in, and making it bigger would mean changing the text. They are counted so you know how many there are.
Is 44px a requirement?
Not in WCAG 2.2 AA. It is the size platform guidance recommends and what the AAA level asks for, so it is listed as guidance and never counted as a failure.
how to use tap targets
- Open Tap targets on the page, ideally at a phone width.
- Read the totals: under 24 and crowded, under 24 but spaced, under 44.
- Go down the list, smallest and most crowded first, with each size printed.
- Fix the failures first - under 44 is guidance, under 24 and crowded fails.
96 of these · no host permissions · three free audits