Loading Developer Playground

Loading ...

Skip to main content

Success Criterion · WCAG 2.5.7

Dragging Movements

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.

Level AAWCAG 2.2Operable2.5 · Input Modalities
Copy button ready

Goal

Provide alternatives to drag-and-drop or dragging gestures.

What to do

If functionality requires dragging, provide a single-pointer alternative that does not require dragging.

Why it matters

Dragging can be difficult or impossible for users with motor impairments and some assistive technologies.

Success criterion

What WCAG 2.5.7 requires

Summarized directly from the official Understanding document so teams can quote the requirement accurately.

For functionality that uses a dragging movement for operation, an alternative is provided that does not require a dragging movement, unless the dragging movement is essential or the functionality is determined by the user agent and not modified by the author.

Intent

Why WCAG created this requirement

  • Dragging is a common barrier for motor impairments.
  • Provide equivalent operations without requiring continuous dragging.
  • This is a WCAG 2.2 addition (Level AA).

Benefits

Who gains when you pass

  • Users with limited dexterity can perform reordering and moving tasks.
  • Keyboard users can reorder items using buttons or controls.
  • Touch users avoid precision dragging requirements.

Why it matters

User impact when this criterion fails

Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.

Users may be unable to reorder lists or complete drag-based workflows.

Dragging-only interfaces can block access entirely.

Exception guidelines

Use the WCAG 2.5.7 exceptions correctly

Document the rationale for each exception and note which alternative support you provide.

Essential

Dragging is essential to the function.

Requirement

Only when the drag gesture itself is essential to meaning or task.

User agent

Functionality is determined by the user agent and not modified by the author.

Requirement

If UA-determined and unmodified, it may be exempt.

Overview

If your UI includes drag-to-reorder, drag-to-move, or drag-and-drop interactions, provide an alternative method such as buttons (“Move up/down”), menus (“Move to position”), or pick-and-place controls.

  • Provide “grab/move/drop” controls that work by single click/keypress.
  • Ensure alternatives are discoverable and not hidden behind hover-only UI.
  • User-agent provided dragging (not author-modified) may be exempt.

Reference: All summaries and highlights originate from Understanding WCAG 2.5.7 and the W3C quick reference.

Fast facts

Conformance level
Level AA
WCAG version introduced
WCAG 2.2
Principle
Operable
Guideline
2.5 · Input Modalities

Examples

Make success tangible for teams

Share pass/fail snapshots to coach designers, engineers, QA, and content authors.

Reorder list

Pass

Each item has “Move up” and “Move down” buttons plus optional drag handle.

Fail

List can only be reordered by dragging with a mouse.

Kanban board

Pass

Cards can be moved via “Move to column…” menu and keyboard controls.

Fail

Cards can only be moved by drag-and-drop.

Evidence to keep

Document conformance decisions

Capture artifacts for VPATs, procurement reviews, and regression testing.

  • Document accessible reordering pattern used across the app.
  • Capture evidence of drag alternatives on representative components.

Official resources

Deep dives and supporting material

Keep these links handy when writing acceptance criteria or responding to audits.

Implementation checklist

Capture progress and blockers

  • Inventory drag-based features (reorder, drag-and-drop upload, canvas movement).
  • Add non-drag alternatives: move up/down buttons, “Move to…” menus, add/remove controls.
  • Ensure alternatives are keyboard accessible and announced properly.
  • Keep visual affordance for drag handles but do not make them the only method.
  • Document any essential drag-only features with rationale.

Testing ideas

Prove conformance with evidence

  • Identify all drag interactions and verify an alternative exists.
  • Use keyboard-only to complete the same outcome.
  • Test on touch devices and confirm alternatives are usable without dragging.
  • Confirm the alternative truly avoids dragging movement.

Related success criteria

More from Input Modalities (2.5)

View all criteria