Goal
Make touch targets large enough for reliable activation.
Success Criterion · WCAG 2.5.5
Target Size (Enhanced)
The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when the target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels, the target is in a sentence or block of text, the size of the target is determined by the user agent and is not modified by the author, or a particular presentation of the target is essential to the information being conveyed.
Level AAAWCAG 2.1Operable2.5 · Input Modalities
Copy button ready
What to do
Ensure interactive targets are at least 44 by 44 CSS pixels, with defined exceptions.
Why it matters
Small targets are difficult for users with motor impairments and for touch users in general.
Success criterion
What WCAG 2.5.5 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 44 by 44 CSS pixels except when: (a) Equivalent: The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels; (b) Inline: The target is in a sentence or block of text; (c) User agent control: The size of the target is determined by the user agent and is not modified by the author; (d) Essential: A particular presentation of the target is essential to the information being conveyed.
Intent
Why WCAG created this requirement
- Small touch targets increase errors and frustration.
- Minimum size improves usability for many disabilities and mobile contexts.
- Inline links are treated differently since increasing size may disrupt text flow.
Benefits
Who gains when you pass
- Users with motor impairments can activate controls more reliably.
- Users on mobile devices make fewer accidental taps.
- Older users and users with tremors benefit from 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.
Users may tap the wrong control when targets are small and close together.
Small targets can make interfaces unusable for some motor impairments.
Exception guidelines
Use the WCAG 2.5.5 exceptions correctly
Document the rationale for each exception and note which alternative support you provide.
Equivalent
An equivalent target exists that meets size requirements.
Requirement
Provide a larger equivalent control on the same page.
Inline
Target is within a sentence or block of text.
Requirement
Inline targets are exempt.
User agent control
Size is determined by the user agent and not modified by the author.
Requirement
If UA-controlled, exception applies.
Essential
Presentation is essential to information.
Requirement
Only when truly essential.
Overview
This AAA criterion requires most pointer targets (buttons, links, icons) to be at least 44×44 CSS pixels. Some exceptions apply, such as inline links within text, or when an equivalent larger control exists.
- Use padding to increase hit area without changing visual design drastically.
- Ensure spacing between adjacent targets to reduce accidental activation.
- Inline links are exempt, but consider line-height and spacing for readability.
Reference: All summaries and highlights originate from Understanding WCAG 2.5.5 and the W3C quick reference.
Fast facts
- Conformance level
- Level AAA
- WCAG version introduced
- WCAG 2.1
- 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.
Icon button
Pass
Icon is small visually but has padding creating a 44×44 hit area.
Fail
Icon button is 24×24 with no padding and is hard to tap.
Inline link
Pass
Inline “privacy policy” link inside a paragraph (exempt).
Fail
Tiny close icon in header with no larger equivalent control.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document a target-size standard for the component library.
- Maintain a list of exceptions with rationale.
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 interactive targets (buttons, icon buttons, links, toggles) on touch and pointer interfaces.
- Ensure target hit areas are ≥ 44×44 CSS px (padding allowed).
- Increase spacing between adjacent targets to avoid mis-taps.
- Document any exceptions (inline, essential) and ensure they are valid.
- Test at common mobile breakpoints.
Testing ideas
Prove conformance with evidence
- Measure target hit areas in CSS pixels (not device pixels).
- Test on touch devices for accuracy and ease of activation.
- Verify equivalent controls exist where smaller targets are used.
- Confirm inline links are appropriately exempt and still usable.
Related success criteria