Published October 24, 2026

WCAG 2.5.7 Dragging Movements, Level AA

Does WCAG require an alternative to dragging?

Yes at WCAG 2.2 Level AA. Success criterion 2.5.7 Dragging Movements requires that all functionality that uses a dragging movement can also be achieved with a single pointer without dragging, unless dragging is essential. The text is in the W3C WCAG 2.2 Recommendation. The W3C explanation is in Understanding Success Criterion 2.5.7.

What has to replace the drag?

Another single-pointer path that does the same job without a press-move-release path. Move-up and move-down buttons for a sortable list, numeric inputs or stepped controls for a slider, or click-to-select plus click-to-place instead of drag-and-drop are typical patterns. Keyboard operability is covered separately under keyboard access; 2.5.7 is about pointer alternatives to dragging. Control size still matters for those alternatives—see target size.

Does the Title II web rule include 2.5.7?

No. The Department of Justice rule for state and local government websites names WCAG 2.1 Level AA, not 2.2. Criterion 2.5.7 was added in WCAG 2.2, so Title II does not include Dragging Movements. Public entities still must meet WCAG 2.1 AA under the rule’s deadlines. Who must comply is on the Title II web rule page. If a contract, policy, or procurement document requires WCAG 2.2 AA, then 2.5.7 applies. The version gap is on the WCAG 2.1 vs 2.2 page.

Where does dragging show up on sites?

Drag-and-drop product sorting, wishlist reordering, range filters, and map-based store pickers are common on accessible ecommerce flows. If those interactions only work by dragging, add a single-pointer path that does not require dragging so people using assistive pointing devices or limited dexterity can finish the task.