WCAG Guideline 2.5.4: Motion Actuation Explained
Estimated read time: 6–7 minutes
Guideline 2: Operable
The Operable principle ensures that all users can interact with and control web content, regardless of their abilities. This includes making sure device motion (like shaking or tilting) is never the only way to interact with content.
Guideline 2.5: Input Modalities
Guideline 2.5 focuses on making it easier for users to operate functionality through various input methods, including device motion, touch, and keyboard.
What Is Guideline 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 motion-activated features can be disabled."
Guideline 2.5.4 Motion Actuation is a Level A requirement in the Web Content Accessibility Guidelines (WCAG) .
- Any feature that uses device motion (shake, tilt, rotate) must also be operable by a standard UI control (button, link, etc.).
- Users must be able to disable motion actuation to prevent accidental triggers.
- Exception: motion is essential to the function (e.g., pedometer).
This ensures all users can operate features without relying on device motion, supporting accessibility and usability for everyone.
For more, see BOIA: Tips for Meeting WCAG Success Criterion 2.5.4 Motion Actuation .
Why Does It Matter?
- Inclusivity: Device motion can be difficult or impossible for some users.
- Legal Compliance: Motion Actuation is a Level A requirement in WCAG 2.1 and 2.2.
- Usability: Ensures all users can operate features regardless of device motion.
For more, see W3C’s guidance on motion actuation .
What Needs Motion Actuation Alternatives?
- Shake to undo
- Tilt to scroll
- Any feature using device or user motion
All must have alternative controls and allow motion actuation to be disabled.
How to Make Motion Actuation Accessible
- Provide alternatives to motion actuation
- Allow users to disable motion-activated features
- Document motion feature options
- Test with users with limited mobility
For more, see the W3C's Motion Actuation Techniques .
Common Mistakes to Avoid
- Only supporting motion actuation
- No alternative for device motion
- Not documenting motion feature options
- Not testing with users with limited mobility
Differences Between A, AA, and AAA for Guideline 2.5.4 in WCAG 2.2
- Level A: Requires alternatives to motion actuation and ability to disable motion features. This is the core requirement for 2.5.4 and is mandatory for basic accessibility.
- Level AA: For Guideline 2.5.4, there are no additional requirements beyond Level A in WCAG 2.2. Meeting Level A for this guideline also satisfies Level AA.
- Level AAA: For Guideline 2.5.4, there are no additional requirements beyond Level A in WCAG 2.2. Meeting Level A for this guideline also satisfies Level AAA.
For more, see the W3C’s official documentation for 2.5.4 Motion Actuation .
Quick Checklist
- Alternatives to motion actuation are provided
- Motion-activated features can be disabled
- Motion feature options are documented
- Tested with users with limited mobility
Summary
Guideline 2.5.4 is essential for ensuring all users can operate your site. By providing alternatives to motion actuation, you support users with disabilities, improve usability, and meet legal requirements. Test your site regularly and make motion accessibility a core part of your development process.