WCAG 2.2 - Success Criterion
2.5.7 Dragging Movements
Description
This criterion, new in WCAG 2.2, requires that all functionality that uses a dragging movement can also be achieved with a single pointer without dragging. Dragging requires the user to press down, maintain contact while moving the pointer, and then release - a multi-step motor action that many users with motor impairments cannot reliably perform. A simple alternative such as clicking a "Move left" button, clicking to pick up and then clicking to place, or entering coordinates achieves the same result without dragging.
How To Test
- Identify all drag interactions on the page: sortable lists, sliders, draggable cards, resizable panels, map pins, and file upload drop zones.
- For each drag interaction, look for a non-dragging alternative that accomplishes the same task using only single-pointer clicks or taps.
- Attempt to complete each drag-based task without performing any drag movement - using only clicks, taps, or keyboard input.
- Verify the non-drag alternative is accessible via keyboard as well (this also relates to 2.1.1 Keyboard).
- Test with a pointing device set to a low precision (or simulated tremor) to understand the difficulty of drag interactions for affected users.
Testing Tools
- axe DevTools — Scan for drag-required interactions and form label issues.
- NVDA — Test form announcements and error messages using keyboard-only navigation.
- Lighthouse — Accessibility audit for form input and error handling.
Demo
This todo list can only be reordered by dragging items. Users with motor impairments cannot reliably perform drag operations:
- Buy groceries
- Call dentist
- Finish report
Drag items to reorder (Note: this demo does not implement actual drag - it shows the fail interface)
Each todo item has Move Up and Move Down buttons for non-drag reordering:
-
Buy groceries
-
Call dentist
-
Finish report
Code
Why this fails
Items can only be reordered by dragging. Users with tremors, limited dexterity, or those using switch control cannot perform sustained drag operations.
Why this passes
Move Up and Move Down buttons provide a single-pointer click alternative to dragging. Users can click buttons to achieve the same result.
Code
This volume slider can only be adjusted by dragging. Keyboard arrow keys work, but dragging is the primary interaction:
The slider now has a number input field. Users can type a value or use the slider, and both stay synchronized:
Code
Why this fails
The slider only provides drag interaction. While keyboard arrow keys work, there is no alternative for users who cannot reliably perform drag operations.
Why this passes
A number input provides a non-drag alternative. Users can type a specific value directly instead of dragging, or use the slider if they prefer.
Code
Fail Explanation
A failure occurs when content is only operable through a drag interaction with no non-dragging alternative. For example, a Kanban board where cards can only be moved between columns by dragging, a slider that has no corresponding number input field, or a sortable list where items can only be reordered by drag-and-drop - all fail if no equivalent single-click or keyboard mechanism is provided. Users with Parkinson's disease, hand tremors, or those using switch access or voice control cannot reliably perform sustained drag actions.
Pass Explanation
A passing implementation provides at least one alternative to every drag interaction that requires only a single pointer action (a tap or click). For a sortable list, this could be "Move up" and "Move down" buttons on each item. For a range slider, a text input that accepts the numeric value is a valid alternative. For a map with draggable pins, a button that opens a dialog where coordinates can be typed would satisfy the requirement. The alternative does not need to provide an identical experience, only equivalent functionality.
WCAG Techniques
- Failure: F108 (dragging movements - no non-drag alternative)
- Success Techniques: G215 (providing buttons and scripts that perform the same function as the drag operation), G216 (providing single point activation for a drag operation)
Notes
This criterion applies to drag interactions that are author-implemented, not to browser or operating system drag behaviors. Scroll dragging (using a scrollbar or touch-scrolling a region) is specifically excluded from this criterion. The criterion is closely related to 2.1.1 (Keyboard) but focuses specifically on pointer-based dragging rather than all keyboard accessibility, and applies to mouse/touch interfaces that lack equivalent non-drag paths.
Techniques
WCAG techniques used in this demo: G219
Suggested Solutions & References
Curated from 6 real-world audit findings and official WCAG guidance.