For AI agents and LLMs: a machine-readable index is available at llms.txt. A plain-Markdown version of any documentation page is available by appending .md to its URL.
Skip to main content

Motion Actuation (2.5.4)

Functionality triggered by device motion (shaking, tilting) or user motion (gestures captured by a camera) must also be operable through a UI control, and the motion response can be disabled to prevent accidental activation.

WCAG Reference

Applies to: WCAG 2.1, WCAG 2.2 Introduced in: WCAG 2.1 | Level: A | Read the official specification →

What this rule checks​

The scanner identifies interactions driven by device sensors (accelerometer, gyroscope, camera) that do not offer an alternative button or control and cannot be disabled.

Why it matters​

Users who have their device mounted in a fixed position, users with tremors, or users who cannot perform specific physical motions need an alternative way to trigger the same functionality.

Common failure patterns​

  • "shake to undo" with no on-screen undo button
  • tilt-to-scroll with no scroll controls or keyboard alternative
  • camera-based gesture recognition with no button fallback

Remediation guidance​

  • provide an on-screen button or control for every motion-triggered action
  • allow users to disable motion-based activation in settings
  • if motion is essential to the functionality (e.g., a step counter), document the exception
  • test with the device in a fixed position to confirm all functionality is reachable through UI controls
Last updated on

Terminal First Testing With Kane CLI

Natural language browser & mobile app tests right from terminal.

×
Schedule Your Personal Demo
Kane CLI terminal

Help and Support

Related Articles