- Level
- AA
- Since
- WCAG 2.2
- Entries
- 88 / 193
2.5.8 Target Size (Minimum)
Anything a person taps or clicks has to measure at least 24 by 24 CSS pixels or have enough empty space around it, so that people do not hit the neighbouring control by mistake.
/ What it requires
A target is the area that reacts to a click or a tap. This criterion sets a floor for it: 24 by 24 CSS pixels, measured on the area that responds and not on the icon drawn inside. It protects people who cannot point precisely: those with a tremor or limited movement in the hand, people who use a head pointer, and anyone on a small touch screen. When targets are tiny and packed together, these users open the wrong link or delete the wrong row.
A smaller target still passes in five cases the criterion names. Spacing: a circle 24 CSS pixels across, centred on the target, touches no other target and no such circle around another undersized target. Equivalent: another control on the same page does the same job and meets the size. Inline: the target sits in a sentence, or the line height of the surrounding text limits it. The browser draws the control and the author has not changed it. A particular presentation is essential or legally required.
This criterion is new in WCAG 2.2, so an audit against WCAG 2.1 does not include it.
/ How pages fail it
- A toolbar of icon buttons 16 pixels wide sits edge to edge with no gap between the buttons.
- Pagination numbers are narrow links placed a few pixels apart.
- The close button of a dialog is a small cross pressed against another control in the corner.
- A row of social media icons in the footer is 20 pixels high with gaps of 4 pixels.
- The remove cross inside a filter chip is a few pixels wide and sits right next to the link of the chip itself.
/ How to check it yourself
- Set the browser zoom to 100 percent and look for the small things first: icon buttons, pagination, close crosses, footer icons and custom checkboxes.
- Inspect each one in the developer tools. The size shown for the element, padding included, is the target, and both width and height have to reach 24 CSS pixels.
- For anything smaller, measure the distance to its neighbours. A circle 24 pixels across centred on the target must not reach another target, nor the same circle around another small target.
- Check whether a remaining small target falls under one of the named exceptions, for example a link in running text or a native checkbox nobody has restyled.
- Open the page on a phone and note where a thumb lands on the wrong control.
/ How to fix it
- Set min-width: 24px and min-height: 24px on the button or the a element itself, not only on the svg inside it.
- Enlarge the clickable area with padding and keep the icon at the size it is drawn.
- Where the design cannot grow, separate the targets with margin, or with gap in a flex or grid container, until the 24 pixel circles no longer meet.
- Give a link that holds only an icon display: inline-flex, so that width, height and padding apply to it.
- Replace a tiny custom checkbox or radio button with the native input element, or size the custom one to 24 by 24 CSS pixels.
/ What our scanner checks
The target-too-small check measures the rendered size of links, buttons, inputs, selects and elements with the role button, link, checkbox or switch. It skips inline links in a paragraph, list item or table cell, and reports a target under 24 by 24 pixels only when the 24 pixel circle around it reaches another target. It sees one desktop layout and cannot judge the equivalent or essential exceptions.
/ Who fails it, in our own measurements
One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.
/ Questions about this criterion
What is the minimum target size in WCAG 2.2?
Success criterion 2.5.8 sets it at 24 by 24 CSS pixels at level AA. A target may be smaller when it has enough space around it, when it is a link inside a sentence, when another control on the page does the same job, when the browser draws it unchanged, or when its presentation is essential or legally required.
What is the difference between 2.5.8 and 2.5.5 target size?
They are two criteria at two levels. 2.5.8 Target Size (Minimum) is level AA and asks for 24 by 24 CSS pixels, with a spacing exception. 2.5.5 Target Size (Enhanced) is level AAA and asks for 44 by 44 CSS pixels. Conformance at level AA requires only the first of them.
Do links inside a paragraph have to be 24 pixels high?
No. The criterion exempts a target that sits in a sentence, or whose size is limited by the line height of the surrounding text. A link in the middle of a paragraph can keep the height of its line. The exemption does not reach a row of buttons or a menu, where every item is a separate target that stands alone.
