2.5.7 Dragging Movements

1. What is the goal of this criterion?

Moving a card on a Kanban board, reordering a list by drag and drop, dragging a slider with the mouse – second nature for many people. But what if precise dragging and dropping becomes an insurmountable obstacle? People with motor disabilities, people with tremors or users of specialized input devices often can’t perform these movements at all, or only with great effort.

The goal of WCAG Success Criterion 2.5.7 is clear: every function operated by dragging needs a single-pointer alternative that doesn’t require dragging. No holding down while moving – just simple clicks or taps.

2. What exactly does it require?

This criterion covers every function that requires a dragging movement – grabbing an element, moving it with the button held or finger down, and letting go.

For every such function, there must be an alternative that works with a single pointer and no dragging:

• Simple clicks or taps instead of a movement with the button held down
• Several separate actions in a row are fine, such as selecting an item first and then its destination
• Menus, buttons or other controls as the alternative

Exceptions apply when:

• dragging is essential – such as freehand drawing, where the path of the movement is the result
• the functionality is determined by the browser and not modified by you – such as dragging a native scrollbar

Important: a keyboard-only alternative is not enough for 2.5.7. People who work with a pointer need an alternative they can operate with that pointer. Keyboard access is still required – that’s covered by Keyboard.

A concrete example: a sortable list that can be reordered by drag and drop also offers buttons to move individual items up or down.

3. Why does it matter for accessibility?

Imagine trying to move an important file into a folder while your hand shakes – or using eye tracking, where held-down movements are barely possible. Without an alternative, the function is closed to you.

Alternatives to dragging improve accessibility because they:

• give people with motor disabilities access to every function
• help people who use a trackball, head pointer or eye tracking
• support people with tremors or limited fine motor control
• help in awkward situations, such as one-handed use or on a moving bus
• make interaction more robust and forgiving for everyone

And finally: many people simply prefer an alternative – for example because dragging on a small touchscreen easily clashes with scrolling.

4. How to meet the criterion

The quality of the alternatives decides whether a drag-and-drop feature is accessible – or just awkward. Here are some proven tips:

Good alternatives are:

• easy to understand – it’s obvious how they work
• equivalent – the same result can be achieved
• clearly visible – nobody has to hunt for them
• consistently placed – similar functions in similar places

Proven patterns:

For sortable lists: “Move up” and “Move down” buttons next to each item, or a select field for the target position.

For Kanban boards: a menu on each card with options like “Move to: In progress”.

For file uploads: always offer a “Choose file” button in addition to the drop zone.

For sliders: tapping the track sets the value directly, plus plus/minus buttons or an input field for the exact value.

For maps: buttons to pan the view in addition to dragging.

<li>
  Task: Write proposal
  <button type="button">Move up</button>
  <button type="button">Move down</button>
</li>

Technical notes:

• The original drag and drop can stay – the alternative is added on top.
• The alternative doesn’t have to look the same, it just has to work equivalently.
• Make sure the extra buttons are large enough – see Target Size (Minimum).

5. Why this criterion matters for businesses

2.5.7 is new in WCAG 2.2. EN 301 549, the standard behind the European Accessibility Act and its German implementation, the BFSG, currently references WCAG 2.1 Level AA – so 2.5.7 is not explicitly required (as of October 2026). It’s still strongly recommended, especially for web applications with lots of drag-and-drop features. This section is general information, not legal advice.

1. Reach more people

Drag and drop without an alternative excludes not only people with disabilities but also anyone in an awkward situation: using one hand, working with an imprecise input device or on the move. With alternatives, your software works for everyone.

2. Better usability

Simple alternatives are often more precise and faster than dragging. Many people prefer clear buttons or menus – especially for important actions.

3. Fewer errors

Dragging easily goes wrong: the wrong target, an accidental release, an interrupted movement. Clear alternatives reduce these errors – and the support requests that come with them.

6. The success criterion in the W3C’s words

Success Criterion 2.5.7 Dragging Movements (Level AA)

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.

Note: This requirement applies to web content that interprets pointer actions (i.e., this does not apply to actions that are required to operate the user agent or assistive technology).

In short: anything that can be operated by dragging must also work with a single pointer without dragging – unless dragging is essential or determined by the browser.