Dragging Movements: Offer a Click Alternative
Also called: Drag and drop alternative, Dragging alternative, Single pointer alternative
Definition
Dragging Movements is WCAG success criterion 2.5.7. All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the browser provides it.
Dragging movements are actions where you press on an item, hold it and move the pointer to a new position before letting go – drag and drop in a sortable list, moving a slider handle, panning a map. WCAG 2.2 requires that each of these actions also works with simple clicks or taps. Some people cannot hold a button down and move precisely at the same time.
What it means
WCAG 2.5.7 Dragging Movements is a Level AA criterion, new in WCAG 2.2: 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.
It applies to web content that interprets pointer actions. Browser scrolling and pull-to-refresh are out of scope – but if your page suppresses them or builds its own scrolling, it is in scope.
| Component | Single-pointer alternative W3C describes |
|---|---|
| Sortable list | Buttons next to each item to move it up or down |
| Slider | Click or tap any point of the track to set the value |
| Map | Up, down, left and right buttons to move the view |
| Kanban board | Select a card with one tap or click, then use an arrow button or choose the target column |
W3C names who benefits: people who have difficulty dragging, including users of trackballs, head pointers, eye-gaze systems and speech-controlled mouse emulators.
Examples
<!-- Sortable list: dragging still works, but each item also has buttons -->
<ol class="sortable">
<li>
Homepage banner
<button type="button" aria-label="Move Homepage banner up">▲</button>
<button type="button" aria-label="Move Homepage banner down">▼</button>
</li>
<li>
Newsletter sign-up
<button type="button" aria-label="Move Newsletter sign-up up">▲</button>
<button type="button" aria-label="Move Newsletter sign-up down">▼</button>
</li>
</ol>
<!-- Slider: in common browsers a click on the track of a native range input sets the value -->
<label for="budget">Budget</label>
<input id="budget" type="range" min="0" max="1000" step="50">In common browsers the native <input type="range"> lets people click the track, so it already offers a single-pointer way to set the value. Custom sliders built from divs must add this themselves – or provide plus and minus buttons or a number field.
Add move buttons to sortable lists, let people click the slider track, give maps zoom and arrow buttons, allow "select, then place" on boards and in file uploads, and make every extra control at least the minimum target size.
Make drag and drop the only way to reorder, upload or assign items, build sliders that only react to dragging the handle, or replace dragging with a swipe gesture.
How to check dragging movements
Questions
Is drag and drop allowed under WCAG 2.2?
Yes. Dragging can stay. WCAG 2.5.7 only requires that the same result can also be reached with a single pointer without dragging, such as clicks or taps on buttons.
Does keyboard support meet 2.5.7?
No. W3C says keyboard equivalence does not automatically meet 2.5.7. People who use a pointer but cannot drag need controls they can click or tap.
Do sliders fail dragging movements?
Not if they offer a click alternative. Letting users click any point on the track, or adding plus and minus buttons or a number field, meets the criterion. In common browsers the native range input supports track clicks.
When is dragging essential?
Rarely. WCAG calls something essential only if removing it would fundamentally change the information or functionality and it cannot be achieved in another conforming way. Reordering, uploading or moving a map view can all be done with clicks, so they are not essential.
Related terms
Target Size: 24 × 24 px for Every Click Target
Target Size (Minimum) is WCAG success criterion 2.5.8. The size of the target for pointer inputs is at least 24 by 24 CSS pixels, unless spacing, an equivalent control, inline text, the user agent or an essential presentation makes an exception.
Read definition: Target Size: 24 × 24 px for Every Click TargetKeyboard Navigation: WCAG 2.1.1 Explained
Keyboard navigation means that every function of a website can be reached and operated with a keyboard alone – usually with Tab, Shift+Tab, Enter, Space and the arrow keys. WCAG 2.1.1 requires it at Level A.
Read definition: Keyboard Navigation: WCAG 2.1.1 ExplainedFocus Visible: WCAG 2.4.7 and Visible Focus Styles
Focus visible means that a website shows a visible indicator – usually an outline – on the link, button or field that currently has keyboard focus. WCAG 2.4.7 requires it at Level AA.
Read definition: Focus Visible: WCAG 2.4.7 and Visible Focus StylesPointer Gestures: A Single Tap Must Do It Too
Pointer Gestures is WCAG success criterion 2.5.1 (Level A). All functionality that uses multipoint or path-based gestures can also be operated with a single pointer without a path-based gesture, unless the gesture is essential.
Read definition: Pointer Gestures: A Single Tap Must Do It Too