Category: Mobile Accessibility

Dragging Movements

Also known as: WCAG Success Criterion 2.5.7, SC 2.5.7, Drag-and-Drop Accessibility

Simply put

Dragging movements are actions where a user grabs an element on screen and moves it from a starting point to a different position, such as drag-and-drop interfaces. Under a WCAG guideline, functionality that relies on dragging should also be operable with a simpler single-pointer action (like a tap or click), unless the dragging is essential to the task. This helps people who have difficulty performing precise or sustained dragging gestures.

Formal definition

Dragging Movements refers to WCAG 2.2 Success Criterion 2.5.7, a Level AA criterion introduced in WCAG 2.2. It requires that all functionality operated through a dragging movement can also be achieved with 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, as described by the W3C, involves the user grabbing an element and moving it to another position; the start and end points of the motion are significant while the actual path taken is not. Meeting this criterion typically involves providing an alternative single-pointer mechanism (for example, tap-to-select-then-tap-to-place, or button controls) in addition to any drag-based interaction. Note that this entry describes the technical guideline only and is not legal advice; applicable legal obligations vary by jurisdiction and should be evaluated with qualified counsel.

Why it matters

Dragging movements can create significant barriers for people who have difficulty performing precise or sustained gestures. Grabbing an element, holding the pointer down, and moving it accurately to a target requires fine motor control and coordination that many users cannot reliably achieve. This includes people with motor disabilities such as tremors, people using head pointers or switch devices, and people navigating with a single finger or an alternative pointing method. When a task can only be completed by dragging, these users may be locked out of the functionality entirely.

WCAG 2.2 Success Criterion 2.5.7 (Dragging Movements), a Level AA criterion introduced in WCAG 2.2, addresses this by requiring that functionality operated through dragging also be achievable with a simpler single-pointer action, such as a tap or click, unless the dragging is essential to the task. As described by the W3C, a dragging movement involves grabbing an element and moving it to another position, where the start and end points matter but the actual path taken does not. Providing an alternative single-pointer mechanism means the underlying task remains available to users who cannot perform the drag.

Because this criterion was added in WCAG 2.2, teams that previously conformed to WCAG 2.0 or 2.1 will not have addressed it under those earlier versions. It is worth noting that meeting this success criterion supports operability for a specific set of interaction barriers but does not on its own guarantee an accessible experience or legal compliance; applicable legal obligations vary by jurisdiction and should be evaluated with qualified counsel.

Who it's relevant to

Front-end and UX Engineers

Developers building drag-and-drop interfaces, sortable lists, sliders, or map interactions are responsible for providing a single-pointer alternative that accomplishes the same task. Understanding SC 2.5.7 helps them design components where the start and end points of an action can be reached through tap or click controls, not only through dragging.

UX and Interaction Designers

Designers who specify drag-based patterns should plan an equivalent non-dragging path from the outset, such as select-then-place flows or explicit move buttons. Designing this alternative early avoids retrofitting and helps ensure the task remains operable for users who cannot perform sustained or precise gestures.

Accessibility and QA Testers

Testers evaluating conformance to WCAG 2.2 need to verify that every drag-operated function has a working single-pointer alternative. Because this is a WCAG 2.2 addition and involves interaction behavior, it generally requires manual and assistive technology testing, as automated tools detect only a portion of accessibility issues.

Compliance Officers and Legal Counsel

Those tracking accessibility obligations should be aware that SC 2.5.7 is a Level AA criterion new to WCAG 2.2, so conformance targets referencing earlier WCAG versions would not have covered it. Whether and how this criterion factors into any legal obligation depends on jurisdiction, applicable regulation, and current guidance, and should be evaluated with qualified counsel.

Users with Motor Disabilities

People who use switch devices, head pointers, or a single finger, and those with tremors or limited fine motor control, benefit directly when dragging is not the only way to complete a task. A single-pointer alternative allows them to reach the same start and end points without a sustained, precise gesture.

Inside Dragging Movements

Dragging Movement

An interaction that requires a user to press down on a control, move it along a path, and release it at a target location, such as sliders, drag-and-drop interfaces, or reordering list items.

Success Criterion 2.5.7 Dragging Movements

