Resource guide
2.5.4 Motion Actuation
Functionality triggered by device motion or user gestures must also be operable through standard interface controls, and must be disableable.
By Calling All Minds·Last updated April 2026
Success criterion
Conformance level
Essential baseline — must meet for any compliance.
What it means
Some interfaces use device motion (shaking or tilting the phone) or hand gestures to trigger actions. Users who have their device mounted in a fixed position, or who have tremors that cause unintentional device movement, cannot reliably use these inputs.
Any functionality triggered by motion must: have a UI control alternative, be disableable to prevent accidental triggers from unintentional motion.
In practice
If you use device orientation events (deviceorientation, devicemotion) to trigger actions, provide a button or other UI alternative for the same action.
Allow users to disable motion controls in your application settings.
The exception is when motion is essential, such as a step counter where physical movement is the point of the application.
Common failures
- Shake to refresh with no button alternative
- Tilt to navigate with no UI controls and no way to disable the motion trigger
AXS Audit
AXS Audit checks your site against 2.5.4 and flags issues your team can act on straight away. It covers criteria that automated scanners often miss.