Skip to main content
متصفحك قديم جدًا لعرض هذا الموقع بشكل صحيح. يُرجى التحديث إلى أحدث إصدار من Chrome أو Edge أو Firefox أو Safari.
Back to WCAG Database
Level AWCAG 2.1

2.5.4 Motion Actuation

Functionality that can be operated by device motion or user motion can also be operated by conventional user interface components, and motion actuation can be disabled to prevent accidental triggering.

Last reviewed: September 9, 2026

Understanding 2.5.4

Features like shake-to-undo, tilt-to-scroll, or motion-based games assume a user can physically move or shake their device, which excludes people who have their device mounted (wheelchair tray, tripod), have limited or no motion in their arms, or have involuntary movements that could trigger the action unintentionally. This criterion ensures a conventional control (a button, menu item) provides the same functionality, and that motion actuation can be turned off for users at risk of accidental activation.

How to Meet It

For every motion-triggered feature, provide an equivalent on-screen control (e.g., an explicit "Undo" button in addition to shake-to-undo). Provide a setting to disable motion actuation entirely for users whose devices are mounted or who may move involuntarily. Motion actuation is exempt from these requirements only when the motion is essential to the function (e.g., a pedometer or a VR headset tracking head movement) or when the motion is used to operate accessibility features of the platform itself.

Frequently Asked Questions

What are common examples of motion actuation on the web?

Shake-to-undo in a mobile web app, tilt-to-pan in a photo viewer, or games that use the device's accelerometer/gyroscope through the DeviceMotion/DeviceOrientation APIs.

Why does this also require a way to disable motion, not just an alternative control?

Someone with tremors or spasms whose device sits in their lap could trigger the motion gesture involuntarily and unexpectedly perform an action they didn't intend. Letting them turn the feature off prevents that, independent of whether an alternative button also exists.

Related Success Criteria

2.5.1 Pointer Gestures2.5.2 Pointer Cancellation2.5.3 Label in Name2.5.5 Target Size (Enhanced)

Quick Facts

  • Criterion2.5.4
  • LevelA
  • IntroducedWCAG 2.1

Automate Compliance

AccessiSight automatically scans and identifies 2.5.4 issues in your codebase.

Try Scanner Free