Target size · WCAG 2.5.8
WCAG target size: the 24 by 24 pixel minimum and the spacing rule
The short answer
WCAG 2.2 success criterion 2.5.8 (Level AA) asks for pointer targets of at least 24 by 24 CSS pixels. A smaller target can still pass if a 24 pixel circle centred on it does not overlap another target or another small target's circle. Links inside sentences, unchanged browser controls and a few other cases are exceptions. Level AAA (2.5.5) asks for 44 by 44.
What WCAG 2.2 asks for
WCAG 2.2 added success criterion 2.5.8 Target Size (Minimum) at Level AA. Its rule is short: "The size of the target for pointer inputs is at least 24 by 24 CSS pixels", unless one of five exceptions applies. A pointer input is any device that points at a spot on the screen, such as a mouse, a pen or a finger on a touch screen. If WCAG levels are new to you, our article on WCAG contrast ratios explains how A, AA and AAA fit together.
A target is the "region of the display that will accept a pointer action, such as the interactive area of a user interface component". That is the area you can click or tap, not just the icon you can see. For the size test, the W3C says it must be possible to draw a solid 24 by 24 CSS pixel square, aligned with the page, completely inside the target. A round button or one with large rounded corners can therefore be smaller than its width and height suggest.
| Criterion | Level | Minimum size | Spacing exception |
|---|---|---|---|
| 2.5.8 Target Size (Minimum) | AA | 24 by 24 CSS pixels | Yes |
| 2.5.5 Target Size (Enhanced) | AAA | 44 by 44 CSS pixels | No |
The sizes are in CSS pixels, the unit you write in a stylesheet, not the physical pixels of a screen. The W3C's Understanding 2.5.8 page also says the requirement is independent of the zoom factor: when users zoom in, the CSS pixel size of an element does not change, so authors cannot meet it by saying the target gets bigger when the user zooms in. Its aim is fewer slips onto the wrong control for people with hand tremors, spasticity or other limits on fine movement, and for anyone using a touch screen.
How the 24 pixel spacing circle works
A target smaller than 24 by 24 is called undersized. It can still pass through the Spacing exception. Draw an imaginary circle 24 CSS pixels across, centred on the target's bounding box. If that circle does not overlap another target, or the circle of another undersized target, the target passes. A small icon on its own, far from anything else, passes. Two small icons side by side may not.
Worked example: two square buttons in a row
Two equal square buttons sit side by side. The distance between their centres is the button size plus the gap, and each circle has a radius of 12 pixels, so the circles do not overlap when the size plus the gap is at least 24. The gap you need is 24 minus the button size.
- 20 pixel buttons need a 4 pixel gap.
- 16 pixel buttons need an 8 pixel gap.
- 24 pixel buttons need no gap at all, because they meet the size rule.
We built each case as a test page and ran axe-core 4.14.0 in Chromium, the version Kerbwise bundles. Its results matched the arithmetic, shown in the table below.
| Button size | Gap | Result | Safe space axe reports |
|---|---|---|---|
| 24 by 24 | 0 px | Pass | 24 px of 24 (size is enough) |
| 20 by 20 | 4 px | Pass | 24 px of 24 |
| 20 by 20 | 3 px | Fail | 22 px of 24 |
| 20 by 20 | 0 px | Fail | 16 px of 24 |
| 16 by 16 | 8 px | Pass | 24 px of 24 |
| 16 by 16 | 7 px | Fail | 22 px of 24 |
The W3C page gives the same 20 by 20 example: with a 4 pixel space between them the buttons pass, and with no space they fail. The rule also works between a small target and a large one. A 16 by 16 button touching a large linked image failed in our test, and the same button 4 pixels away passed, again matching the W3C's own example. Stacked rows count too: links 18 pixels tall with a 1 pixel gap between rows failed, because each circle reaches into the row above or below.
The other four exceptions
Besides spacing, success criterion 2.5.8 lists four more exceptions.
- Equivalent: the same function is available through another control on the same page that meets the criterion.
- Inline: the target is in a sentence, or its size is constrained by the line-height of non-target text. A link in a paragraph does not need to be 24 pixels tall.
- User agent control: the browser decides the size and the author has not changed it. The W3C's examples are the days
in the calendar of an
<input type="date">and the browser's scrollbars. - Essential: a particular presentation is essential, or legally required, for the information being conveyed. Pins on a digital map are the W3C's example.
The W3C also notes that a target covered by content that appears after a user action or through a script, such as a dropdown list, a modal dialog or a cookie banner, does not have to meet the rule while it is covered. The new content on top does.
Fixing small icon buttons
Icon buttons, such as close, previous and next, quantity plus and minus, and social links, are small targets when their clickable area is no bigger than the icon. The icon can stay the same size. What has to grow is the clickable area around it, or the space between neighbours.
- Add padding to the button or link itself, not to the icon inside it. Padding on the element that gets the click makes its clickable area bigger.
- Or set a minimum size on the control, such as
min-width: 24px; min-height: 24px;, and centre the icon. - Or keep the controls small and move them apart until the gap is at least 24 minus their size.
We tested the first two on a pair of 16 pixel icon buttons that touched each other. As they were, axe reported both as
failing. With padding: 4px on each button, each one measured 24 by 24 and passed. With min-width and min-height set to 24 pixels, the result was the same. Treat 24 pixels as the
floor. The W3C's Understanding page encourages authors to meet the size requirement even when spacing would allow a
pass, and suggests aiming for the stricter 44 by 44 of success criterion 2.5.5 for important
controls.
What automated checks can and cannot decide
Size and spacing are measurable, so a checker can do much of this work. axe-core has a target-size rule for
2.5.8. In our tests it left links inside a sentence out of the check altogether, in line with the Inline exception. When
targets overlap in complicated ways, or a neighbouring element may or may not be a target, axe reports the element as needing
review rather than failing it.
Other exceptions need judgement. Whether another control on the page does the same job (Equivalent), or whether a layout is essential to the information (Essential), is something a person has to decide. A check also measures the page at one moment and one window size. A menu that only opens on click, or a layout that changes on a phone, is only measured in the state it was in during the scan. Automated checks find many issues, but not all of them, so a manual review is still needed.
Kerbwise runs axe-core's target-size rule with its other WCAG 2.2 A and AA checks on the page you have open.
For each issue found by automated checks, it explains in plain language who is affected, outlines the element on the page
and offers a "Copy prompt for your AI agent" button. It has no ready-made code fix for this rule, so the padding or spacing
change is yours to make.
Questions people ask
- What is the minimum target size in WCAG 2.2?
- 24 by 24 CSS pixels at Level AA, in success criterion 2.5.8, Target Size (Minimum). A smaller target can still pass through one of five exceptions, such as enough spacing from other targets.
- Is the WCAG target size 24 or 44 pixels?
- Both numbers exist. 24 by 24 is Level AA (2.5.8), new in WCAG 2.2. 44 by 44 is Level AAA (2.5.5, Target Size (Enhanced)), which came in with WCAG 2.1 and has no spacing exception.
- Do links in a paragraph have to be 24 pixels tall?
- No. The Inline exception covers targets in a sentence, and targets whose size is constrained by the line-height of the text around them.
- Does padding count towards the target size?
- Padding on the element that receives the click, such as the button or link itself, makes its clickable area bigger. In our test, a 16 pixel icon in a button with 4 pixels of padding measured 24 by 24 and passed.
- Can zooming in make a small target pass?
- No. The W3C says the requirement is independent of the zoom factor, because the CSS pixel size of an element does not change when users zoom.
- Can an automated check confirm that a page meets 2.5.8?
- No. It can measure the size and spacing of the targets it finds, but exceptions such as Equivalent and Essential need a person to judge, so a manual review is still needed.