WCAG 2.5.7 Dragging Movements
WCAG 2.5.7 Dragging Movements explained: anything you can drag also needs a single-pointer alternative, unless dragging is essential. How to test it.
Table of contents
WCAG 2.5.7 Dragging Movements is a Level AA success criterion, added in WCAG 2.2. This page is part of the WCAG 2.2 success criteria guide. It explains the rule in plain English, who it helps, what passing and failing code look like, and how to test it by hand and with AccessBell, a website accessibility monitoring tool. AccessBell is not an overlay.
What WCAG 2.5.7 Dragging Movements 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.
That sentence is the heart of the criterion. The exceptions and notes are in the WCAG 2.2 Recommendation and the Understanding document for 2.5.7 Dragging Movements.
What WCAG 2.5.7 means in plain English
WCAG 2.5.7 Dragging Movements is new in WCAG 2.2. If a person must press, hold and move the pointer to use something, the same action also has to work with a single click or tap, unless dragging is essential. A list that reorders only by dragging fails. The same list with Up and Down buttons, or a menu of positions, passes.
Dragging is essential when the path itself is the point, such as a signature or a freehand drawing. A slider the browser provides and the site has not rebuilt is the user-agent exception. A map someone must drag in order to pan usually needs another way to move the view, such as arrow buttons, because panning is not the only way to offer that function. The W3C’s short version is: for any action that involves dragging, provide a simple pointer alternative.
Who WCAG 2.5.7 helps
People with tremors, limited hand strength or pain who cannot hold a pointer button down while moving. People using a head pointer or another single-tap device. Keyboard access is a separate criterion, 2.1.1 Keyboard. 2.5.7 is about pointer users who can click but cannot drag.
Pass and fail examples
<ul class="sortable">
<li draggable="true">Blue shirt</li>
<li draggable="true">Red shirt</li>
</ul> <li>
<span>Blue shirt</span>
<button type="button">Move up</button>
<button type="button">Move down</button>
</li> How to test WCAG 2.5.7
- Find every drag: carousels with a swipe-only next image, sliders, sortable lists, kanban boards, range inputs the theme has rebuilt, maps and “compare” image wipes.
- Try to do the same task with one click or tap and no hold. Buttons, a select, or a click-to-pick-up then click-to-drop pattern can pass.
- If the only alternative is a keyboard shortcut, that does not meet 2.5.7. The alternative has to work with a single pointer.
- Leave a native scrollbar and a native range input alone if the site has not restyled their behavior.
Testing WCAG 2.5.7 with AccessBell
Dragging is a behavior, so a website accessibility monitoring tool cannot reliably see that a carousel only advances by a swipe. AccessBell reports 2.5.7 for manual review unless an axe-core rule matches a known pattern. Operate each draggable control with a single click before you call it done.
Check your site for this with a free scan of one public page. AccessBell is a website accessibility monitoring tool, not an overlay.
Common failures on Shopify, WordPress, Wix and Squarespace
These are patterns in how the builders work. They are not counts from AccessBell scans. Where a platform hosts the screen, a merchant may not be able to change it, and an unscanned page is not a pass.
Shopify
Product galleries and “shop the look” sections often drag to the next image with no Next button. Theme carousels and cart upsells are the place to add buttons. Hosted checkout is less often the source. The store checklist includes 2.5.7. Scan the product page with the Shopify checker, then try the gallery with one click.
WordPress
Slider and page-builder carousels, and WooCommerce gallery plugins, frequently support only swipe. Turn on arrow controls in the plugin, or pick a pattern that moves on click. Check the page with the WordPress checker.
Wix
Slideshow strips and some store galleries drag. The Accessibility Wizard’s gaps, including galleries it does not fully cover, are in the Wix checklist. Add arrows or dots that work on a single click, publish, and test. The Wix checker covers what automation can see.
Squarespace
Gallery blocks and background sliders can be swipe-first. Squarespace’s media guidance is cited in the Squarespace checklist. Confirm the gallery has a clickable control for the next item on the published page, not only a drag.
Level and conformance
Level AA, added in WCAG 2.2, under Input Modalities. It is not in WCAG 2.1. The exception for essential dragging is narrow: the movement has to be required for the function, not merely the design the theme chose. See What’s New in WCAG 2.2 for the W3C’s short statement of the rule.
Conforming at Level AA means meeting every Level A and Level AA criterion that applies, not only the ones labeled AA. See the WCAG 2.2 conformance requirements. This page explains the technical rule. It is not a legal opinion. Read the disclaimer.
Related WCAG criteria
- 2.5.1 Pointer Gestures (Level A, WCAG 2.1)
- 2.1.1 Keyboard (Level A, WCAG 2.0)
- 2.5.8 Target Size (Minimum) (Level AA, WCAG 2.2)
- 2.5.2 Pointer Cancellation (Level A, WCAG 2.1)
Every criterion is listed in the WCAG 2.2 success criteria guide.
Frequently Asked Questions
What level is WCAG 2.5.7 Dragging Movements?
Level AA. It was added in WCAG 2.2 and is not part of WCAG 2.1.
Does a carousel that only swipes fail 2.5.7?
Yes, if the next slide cannot also be reached with a single click or tap. Add a Next and Previous button. A keyboard alternative alone does not meet this criterion, which is about pointer input.
Is a signature pad a failure of 2.5.7?
Drawing a signature is a case where dragging is essential, because the path is the content. The exception is for that kind of function, not for a list that would work with buttons.
Sources
- W3C: Understanding 2.5.7 Dragging Movements (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.