A WCAG success criterion added in WCAG 2.2 at Level AA that addresses functionality relying on dragging. It generally requires that any function operable through a dragging movement can also be operated with a single pointer without dragging, unless dragging is essential.

Single-Pointer Alternative

An alternate means of accomplishing the same task using simple pointer actions such as taps or clicks, so users who cannot perform a sustained drag gesture can still complete the operation.

Essential Exception

A carve-out recognizing that where dragging is fundamental to the activity and a non-dragging alternative would change the nature of the function, the requirement may not apply.

Motor and Dexterity Considerations

The rationale for the criterion, which centers on users who have difficulty performing precise, sustained path-based gestures, including people using assistive technologies or those with limited fine motor control.

Common questions

Answers to the questions practitioners most commonly ask about Dragging Movements.

Does the Dragging Movements success criterion ban drag-and-drop functionality?

No. The criterion does not prohibit dragging interactions. It requires that any functionality operated through a dragging movement also be operable through a single pointer without dragging, unless dragging is essential. You can keep drag-and-drop as an option while providing an alternative, non-dragging method to achieve the same result.

Is Dragging Movements just a duplicate of the older Pointer Gestures requirement?

They are distinct. Pointer Gestures addresses path-based or multipoint gestures such as pinch or swipe, while Dragging Movements specifically addresses actions that require pressing, moving along a screen, and releasing. A control can satisfy one and not the other, so both should be considered separately when evaluating pointer-based interactions.

What is a common way to provide a non-dragging alternative to a slider control?

A slider that requires dragging the thumb can often be paired with single-tap or single-click targets, such as increment and decrement buttons or a text input field where a value can be entered directly. This lets users adjust the value without performing a continuous dragging movement.

How can drag-and-drop list reordering be made operable without dragging?

Reordering that relies on dragging items can commonly be supplemented with single-pointer controls, such as move up and move down buttons for each item, or a menu that lets the user select a new position. The dragging option can remain available alongside these alternatives.

When might dragging be considered essential and therefore exempt?

Dragging may be treated as essential when the movement itself is fundamental to the activity and cannot be replaced without changing the function, such as certain freeform drawing or signature tasks. The exception is intended to be narrow, so it is generally advisable to confirm that no single-pointer alternative could achieve the same outcome before relying on it.

Can automated testing confirm that this criterion is met?

Automated tools can detect only a portion of accessibility issues and are generally limited in evaluating pointer interactions like dragging. Verifying that a non-dragging alternative exists and functions correctly typically requires manual testing with a single pointer, and this evaluation should be part of a broader assessment rather than a standalone check.

Common misconceptions

Dragging Movements (SC 2.5.7) has always been part of WCAG, so older 2.0 or 2.1 conformance covers it.

This success criterion was introduced in WCAG 2.2. Conformance claims based on WCAG 2.0 or 2.1 do not include it, so teams targeting 2.2 should evaluate it separately.

Providing keyboard access is enough to satisfy the Dragging Movements requirement.

The criterion specifically concerns pointer input and generally calls for a single-pointer alternative to dragging. Keyboard operability is addressed by other criteria and does not by itself resolve the pointer-based requirement.

Meeting SC 2.5.7 guarantees the interface is usable for everyone and legally compliant.

Meeting a success criterion supports conformance but does not guarantee an accessible experience for all users or immunity from legal claims. Manual and assistive technology testing remain necessary, and legal obligations depend on jurisdiction and evolving case law.

Best practices

Provide a single-pointer alternative, such as tap or click targets, for any function that can be accomplished by dragging, unless the dragging is genuinely essential to the task.

For sliders and similar controls, offer discrete controls (such as increment and decrement buttons or selectable values) alongside the drag interaction.

For drag-and-drop and reordering interfaces, add non-dragging methods like select-then-place, move-up/move-down buttons, or menu-based reordering.

Document and justify any reliance on the essential exception, confirming that a non-dragging alternative would fundamentally change the function.

Test dragging-dependent features with manual and assistive technology methods, since automated checks detect only a portion of these issues.

Confirm which WCAG version you are targeting, and if targeting WCAG 2.2, evaluate SC 2.5.7 explicitly rather than assuming prior-version conformance covers it. This guidance is not legal advice; consult qualified counsel on applicable obligations.