# The Dragging Movements Metric: Why Drag-and-Drop Checkouts Fail WCAG 2.5.7

Source: https://complymetric.com/blog/2026-11-14-dragging-movements-metric-drag-drop-checkout.html

*A shopper with a hand tremor tries to reorder their cart by dragging an item up the list. They cannot hold the drag steady. There is no up button, no move control, no alternative at all. The cart is unusable for them, and the store fails a criterion it has never heard of.*

## The criterion in one sentence

WCAG 2.5.7, Dragging Movements, is a Level AA criterion in WCAG 2.2. It says that any functionality that uses a dragging movement must also be operable with a single pointer, without dragging, unless dragging is essential. The examples the W3C gives are direct: a slider gets plus and minus buttons or a number input, a drag-to-reorder list gets move up and move down buttons, a map gets arrow buttons as well as drag-to-pan. The drag can stay. It just cannot be the only way.

The reason keyboard support alone does not meet it is worth stating plainly. A keyboard user can often operate a drag control through arrow keys, but a pointer user with a motor impairment cannot drag steadily, and the criterion is about pointer input, not keyboard input. Someone with a tremor can click. They cannot hold and drag. A single click alternative is the difference between usable and unusable.

The places this shows up in ecommerce are specific: drag-to-reorder cart items, drag-to-resize image crops in custom product builders, swipe-to-delete saved items, sliders for price ranges and quantities, and signature pads at checkout. A signature pad that requires drawing with a finger fails unless there is a typed-name alternative. A price slider with no number input fails unless there is a way to type the value.

## How to measure it

The metric is a count. Inventory every drag interaction on the site, and for each one ask whether a single-pointer alternative exists. The score is the share of drag interactions with an alternative. A store with four drag interactions and one alternative scores 25%, and the number tells the team exactly what to fix: the three interactions without buttons.

Test it the way a user would. Open the cart on a touch device and try to reorder items without dragging. Try to set a price range without touching the slider. Try to delete a saved address without swiping. If any of those actions has no tap or click alternative, it fails. [Target size is the sibling metric](2026-11-13-target-size-metric-24px-wcag-2-5-8.md): a 24 by 24 pixel minimum that decides whether the alternative button is itself usable. [Redundant entry is the same pattern at a different layer](2026-11-12-redundant-entry-metric-retyping-tax.md): asking the shopper to do work the system could do for them.

## The fix is buttons, not a redesign

Every drag interaction has a button-shaped fix. A reorderable list gets move up and move down buttons next to each item. A slider gets plus and minus buttons and a number input. A swipe-to-delete gets a visible delete button. A signature pad gets a typed-name option. None of these change the design. They add a control next to the one that already exists.

That is why this metric is worth tracking separately from the rest of the audit. It is cheap to fix, it is easy to count, and it is the kind of failure that never shows up in automated scans, because a scanner cannot tell whether a drag control has a non-drag alternative. It takes a human with a list. [Accessible authentication is the same kind of gap](2026-11-12-accessible-authentication-metric-memory-test.md): a criterion that only a human tester finds, and a fix that is usually a button.

## Frequently asked questions

### Does keyboard support satisfy WCAG 2.5.7?

Not automatically. The criterion is about pointer input: a user with a motor impairment who can click but cannot drag steadily needs a single-pointer alternative. Keyboard arrow keys help keyboard users, but they do not give a pointer user a way to act without dragging.

### What counts as a dragging movement?

Any action that requires holding a pointer down and moving it: drag-to-reorder lists, sliders, map panning, swipe-to-delete, drag-to-resize, and signature pads. If the only way to do it is to drag, it falls under 2.5.7.

### Is dragging ever essential, and exempt?

The criterion exempts dragging only where it is essential to the function, which is a narrow exception. A drawing app is the usual example. Reordering a cart, setting a price range, or deleting a saved item is never essential dragging, because a button does the same job.

### How do I count the dragging movements metric?

Inventory every drag interaction on the site, then check each one for a single-pointer alternative: a button, a number input, or a menu choice. The score is the share of drag interactions that have one. Anything below 100% is a list of fixes, not a judgment.