W3C WCAG 2.5.7 Dragging Movements (Level AA) - New in WCAG 2.2
Provide single-pointer alternatives for all drag-and-drop functionality, unless dragging is essential to the underlying activity
Where this comes from
Provision: 2.5.7 Dragging Movements (Level AA) - New in WCAG 2.2
Instrument: W3C Web Content Accessibility Guidelines (WCAG) 2.2
Citation: W3C, Web Content Accessibility Guidelines (WCAG) 2.2, Success Criterion 2.5.7 Dragging Movements, Level AA, W3C Recommendation 05 October 2023
Text version: WCAG 2.2
Who it applies to
It applies when all of these are true:
- Service type — any answer
- Service uses content personalization
What engineering work it implies
Sample acceptance criteria Landfall generates for this obligation:
- Every drag-and-drop action has a single-pointer (click/tap) alternative
- Sortable lists offer move/reorder buttons; sliders accept direct value entry
- File drop zones always include a browse/upload button
- Alternatives are announced to assistive tech (ARIA live where state changes), unless dragging is essential
- Unit tests cover the core logic (aim for >80% coverage on new code)
Questions people ask
- Does W3C WCAG 2.5.7 Dragging Movements (Level AA) - New in WCAG 2.2 apply to my service?
- It applies when Service type — any answer; Service uses content personalization.
- From when does this apply?
- W3C WCAG 2.5.7 Dragging Movements (Level AA) - New in WCAG 2.2 applies from 5 October 2023. Its current status is: in force.
Find out whether this one lands on you
Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.
Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.