WCAG 2.5.4 Motion Actuation
Functions triggered by device motion, such as shaking or tilting a phone, must also have a standard control-based alternative, and the motion trigger must be disableable.
Table of contents
What WCAG 2.5.4 Requires
Functions triggered by device motion, such as shaking or tilting a phone, must also have a standard control-based alternative, and the motion trigger must be disableable.
How to Test It by Hand
Check whether any shake-to-undo or tilt-based interaction also has an on-screen button, and whether motion triggers can be turned off.
Common Failures
- A "shake to undo" feature has no equivalent undo button.
Testing WCAG 2.5.4 With AccessBell
This criterion depends on meaning or context, so it needs a person to judge. AccessBell's report lists it for manual review rather than marking it pass or fail automatically, so it is not missed.
Run a free scan to spot issues on your own pages.
Related Criteria in Input Modalities
- 2.5.1 Pointer Gestures (Level A, WCAG 2.1)
- 2.5.2 Pointer Cancellation (Level A, WCAG 2.1)
- 2.5.3 Label in Name (Level A, WCAG 2.1)
- 2.5.5 Target Size (Enhanced) (Level AAA, WCAG 2.1)
- 2.5.6 Concurrent Input Mechanisms (Level AAA, WCAG 2.1)
- 2.5.7 Dragging Movements (Level AA, WCAG 2.2)
- 2.5.8 Target Size (Minimum) (Level AA, WCAG 2.2)
Frequently Asked Questions
What does WCAG 2.5.4 require?
Functions triggered by device motion, such as shaking or tilting a phone, must also have a standard control-based alternative, and the motion trigger must be disableable.
Can AccessBell test WCAG 2.5.4 automatically?
Not fully. This criterion needs a person to judge, so AccessBell's report lists it for manual review rather than marking it pass or fail on its own.
What level is WCAG 2.5.4?
Level A, added in WCAG 2.1.
Sources
- W3C: Understanding 2.5.4 Motion Actuation (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.