2.5.4 Motion Actuation (Level A) — WCAG 2.1
WCAG 2.1 Success Criterion 2.5.4 Motion Actuation (Level A): what it requires, a common e-commerce accessibility failure, and how to fix it.
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
WCAG 2.1 guidelines hub → Operable → 2.5.4 Motion Actuation
2.5.4 Motion Actuation (Level A)
What it requires: Functionality triggered by device motion (shake-to-undo, tilt controls) also has a standard UI control alternative, and can be disabled to prevent accidental triggering.
Common failure: A “shake to see a random product” feature has no on-screen button equivalent, excluding users whose device is mounted or who can’t perform the shake motion.
Fix it: Always pair motion-triggered features with a standard button/control that achieves the same result, and provide a way to turn off motion actuation if accidental triggering is likely.
In 2.5 Input Modalities: ← 2.5.3 Label in Name · 2.5.5 Target Size →
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
This page was drafted with AI assistance and reviewed by a person for accuracy before publication.