WCAG 2.2 success criterion 2.5.4, Motion Actuation, is a Level A requirement: motion-triggered functions have a control and can be disabled.
Read the criterion in the W3C Recommendation, WCAG 2.2 (opens in a new tab).
How BearScan checks it
Motion-triggered functions have a control and can be disabled
Checked automatically: clicks through the page. Severity: low. A user whose device is mounted, or who has tremors, cannot shake or tilt it deliberately, and may trigger the function by accident.
An approximation: The page's device motion and orientation handlers (and any Accelerometer or Gyroscope sensor it creates) are recorded as it loads. With none, the criterion does not apply. With some, a series of strong shakes and tilts is dispatched to it and its text, address and dialogs are compared. A page that does not react passes; one that does is reported for review, because whether the same function is on a visible control and whether motion can be switched off is in the application's own settings. Listeners added after a user action, or by a script that waits for a permission prompt, are not found.
How to fix it. Provide an on-screen control for anything triggered by shaking, tilting or moving the device, and a setting to turn motion response off.
All WCAG 2.2 criteria · Next: 2.5.7 Dragging Movements
Questions
Is WCAG 2.5.4 required by the ADA?
The ADA doesn't name a technical standard for businesses, but the Justice Department's 2022 guidance points businesses to WCAG, and its 2024 rule for state and local governments adopted WCAG 2.1 Level AA, which includes 2.5.4.
Can an automated tool check WCAG 2.5.4?
Mostly. BearScan checks it automatically (clicks through the page). A clean result still isn't proof every page passes, only the pages scanned.
How do I fix a WCAG 2.5.4 failure?
Provide an on-screen control for anything triggered by shaking, tilting or moving the device, and a setting to turn motion response off.