WCAG 2.1 · Level A · Operable
2.5.4 Motion Actuation
Manual verification
How to validate 2.5.4 by hand
Check actions triggered by device motion or gestures and ensure an equivalent interface control is available.
Start with the extension result
Reopen the reported URL and reproduce the same state (for example, after expanding a menu or submitting a form). Use the result’s Highlight action when available, or its affected-element details and CSS selector, to find the reported content. Apply the checks below to that content and its context. If the element or state has changed, rescan and record that difference before deciding whether the finding still applies.
- Identify features activated by shaking, tilting, or moving a device, and determine whether motion is essential.
- Try the same action using a visible control and verify the action can be disabled when motion is not essential.
- Test with the device stationary and with motion permissions denied to confirm the task remains available.
Evidence to record
Record the motion, resulting action, equivalent control, disable option, and any claimed essential exception.
Scope and exceptions
Motion that is essential to the function and motion used by an accessible interface are exceptions. A tilt-based game mechanic may have different scope from a form command.
Record the review outcome
- Confirmed: the recorded evidence shows the requirement is not met in the tested page state, and no applicable exception explains it.
- Not reproduced: the reported issue is absent in the current state. Record the URL, state, and affected element you checked; this does not prove other pages or states conform.
- Needs more review: evidence is incomplete, the content requires human judgment, or an exception is uncertain. Record what remains to be checked instead of treating it as a pass.