WCAG 2.5.7: Dragging Movements
Level AAQuick answer: Tasks that require dragging need a simpler alternative like tap, click, or buttons.
What This Means
On ecommerce sites, Dragging Movements usually shows up in repeating storefront components such as product cards, PDP media, search results, cart drawers, checkout forms, and support content. If the live experience depends on patterns like gift-box builders require drag-and-drop to arrange items. or before-and-after comparison sliders only work by dragging the handle., disabled shoppers can lose context or get blocked before purchase.
This criterion matters because D2C teams often fix the homepage but miss reusable app blocks, campaign pages, and mobile-specific UI. The practical standard is simple: build the same outcome for keyboard users, screen-reader users, low-vision users, and anyone relying on captions, labels, structure, or predictable behavior.
For Shopify, WooCommerce, and custom storefronts, the fastest remediation path is usually template-level work. Fix the repeated component once, then retest every place it appears across browse, buy, and post-purchase journeys.
Common Violations on Ecommerce Sites
- Gift-box builders require drag-and-drop to arrange items.
- Before-and-after comparison sliders only work by dragging the handle.
- Filter chips must be dragged to reorder saved preferences.
- Captcha puzzles require dragging pieces with no alternate path.
How to Fix It
Start with the live customer journey, not isolated components in Storybook or Figma. Audit the problem on category pages, product detail pages, quick views, cart, checkout, account, and help templates.
- Add click-to-select or button-based alternatives alongside drag interactions.
- Offer reorder controls like Move up and Move down for sortable lists.
- Use standard buttons for carousels and sliders when drag is only a convenience.
- Never block checkout or account recovery behind a drag-only challenge.
On Shopify, fix the theme section or app block that repeats the defect. On WooCommerce and WordPress, update the template override or plugin output. In custom React or headless storefronts, move the fix into shared components so merchandisers cannot reintroduce the issue with every campaign.
Code Example
<!-- Before -->
<div draggable="true">Small gift box</div>
<!-- After -->
<button type="button">Add small gift box</button>FAQ
What is WCAG 2.5.7?
Tasks that require dragging need a simpler alternative like tap, click, or buttons.
How does WCAG 2.5.7 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with gift-box builders require drag-and-drop to arrange items. and before-and-after comparison sliders only work by dragging the handle. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 2.5.7 violations?
Start by auditing the live storefront, then Add click-to-select or button-based alternatives alongside drag interactions.; Offer reorder controls like Move up and Move down for sortable lists.; Use standard buttons for carousels and sliders when drag is only a convenience.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 2.5.7 → Free ADA Compliance Scan