Accessibility Wiki

Pointer targets must be large enough

Rule target-size · Deeper checks · impact serious · Live only (static → incomplete)

↩ Back to the rules index · WCAG cross-reference

Why it matters

Small tap targets are hard to hit for people with motor impairments or on touch screens. WCAG 2.2 requires interactive targets to be at least 24×24 CSS px, exempting inline targets in sentences (size constrained by the line-height of surrounding text) and undersized targets with adequate spacing (the 24px-circle test). This needs real geometry, so it runs on a live page.

How to fix

Make the clickable box at least 24×24 CSS px: add padding, set min-width and min-height, or enlarge the link or button itself rather than only the icon inside it — the measured size is the element’s box, so padding on a transparent button counts. WCAG also accepts an undersized target when there is enough space around it (a 24px circle centred on it touches no other target), when it sits inline in a sentence, or when a larger control on the same page does the same thing. Native buttons and inputs, and lone inline links outside running text, are reported as a warning to review rather than a failure.

Example

✕ Fails
<button style="width:16px;height:16px">x</button>
✓ Passes
<button style="width:24px;height:24px">x</button>

WCAG success criteria

2.5.8 Target Size (Minimum) — Level AA

Pointer targets should be at least 24×24 CSS px, or have sufficient spacing.

Understanding 2.5.8

Standards

This rule contributes to the following standards:

WCAG AA EN 301 549

Standard Criteria
EN 301 549 9.2.5.8

References

Generated from the EqualWeb accessibility engine’s rule metadata. Back to top ↑