WCAG 2.5.7 Dragging Movements

Success criterion 2.5.7 is new in WCAG 2.2. It helps people who cannot press and hold while moving a pointer: people with tremors or limited dexterity, and people using a trackball, head pointer, eye-gaze system or speech control. It is level AA and part of EN 301 549 (clause 9.2.5.7).

What the criterion requires

All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.

• A dragging movement starts with a press on an element, moves the pointer while held, and ends with a release.
• A single-pointer alternative is a click, tap or long press — for example tapping a position, or tapping "up" and "down" buttons.
• The criterion applies to pointer actions the web content interprets, not to dragging that operates the browser or assistive technology.

W3C examples: a slider where tapping the track moves the handle, a sortable list where an item can be moved with buttons, and a map with arrow buttons to pan.

Typical failures on an online shop

• a price range filter with two drag-only handles;
• a "compare" or before/after image slider that only works by dragging the divider;
• sortable wishlists, gift registries or product bundles that can be reordered only by drag and drop;
• an image uploader (for custom prints or reviews) that accepts files only by dragging them onto a drop zone;
• a store locator map that pans only by dragging.

How to check it

Automated: there is no axe-core rule for this criterion. Whether a drag action has a non-drag alternative depends on scripted behaviour, so it needs a manual check.

By hand: list every element that you can drag: sliders, carousels, maps, sortable lists, drop zones, cropping tools. For each function, try to achieve the same result using only single clicks or taps, never holding the button down while moving. If you cannot, it fails.

How to fix it

• Make slider tracks clickable and add number fields or +/− buttons next to range filters.
• Add "Move up" / "Move down" buttons, or a position menu, to sortable lists.
• Always pair a drop zone with a "Choose file" button (a native <input type="file">).
• Add arrow buttons and zoom controls to maps.
• For before/after sliders, add buttons or a toggle to switch views.

Related criteria

• 2.5.1 Pointer Gestures — multipoint and path-based gestures need alternatives.
• 2.5.8 Target Size (Minimum) — the alternative buttons must be large enough.
• 2.1.1 Keyboard — the same functions must work from the keyboard.

Frequently asked questions

Does a price range slider fail WCAG 2.5.7?

Only if the handles can be moved by dragging alone. Letting users click or tap on the track to move a handle, or adding plus and minus buttons or number inputs, gives the single-pointer alternative 2.5.7 asks for.

Is keyboard support enough for 2.5.7?

No. Keyboard operation is covered by 2.1.1; 2.5.7 asks for a way that works with a single pointer, such as clicks or taps, without dragging.

What is the difference between 2.5.7 and 2.5.1?

2.5.1 Pointer Gestures covers multipoint and path-based gestures, where the path matters. 2.5.7 covers dragging, where only the start and end points matter, such as moving a slider handle or a list item.