WCAG 2.5.4 — Motion Actuation — device motion with no alternative

Who Is Affected

Users with mobility impairments who cannot tilt, shake, or rotate their devices, users who have their devices mounted or in fixed positions, users of assistive technologies, and anyone using a device with broken or disabled motion sensors.

What This Means

Some websites include features that respond to device motion — like shaking a phone to undo an action, tilting to navigate through content, or rotating to trigger a function. While these can be convenient shortcuts, they become barriers when they're the only way to access certain functionality.

WCAG requires that any feature triggered by device motion must also have an alternative method of activation, such as a button or menu option. Users must also be able to disable motion actuation entirely to prevent accidental triggering.

Common violations include shake-to-refresh features, tilt-based navigation, motion-controlled games or interactive elements, and device orientation changes that trigger functionality without alternatives.

Fix: CMS / Theme

Review your theme and any installed plugins for motion-based interactions:

1. Audit motion features: Check your site on a mobile device and look for:

   • Shake gestures (refresh, undo, reset)
   • Tilt-based navigation or scrolling
   • Device rotation triggers beyond responsive layout
   • Motion-controlled sliders or carousels

2. Add alternative controls: For each motion feature found:

   • Provide a visible button or link that performs the same action
   • Ensure the alternative is clearly labeled and easily discoverable
   • Test that both methods work identically

3. Implement disable option: Add a user preference to turn off motion actuation: In WordPress, check accessibility settings in your theme customizer or add a toggle in user preferences. In Joomla, look for motion settings in your template parameters or consider a user preference module.

4. Review JavaScript libraries: Common culprits include:

   • Shake.js implementations
   • Device orientation event listeners
   • Touch gesture libraries with motion components

Fix: Content Editor

If motion features are embedded in specific pages:

1. Identify motion-triggered content: Look for:

   • Interactive elements that mention shaking or tilting
   • Embedded widgets or iframes with motion controls
   • Custom JavaScript that uses device motion events

2. Add alternative text controls: Next to any motion-triggered element, add:

   • Clear instructions for the alternative method
   • Visible buttons or links for the same functionality
   • Labels that explain what the motion gesture does

3. Update instructions: If your content includes directions like "shake to continue" or "tilt to view more":

   • Add alternative instructions: "shake device or tap the refresh button"
   • Ensure both methods are equally prominent in the instructions

Standard Reference

WCAG 2.1 Success Criterion 2.5.4 — Motion Actuation, Level A

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:

• The motion is used to operate functionality through an accessibility supported interface; or

• The motion is essential for the function and doing so would invalidate the activity.

• W3C Understanding SC 2.5.4

• WCAG Technique G213 — Provide conventional controls and application setting for motion activated input

• WCAG Failure F106 — Motion actuation without alternative