- Success Criterion 2.5.8
- Conformance level AA
Tap Target Smaller Than the Required 24×24 Pixel Minimum
2.5.8 — Target Size (Minimum)
Scenario
Setting
A subscription box service's account settings
What’s wrong
No numbered W3C failure technique exists for this rule — it fails simply when the required feature/behavior is missing or inadequate (see the scenarios below).
Example
This shows up on a subscription box service's account settings: no numbered W3C failure technique exists for this rule — it fails simply when the required feature/behavior is missing or inadequate (see the scenarios below).
Why it matters
People with tremor or larger touch contact areas, and anyone tapping on a moving vehicle. In this case (a subscription box service's account settings), they can't operate the feature without a mouse.
How to test
Measure the target's clickable area in DevTools: it must be at least 24x24 CSS px, or have enough spacing that a 24px circle centered on it doesn't touch another target, or have an equally-sized equivalent elsewhere.
How to fix
The target must be at least 24x24 CSS px, or have enough spacing that a 24px circle around its center overlaps no other target, or a compliant equivalent control must exist.
Outcome
Once corrected, a subscription box service's account settings lets them complete the task using only the keyboard.
Who is affected
People with tremor or larger touch contact areas, and anyone tapping on a moving vehicle.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Small Icon Buttons Packed Too Close Together to Tap
- Pagination Numbers Packed Too Tightly Below 24 Pixels
- Tiny Carousel Dots Clustered With No Spacing Between Them
- Calendar Day Cells Too Small to Tap in Compact View
- Toolbar Icons Packed Edge to Edge With No Gap
- Checkbox Hit Area Limited to Its Tiny Visible Glyph