Target-spacing check - #255
Merged
Merged
Conversation
Small adjacent tap targets closer than 24px between centers get flagged — the fat-finger failure the 24px size check alone misses.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WCAG 2.5.8, the complement to the tap-target size check: two small targets can each be under 24px AND sit right next to each other, so fingers hit the wrong one. The audit measures center-to-center distance between small adjacent targets and flags clearances under 24px. Live fixture: two abutting 16px links flag. Local check green; merge gated on PR CI.