2.5.8 Target Size (Minimum)

Level AA · added in WCAG 2.2

Targets you click or tap must be at least 24 by 24 CSS pixels. Smaller targets pass only if they have enough space around them or fall under one of the listed exceptions.

Who it helps

People with tremors, limited dexterity or large fingers often hit the wrong control when targets are tiny and packed together. Mobile users and people using a head pointer or mouth stick also benefit.

How to meet it

Make buttons, icon links and form controls at least 24 by 24 CSS pixels, using padding or min-width and min-height.
Spacing exception: a smaller target passes if a 24 pixel circle centered on it does not overlap another target or another small target's circle.
Inline exception: links inside a sentence or paragraph do not need to meet the size.
Equivalent exception: a small target passes if another control on the same page does the same thing and meets the size.
User agent and essential exceptions: unstyled browser controls and targets whose size is essential or legally required, such as map pins, are exempt.

Examples

Fails:16 pixel icon buttons placed right next to each other

.toolbar button {
  width: 16px;
  height: 16px;
  padding: 0;
  margin: 0;
}

Passes:The same icons with a 24 pixel minimum hit area

.toolbar button {
  min-width: 24px;
  min-height: 24px;
  padding: 4px;
  margin: 0;
}

Passes:Small 16 pixel targets that pass through spacing

.pagination a {
  display: inline-block;
  width: 16px;
  height: 16px;
  /* 10px gap: centers 26px apart, so 24px circles never overlap */
  margin-right: 10px;
}

Can a scanner detect this?

Partly

axe-core's target-size rule measures target sizes and the spacing between them, so it catches many failures. It cannot judge the equivalent or essential exceptions, and overlapping or hidden targets may need a manual check.

axe-core rules that test it

target-size

Common mistakes

Sizing the icon at 24 pixels but making the clickable element smaller than the icon's box.
Packing small social media icons or close buttons together with no gap.
Assuming the inline exception covers stand-alone links in a navigation list or footer.
Treating 24 pixels as the goal on touch screens, where 44 pixels is far easier to use.

Official W3C explanation of 2.5.8

Check your own page

See which automated WCAG checks your page fails, with the failing elements and how to fix them.

Reviewed November 2, 2026