WCAG 2.2 · Level AA · Operable
2.5.7 Dragging Movements
Manual verification
How to validate 2.5.7 by hand
Check every function that requires dragging and provide a single-pointer alternative that does not require a dragging movement.
Start with the extension result
Reopen the reported URL and reproduce the same state (for example, after expanding a menu or submitting a form). Use the result’s Highlight action when available, or its affected-element details and CSS selector, to find the reported content. Apply the checks below to that content and its context. If the element or state has changed, rescan and record that difference before deciding whether the finding still applies.
- Find sliders, sortable lists, draggable cards, maps, and other controls that require press-move-release.
- Try to achieve the same result using clicks or taps at the start and end points, or another single-pointer control.
- Check whether the drag is essential to the function or is determined by the user agent rather than page content.
Evidence to record
Record the drag task, alternative pointer operation, and outcome, or explain the precise exception.
Scope and exceptions
A keyboard alternative does not satisfy this pointer-specific requirement by itself. The alternative must avoid dragging and use a single pointer.
Record the review outcome
- Confirmed: the recorded evidence shows the requirement is not met in the tested page state, and no applicable exception explains it.
- Not reproduced: the reported issue is absent in the current state. Record the URL, state, and affected element you checked; this does not prove other pages or states conform.
- Needs more review: evidence is incomplete, the content requires human judgment, or an exception is uncertain. Record what remains to be checked instead of treating it as a pass.