Micro Tools
Advertisement

Touch target checker

Check whether a tap target meets WCAG, Apple, and Material size guidelines, with a true-scale visual preview.

Target size

Shown at true CSS-pixel scale (capped for display).

Preview and verdict

Verdict appears here.

Advertisement

Three guidelines, one verdict

WCAG 2.2 AA requires at least 24x24 CSS pixels, Apple recommends 44x44 points, and Material Design recommends 48x48 dp. The checker tests your size against all three and shows a true-scale preview so you can feel the target with your own eyes.

Spacing counts too: the gap input shows how nearby targets affect the effective tappable envelope.

Why it matters

Small tap targets are the top mobile usability complaint: users mis-tap, get frustrated, and blame the app. Hitting 44px or more is the simplest accessibility win in interface design.

The preview caps oversized targets for display but always labels the true pixel size.

Related tools

JSON formatterFormat and validate JSON, privately. Regex testerTest regex live with highlighting. Base64 encoderBase64 encode and decode, plus URL encoder and JWT decoder.

Touch Target Checker FAQs

What is the minimum tap target size?
WCAG 2.2 AA sets 24x24 CSS px as the minimum. Apple and Google recommend larger: 44pt and 48dp respectively.
Are px, pt, and dp the same?
On standard displays they map 1:1 to CSS px. On high-DPI screens the OS scales them, but the CSS px value is what you design with.
Does spacing between targets help?
Yes. WCAG's target-size rule has a spacing exception: small targets pass if their 24px spacing envelopes do not overlap.
Why is the preview capped at 220px?
So huge test values do not break the layout. The label always shows the true size you entered.
Is this a substitute for device testing?
No. It validates sizes against guidelines, but real thumbs on real phones remain the final test.
Advertisement