Goal
Make touch targets large enough and/or spaced to reduce accidental activation.
Success Criterion · WCAG 2.5.8
Target Size (Minimum)
The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except where the target is available through an equivalent link or control on the same page that is at least 24 by 24 CSS pixels, the target is in a sentence or its size is otherwise constrained by the line-height of non-target text, a particular presentation of the target is essential or is legally required for the information being conveyed, or the size of the target is determined by the user agent and is not modified by the author.
Level AAWCAG 2.2Operable2.5 · Input Modalities
Copy button ready
What to do
Ensure minimum target size of 24×24 CSS pixels or provide sufficient spacing/offset to achieve the requirement.
Why it matters
Small targets cause errors for users with motor impairments and on touch devices.
Success criterion
What WCAG 2.5.8 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except where: (a) Spacing: The target is at least 24 by 24 CSS pixels or there is a spacing of at least 24 CSS pixels to the nearest target; (b) Equivalent: The function can be achieved through an equivalent control on the same page that meets this criterion; (c) Inline: The target is in a sentence or block of text; (d) User agent control: The size of the target is determined by the user agent and is not modified by the author; (e) Essential: A particular presentation of the target is essential to the information being conveyed.
Intent
Why WCAG created this requirement
- Reduce accidental activation and improve pointer usability.
- Allow either a minimum size or adequate spacing.
- This is a WCAG 2.2 addition (Level AA).
Benefits
Who gains when you pass
- Users with limited dexterity can tap targets more reliably.
- Mobile users make fewer mistakes.
- Users with tremors benefit from additional spacing and larger targets.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Small, crowded icons lead to frequent mis-taps.
Users may be unable to operate dense toolbars or controls.
Exception guidelines
Use the WCAG 2.5.8 exceptions correctly
Document the rationale for each exception and note which alternative support you provide.
Spacing
Adequate spacing exists between targets.
Requirement
Ensure minimum spacing to nearest target to reduce mis-taps.
Equivalent
An equivalent control meets the requirement.
Requirement
Provide an equivalent target meeting this criterion.
Inline
Target is inline within text.
Requirement
Inline targets are exempt.
User agent control
Size determined by user agent and not modified by author.
Requirement
UA-controlled targets may be exempt.
Essential
Presentation is essential to information.
Requirement
Only when truly essential.
Overview
This WCAG 2.2 Level AA criterion sets a baseline target size: most pointer targets should be at least 24×24 CSS pixels, or have sufficient spacing to prevent mis-taps. It includes exceptions similar to 2.5.5.
- Measure in CSS pixels and consider effective hit area, not just visible icon size.
- Spacing between targets can satisfy the criterion even if targets are small.
- Inline links are exempt; avoid making inline links too cramped.
Reference: All summaries and highlights originate from Understanding WCAG 2.5.8 and the W3C quick reference.
Fast facts
- Conformance level
- Level AA
- WCAG version introduced
- WCAG 2.2
- Principle
- Operable
- Guideline
- 2.5 · Input Modalities
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Toolbar icons
Pass
Icons are 16px but wrapped in 24×24+ hit areas with spacing.
Fail
Icons are 16px with no padding and tightly packed.
Close button
Pass
Close target is at least 24×24 with sufficient spacing from other controls.
Fail
Close target is tiny and adjacent to other icons, causing mis-taps.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document target size/spacings used in component library.
- Maintain exception list and rationale for dense interfaces.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Capture progress and blockers
- Audit target sizes and spacing for common UI controls and icon buttons.
- Ensure targets are ≥ 24×24 CSS px or adjust spacing to meet the rule.
- Increase hit area via padding without changing layout excessively.
- Ensure small targets have sufficient separation from adjacent targets.
- Document any exceptions (inline, essential) and ensure they are valid.
Testing ideas
Prove conformance with evidence
- Measure target hit areas and/or spacing in CSS pixels.
- Test on touch devices to verify ease of activation.
- Verify equivalent controls exist where needed.
- Check dense UI regions (toolbars) for accidental activation issues.
Related success criteria