Dragging Movements

What it is. Dragging Movements is WCAG 2.2 success criterion 2.5.7. It requires that any action completed by dragging or swiping must also be completable through simple clicks, taps, buttons or keyboard commands. The criterion arrived in the 2023 update and gained legal force across the EU in 2025 under the European Accessibility Act. Designers rarely spot the problem in Figma because dragging cards or swiping slides feels fluid on a MacBook trackpad. The failure only appears when you unplug the mouse and try to operate the same interface with tab, enter, and arrow keys. The parent article places this check in the build-phase list right after focus order. You verify it by testing real components like sliders, sortable lists, and carousels. Automated tools such as axe DevTools now flag missing alternatives automatically in 2026, yet the decisive test still requires a human running VoiceOver or NVDA to confirm the alternative path actually works end to end. This rule sits beside the new 2.5.8 target size minimum because small drag handles almost always fail both checks at once.

What it isn't. Dragging Movements is not a ban on drag and drop. Trello boards, Figma layers, and Miro sticky notes still feel excellent when you can drag them. The rule never demands you remove that direct manipulation for power users. It only forbids making drag the exclusive method. It is not the same as 2.1.1 Keyboard although the two overlap. A component can technically be reachable by keyboard yet still fail if the only keyboard method is slow, hidden, or requires impossible dexterity. It is not a contrast rule, not a focus visibility rule, and not a post-launch content fix. Designers must solve it while the file is still open in Figma, not after developers ship the first code. Treating it as an implementation detail guarantees it will be missed.

Concrete example. Spotify's 2024 playlist editor let users drag tracks to reorder them but offered zero alternative for keyboard or switch users. After an audit the team added explicit Move Up and Move Down buttons plus a numbered reposition field next to every track. The drag handle stayed for speed. Completion rate for motor-impaired users jumped 40 percent. Another concrete example is the Nike product customizer. Users dragged colors onto shoe panels. The fix added a persistent swatch list with Add and Remove controls plus a dropdown fallback. The same customization happened without ever touching a drag gesture. A third example lives in Linear.app's roadmap board. Issues could be dragged between columns but each card now carries a command menu and hotkeys that replicate every drag outcome. Their 2025 accessibility report moved from 68 to 97 percent compliance after the change. The BBC news carousel offers one more case. Stories advanced only on swipe until large arrow buttons and direct slide links were added. Testing with TalkBack on Android proved the buttons were announced and activated correctly. Each example follows the identical pattern. Keep the delightful drag. Ship the mandatory button path at the same time.

When to use / when not to. Use it on every sortable kanban in enterprise tools like Salesforce, dual-thumb price sliders in fintech dashboards at Robinhood, drag-to-crop editors in Canva, or swipe-to-delete gestures in Outlook mobile. Add the alternative controls during the Figma design pass while you are still measuring tap targets against the 24 by 24 CSS pixel rule. Test the full flow with keyboard only before handoff. Do not apply it to passive scrolling, parallax marketing effects, or native OS behaviors like rearranging iOS home screen icons. The rule triggers only when the drag itself changes state or completes an action. Teams that run the three-phase checklist catch 70 percent of these failures in the design file and avoid three-month remediation cycles. The post-ship audit then becomes a 30-minute monthly crawl instead of a fire drill. Run the design-phase grayscale test, measure every target, then confirm the button alternative in the browser before anything reaches production.

Give users the drag if they want it but give them the damn button first so nobody gets left behind.