WCAG 2.2 Dragging Movements: Accessible Options
When a drag-and-drop workflow stops a task
A service team organizes incoming requests on a board. Moving a request into Approved takes a drag across the screen. For one staff member, the gesture is quick. For another, holding the pointer down while moving precisely is unreliable or impossible. The task itself is straightforward; the chosen interaction has made it inaccessible.
WCAG 2.2 offers a direct test for this situation: can the same result be reached with a single pointer without dragging?
Start with the result, not the gesture
The business outcome may be to change a request’s status, reorder a list, reveal the next slide, or set a value. Dragging is only one way to get there. A select-then-move action, a menu of destinations, or visible move buttons can support the same outcome through discrete clicks or taps.
Get IAAP Audit’s stories in your inbox
Join Medium for free to get updates from this writer.
The [W3C Dragging Movements guidance] gives examples across maps, carousels, sliders, and task boards. It also makes clear that a keyboard route alone does not necessarily meet the single-pointer requirement.
Keep the exception narrow
Success Criterion 2.5.7 is Level AA. It allows exceptions when dragging is essential to the underlying function, or when an unmodified browser or other user agent determines the action. Those conditions should be explained in the context of the product.
Moving a card between columns is a destination choice and can usually have another route. Native page scrolling is normally a browser operation. A custom drag-only scroller written by the site deserves a separate assessment.
Make the audit finding useful to delivery teams
Ask the auditor to show the task, the state before the action, the available pointer controls, and the state afterward. If the non-dragging route is absent, the report should explain what the user cannot complete and where the change belongs. A shared board component may affect many teams and pages.
Test the new control after release. Clicking a button that appears to move an item is not enough if the item does not actually reach the selected column. The same is true for a slider whose numerical field updates a label but not the underlying value.
Design for more than one route
A drag gesture can stay available for those who prefer it. The service becomes stronger when people can also choose an explicit item and destination. That design tends to make state and intent easier to explain, test, and support.
Read the original guide on IAAP Audit: https://iaapaudit.com/blog/wcag-2-2-dragging-movements-alternatives
