Free target size checker for any web page
A page's URL in, every button and link too small to tap out, measured in a browser against the WCAG 2.2 minimum of 24 by 24 pixels.
Check a page's target sizes
Example A made-up bakery's order page. Enter yours to check it.
8 targets too small to tap
A target passes at 24 by 24 pixels, or with 24 pixels of room around it.
| Problem | Element |
|---|---|
| 2 buttons at 20 by 20 pixels 20 pixels of room around it. | <button type="button" aria-label="One fewer loaf"><button type="button" aria-label="One more loaf"> |
| 3 links at 18 by 18 pixels 16 pixels of room around it. | <a href="/breads?page=1" aria-current="page"><a href="/breads?page=2"><a href="/breads?page=3"> |
| 3 links at 16 by 16 pixels 16 pixels of room around it. | <a href="https://instagram.example/qsb" aria-label="Instagram"><a href="https://facebook.example/qsb" aria-label="Facebook"><a href="https://tiktok.example/qsb" aria-label="TikTok"> |
The fix, in CSS
Social icons in a footer are 16 pixels square and sit 4 pixels apart. People with tremors or on small screens tap the wrong one.
/* Broken: 16 by 16 targets packed together */
.social a {
width: 16px;
height: 16px;
margin: 0 2px;
}
/* Fixed: the icon stays small, the tap area is 44 by 44 */
.social a {
display: inline-grid;
place-items: center;
width: 44px;
height: 44px;
}
.social a svg {
width: 16px;
height: 16px;
}
What still needs a person
No automated tool can confirm these. AccessGuard marks related findings as Review, so nobody mistakes them for a pass.
This check maps to WCAG 2.5.8 Target Size (Minimum), level AA, and is partly automated.
- Whether another control on the page does the same thing at full size, which lets a small one pass.
- Whether a small size is essential, such as a pin on a map that has to sit at its place.
- The page at a phone width, where a layout can draw the same controls smaller.
Questions
What does WCAG 2.5.8 require?
Pointer targets must be at least 24 by 24 CSS pixels, unless there is enough space around them, they are inline in text, the browser controls their size, or the small size is essential.
Is 44 by 44 pixels required?
44 by 44 is the stricter AAA criterion (2.5.5) and a common design guideline. The AA minimum is 24 by 24.
Is target size new?
Yes. Target Size (Minimum) was added in WCAG 2.2, published in October 2023.
Related checks and guides
-
Checks
Keyboard and focus checkerFinds controls people can't reach by keyboard, controls a keyboard reaches but nobody can see, focus styles that were removed, and focused elements hidden behind sticky headers.
-
Color contrast checker
Two colors in, the ratio out, and the nearest color that passes WCAG 2.2.
-
Link text checker
Finds links with no accessible name, vague text like "click here", and links that open new windows without warning.
-
Guides
Most Common WCAG Violations (With Code Fixes for Each)The same handful of WCAG violations appear on nearly every website we scan. Here's what they are, why they matter for compliance, and exactly how to fix each one with code examples.
-
WCAG 2.2 vs 2.1: What Changed and What to Re-Test
WCAG 2.2 keeps every 2.1 criterion but one, adds six at Level AA and leaves color contrast alone, so here is exactly what to re-test.
-
WCAG 2.5.8 Target Size: The 24px Minimum and Its Exceptions
What 2.5.8 actually asks for, the spacing exception worked out in pixels, and CSS fixes that leave the design alone.
-
WCAG 2.2 Checklist: Every Level A and AA Criterion
All 55 Level A and AA success criteria in plain words, how to check each one, and which ones a scan can see and which need a person.
Every check, not only target size
The free audit runs this check and every other one. Results in about a minute.