- Level
- AA
- Since
- WCAG 2.2
2.5.7 Dragging Movements
Anything done by dragging, such as reordering a list or moving a slider, must also be possible with single taps or clicks, unless dragging is essential.
/ What it requires
A dragging movement is an operation where the pointer engages an element on the down-event and the element, or a representation of its position, follows the pointer until the up-event. It asks a person to press, hold, move and release in one controlled motion. This criterion asks that any function operated that way can also be achieved by a single pointer without dragging: tap an item and then its destination, use arrow buttons or a menu, or type a value into a field. It helps people with tremors or a weak grip, and people using a trackball, head pointer, eye gaze or speech-controlled mouse, for whom dragging is error-prone or impossible.
Dragging may stay as the only way when it is essential, or when the browser provides it and the author has not modified it, such as scrolling a page or an area made scrollable with CSS overflow. A script that replaces the browser's own scrolling brings that scrolling into scope. The alternative does not have to be the same component: a colour wheel passes if text fields for the colour value sit beside it. Keyboard support is judged separately under 2.1.1 and does not satisfy this criterion unless it comes with controls that can be clicked or tapped, and the alternative may not be a swipe either, which would fail 2.5.1.
This criterion is new in WCAG 2.2 and is not part of WCAG 2.0 or 2.1.
/ How pages fail it
- A sortable list can be reordered only by dragging items up and down, with no move buttons and no position field.
- Cards on a kanban board change status only when dragged to another column.
- A custom range slider changes value only when its thumb is dragged, and clicking the track does nothing.
- An image cropper sets its selection only by dragging the corners, with no numeric fields and no way to place the corners by clicking.
- A matching quiz asks people to draw a line from each item to its pair, and clicking one item and then the other does nothing.
/ How to check it yourself
- List every function that responds to dragging: sortable lists, kanban boards, sliders, maps, crop and selection tools, colour pickers, carousels that can be pulled, and matching or drawing exercises.
- Operate each one with taps or clicks only, never holding the button down while moving.
- If the only alternative is a keyboard, it does not count here. Check that there is something on screen to click or tap.
- Check that the alternative can reach the same results as the drag, such as any position in the list or any column on the board.
- Set aside scrolling the page or a scrollable box with the browser's own scrolling, which the browser provides, unless a script has replaced it.
/ How to fix it
- In sortable lists, add move up and move down buttons to each item, or a number field for its position.
- On boards, add a "Move to" menu on each card that lists the other columns.
- Build sliders on input type="range", or let a custom track accept a click or tap at any point, and add a text field for an exact value.
- In crop and selection tools, let people click one corner and then the opposite corner, and offer numeric fields for position and size.
- Give draggable maps and carousels buttons for panning and for the previous and next item.
/ What our scanner checks
Nothing in our scan detects dragging. A drag is handled in script through pointer events or the drag and drop API, the scan does not read those handlers, and it never drags anything. The HTML_CodeSniffer release in our validator has no sniff for 2.5.7 at all. A person checks each draggable feature for a click or tap alternative in a manual audit.
/ Who fails it, in our own measurements
The weekly index has no figures for this criterion, because none of the checks the site scan runs can test it. A person judges it, which is what a manual audit is for.
One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.
/ Questions about this criterion
Is drag and drop allowed under WCAG 2.2?
Yes. Dragging can stay. What 2.5.7 requires is a second way to reach the same result with a single pointer and no dragging, such as move buttons, a menu or a tap on the destination. Dragging with no such alternative fails, unless it is essential or the browser provides it unmodified.
Does keyboard support for drag and drop meet 2.5.7?
Not on its own. Keyboard access is required by 2.1.1 Keyboard and is checked separately. 2.5.7 is about people who use a pointer, often on a touch screen with no keyboard, so the alternative has to be something they can click or tap.
Is 2.5.7 Dragging Movements required for AA conformance?
Under WCAG 2.2, yes. It is a level AA criterion added in WCAG 2.2, so an audit against WCAG 2.2 AA includes it. It is not part of WCAG 2.0 or 2.1, so an audit against those versions does not test it.
