Protocol
Test the target and its neighbours, not just the icon
The finger meets the clickable area, not the design file.
When it fits
- Small controls are difficult to activate without hitting something else.
When to avoid it
- CSS pixels are not physical screen pixels. Passing the minimum criterion does not prove comfort or suitability for every user.
Why it matters
Inspect the actual pointer target and its spacing from nearby targets. WCAG 2.5.8 uses a 24 by 24 CSS pixel minimum with defined exceptions, including qualifying spacing. Apply the complete condition rather than treating one icon dimension as the whole test.
Steps
- Measure the implemented hit area, not only its visible artwork.
- Check adjacent controls, spacing and any applicable exception.
- Try the important task on the intended input device and viewport.
An example
A tiny visible icon has a larger implemented target, while two adjacent text actions overlap their effective hit areas. They need different fixes.
Check your result
Can the user reliably choose the intended action without an unintended neighbour receiving it?
Keep this limit in mind
- CSS pixels are not physical screen pixels. Passing the minimum criterion does not prove comfort or suitability for every user.
Connected ideas
Useful withComplete the journey with the keyboard alone
Evidence and sources
WCAG 2.5.8 at Level AA specifies a 24 by 24 CSS pixel minimum target or applicable exceptions, including qualifying spacing.
Do not replace the complete criterion with a claim that every target must be enlarged to the same dimensions.
Understanding Success Criterion 2.5.8: Target Size (Minimum) · Success criterion and exception explanations.