Small interactive targets are difficult to activate accurately, especially on touch screens. Users may miss the intended control, activate the wrong one, or be unable to interact at all. These problems are amplified for users with limited dexterity, tremors, or reduced motor control.
WCAG 2.5.5 addresses this by requiring larger, more forgiving targets for pointer input.
What Is a Target
A target is the interactive area that responds to pointer input, such as a button, link, icon, or any clickable or tappable region.
The target is not just the visible graphic or text. It is the full hit area that responds to interaction. Padding can increase the target size even if the visible element appears small.
WCAG Success Criterion
2.5.5 Target Size (Enhanced) (Level AAA)
The size of the target for pointer inputs is at least 44 by 44 CSS pixels, except when one of the following conditions applies:
Equivalent
The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels.
Inline
The target is contained within a sentence or block of text.
User Agent Control
The size of the target is determined by the user agent and is not modified by the author.
Essential
A particular presentation of the target is essential to the information being conveyed.
Intent of the Success Criterion
This criterion intends to help users who have difficulty activating small targets due to:
- Hand tremors
- Limited dexterity
- Reduced fine motor control
- One-handed use
- Coarse input methods such as touch
Touch input is particularly challenging because a finger is larger than a mouse pointer and often obscures the precise activation point.
Larger targets reduce missed taps and incorrect activation, which is the failure condition this criterion is designed to prevent.
Understanding the 44 × 44 CSS Pixel Requirement
- The requirement is based on CSS pixels, not physical device pixels.
- Padding around an element counts toward the target size.
- The visible control does not need to appear large if the interactive area meets the requirement.
This criterion defines a minimum, not an ideal size. Larger targets are recommended when:
- The control is used frequently
- The result of the action cannot be easily undone
- The control is near the edge of the screen
- The control is part of a sequential task
Note on WCAG 2.5.8
WCAG 2.5.5 is the stricter Level AAA version of target size. WCAG 2.5.8 (Level AA) allows smaller targets if sufficient spacing is provided around them.
This criterion removes that flexibility. Under 2.5.5, targets must meet the full 44 × 44 CSS pixel size unless an explicit exception applies.
Exceptions Explained
Equivalent Targets
If multiple targets perform the same action, only one needs to meet the 44 × 44 requirement.
Example:
- A large “Next” button and a smaller icon both navigate forward
- The large button satisfies the requirement
Inline Targets
Targets that are part of the text flow within a sentence or paragraph are excluded.
This includes:
- Text links within paragraphs
- Footnote markers at the end of sentences
- Icons that function as inline links within text
This exception exists because inline content must reflow and cannot reliably support large hit areas without overlap.
Important clarification:
If the entire sentence itself is the target and is not part of a larger text block, it must meet the 44 × 44 requirement.
User Agent Control
If the target size is controlled entirely by the user agent and not modified by the author, the requirement does not apply.
This exception applies only when authors do not override size through CSS or other styling.
Essential
If a target must be a specific size to convey information or functionality, and increasing its size would fundamentally alter the experience, the exception applies.
This is a narrow exception and should not be used for convenience or visual preference.
Common Failures of SC 2.5.5
Icon-only buttons smaller than 44 × 44 with no equivalent control
Fails because the target is too small and no exception applies.
Closely packed controls with reduced padding
Fails because the effective hit area is below the minimum size.
Increasing visual size without increasing the hit area
Fails because only the clickable region matters.
Overlapping hit areas
Fails because users may activate the wrong control even if each appears visually large.
Common Misinterpretations
- Increasing visual size without increasing the interactive area
- Assuming margin between elements counts toward target size (it does not)
- Treating standalone icon buttons as inline text
- Relying on spacing alone instead of target size under 2.5.5
How to Test Target Size
- Inspect the element in the browser developer tools
- Check the clickable or tappable bounding box
- Confirm it is at least 44 × 44 CSS pixels
- Verify padding contributes to the hit area
- Test using touch simulation or coarse pointer emulation
If the interactive area is smaller, the criterion is not met unless an exception applies.
Examples That Pass
- Buttons with a clickable area of at least 44 × 44 CSS pixels
- Equivalent targets where one meets the size requirement
- Inline text links within paragraphs
- Footnote markers within sentences
- Native browser controls whose size is not overridden
Benefits
This success criterion benefits:
- Touchscreen users
- Users with motor impairments or tremors
- Users operating devices in unstable environments
- Users who find precise movements difficult
- Users with low vision who benefit from larger interactive areas
Wrapping Up
WCAG 2.5.5 raises the bar for pointer accessibility by requiring larger, more forgiving targets. Although it is a Level AAA criterion, it addresses common and well-documented usability failures on touch devices.
Where it applies, targets must be at least 44 × 44 CSS pixels unless a clearly defined exception is met. Designing with an adequate target size reduces incorrect activation and improves reliability for all users.
