Goal
Provide alternatives to device motion for triggering actions.
Success Criterion · WCAG 2.5.4
Motion Actuation
Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when supported motion is essential or not using motions would invalidate the activity.
Level AWCAG 2.1Operable2.5 · Input Modalities
Copy button ready
What to do
If functionality uses device motion (shake, tilt), provide UI controls and allow disabling motion activation.
Why it matters
Some users cannot perform motion gestures or may trigger them accidentally; motion can also cause vestibular issues.
Success criterion
What WCAG 2.5.4 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental activation, except when the motion is used to operate functionality through an accessibility supported interface.
Intent
Why WCAG created this requirement
- Motion-based activation can exclude users with limited mobility.
- Motion gestures can be triggered accidentally.
- Provide standard controls and a way to disable motion response.
Benefits
Who gains when you pass
- Users who cannot shake/tilt can still use the feature.
- Users with tremors avoid accidental activation.
- Users sensitive to motion avoid triggering symptoms.
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 perform motion actions or may trigger them unintentionally.
Motion activation can cause confusion when the UI changes unexpectedly.
Exception guidelines
Use the WCAG 2.5.4 exceptions correctly
Document the rationale for each exception and note which alternative support you provide.
Accessibility supported interface
Motion is used to operate functionality through an accessibility supported interface.
Requirement
Only applies when the interface itself is accessibility supported and motion is part of it.
Overview
If your app uses shaking, tilting, or moving the device to trigger actions, provide a standard UI control to do the same action and allow users to disable motion-triggered activation to prevent accidental triggers.
- Provide a visible button/menu option for the motion-triggered action.
- Offer a setting to disable motion activation (or honor OS-level motion preferences).
- If motion is used via an accessibility-supported interface, exception may apply.
Reference: All summaries and highlights originate from Understanding WCAG 2.5.4 and the W3C quick reference.
Fast facts
- Conformance level
- Level A
- WCAG version introduced
- WCAG 2.1
- 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.
Shake to undo
Pass
Undo is available via a button/menu; shake can be disabled.
Fail
Undo is available only by shaking the device.
Tilt navigation
Pass
Tilt can move content, but arrow buttons/slider also control movement, and tilt can be disabled.
Fail
Tilt is the only way to move and cannot be turned off.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document where motion features exist and how to access alternatives.
- Document the “disable motion” setting and its default behavior.
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 features triggered by device motion (shake to undo, tilt to steer, etc.).
- Add UI controls (button/menu) that perform the same action.
- Add a setting to disable motion-triggered activation.
- Test on devices with motion sensors and in environments where motion occurs (walking).
Testing ideas
Prove conformance with evidence
- Identify motion-triggered features and verify they have UI alternatives.
- Disable motion activation and confirm motion no longer triggers actions.
- Verify UI alternative remains fully functional.
- Test with keyboard and assistive tech for the alternative controls.
Related success criteria