add(a11y): Dragging movements (WCAG 2.2 SC 2.5.7)#91
Draft
jdevalk wants to merge 1 commit into
Draft
Conversation
Every dragging interaction must also be operable by a single pointer that never drags. Documents the three exceptions (essential, user-agent determined, path-based gestures under SC 2.5.1) and contrasts against the common belief that the criterion bans drag and drop. Status: recommended — Level AA, and the platform contract does not break without it, so per CLAUDE.md's default-to-recommended rule it does not clear the required bar. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
f7da161
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://0f7430c5.specification-website.pages.dev |
| Branch Preview URL: | https://standards-scan-dragging-move.specification-website.pages.dev |
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.
What changed
New spec page:
accessibility/dragging-movements— WCAG 2.2 Success Criterion 2.5.7 Dragging Movements.dragging-movementsintorelatedSlugsontouch-target-size,keyboard-navigation, andnative-interactive-elements.added), linking the page inline.npm run sign:skill→ SKILL.md now claims 161 pages;index.jsondigest recomputed.Why now
Surfaced by the daily standards scan. The site covers four other WCAG 2.2 success criteria (2.5.8 target size, 3.3.7 redundant entry, 3.3.8 accessible authentication, and 2.4.11 inside
focus-indicators) but had no page on 2.5.7, and no page anywhere on providing a non-dragging route to a dragging interaction.Primary sources
Status:
recommendedLevel AA. A dragging-only control genuinely locks out switch, head-pointer, and tremor users, which is an argument for
required— andtouch-target-size(also AA, also motor impairment) isrequiredtoday. I choserecommendedbecause the web platform contract does not break without it, and CLAUDE.md says to default torecommendedwhen in doubt.This is the one judgement call in the PR — happy to promote it to
requiredto matchtouch-target-sizeif you prefer.Auditable-outcome check
Passes. Externally checkable per interaction: complete the task with single clicks only, never moving while held. "Why it matters" is phrased for visitors (dexterity, switch access, head-pointers), not developers.
Notes
consistent-help(SC 3.2.6). Each independently bumps the SKILL.md page count to 161 — whichever merges second needsnpm run sign:skillrerun to land on 162.npm run buildpasses (161 pages indexed).🤖 Generated with Claude Code