An agency project brief may let customers rank priorities by dragging cards. Before accepting that interface, require an equivalent result through buttons or another single-pointer method, plus keyboard operation. A touch user who cannot drag should still be able to express the same priorities.
Primary evidence and claim boundaries
WCAG 2.2 criterion 2.5.7 requires an alternative to dragging using a single pointer, subject to its exceptions. Keyboard equivalence is a separate requirement. Primary reference · Read 17 October 2026.
Filled acceptance example
Synthetic teaching scenario, not a client case, provider integration test or business result. Scroll the example table on narrow screens.
| Synthetic starting order | Alternative action | Expected order / feedback |
|---|---|---|
| A brand;B enquiry;C catalogue | Click Move C to position 1 | C,A,B; announce new position |
| C,A,B | Keyboard Move B up once | C,B,A; focus remains on B control |
| C,B,A | Move first item up | No change; boundary communicated |
| C,B,A | Submit brief | Stored order exactlyC,B,A |
Practical handover procedure
- Choose explicit controls such as Move up/down or a target-position selector. Labels identify the item and action; do not rely on an unlabeled grip icon.
- Write the state transitions above into the acceptance brief. Check first/last boundaries, repeated moves, cancellation and stable focus after the DOM changes.
- Test drag, pointer-only alternatives and keyboard separately, then inspect the submitted payload and readback. Visual order and saved order must match.
Interpret the outcome
The first move relocatesC, while the second relocatesB without losing its control. A supplier who only makes arrow-key dragging work has not demonstrated the pointer alternative. The final saved sequence is part of acceptance, not just animation polish.
Acceptance decision
All supported input paths must reach the same ordered list, preserve usable focus and submit that exact list. Record the path used for each observation.
Limits and unverified work
Synthetic priority list. This is an interaction specification, not a tested drag-and-drop library or legal compliance opinion. Essential spatial tasks need separate assessment.
Download the filled bilingual acceptance record — Contains these inputs, steps, expectations and limits. This is a teaching record, not an executable integration.