WCAG 2.5.4: Motion Actuation
Level AQuick answer: Device motion or shaking cannot be the only way to trigger actions unless users can turn it off and use a standard control instead.
What This Means
On ecommerce sites, Motion Actuation usually shows up in repeating storefront components such as product cards, PDP media, search results, cart drawers, checkout forms, and support content. If the live experience depends on patterns like a mobile app webview reveals discount cards when the phone is shaken. or ar try-on experiences rely on device motion without onscreen buttons., disabled shoppers can lose context or get blocked before purchase.
This criterion matters because D2C teams often fix the homepage but miss reusable app blocks, campaign pages, and mobile-specific UI. The practical standard is simple: build the same outcome for keyboard users, screen-reader users, low-vision users, and anyone relying on captions, labels, structure, or predictable behavior.
For Shopify, WooCommerce, and custom storefronts, the fastest remediation path is usually template-level work. Fix the repeated component once, then retest every place it appears across browse, buy, and post-purchase journeys.
Common Violations on Ecommerce Sites
- A mobile app webview reveals discount cards when the phone is shaken.
- AR try-on experiences rely on device motion without onscreen buttons.
- Product rotators advance when the device tilts but have no manual controls.
- Motion-triggered easter eggs interfere with users who cannot hold devices steady.
How to Fix It
Start with the live customer journey, not isolated components in Storybook or Figma. Audit the problem on category pages, product detail pages, quick views, cart, checkout, account, and help templates.
- Provide onscreen buttons for any action available through motion.
- Let users disable motion activation in settings or session controls.
- Do not rely on device sensors for core commerce steps like browsing or applying offers.
- Respect reduced-motion preferences when enabling motion features.
On Shopify, fix the theme section or app block that repeats the defect. On WooCommerce and WordPress, update the template override or plugin output. In custom React or headless storefronts, move the fix into shared components so merchandisers cannot reintroduce the issue with every campaign.
Code Example
<!-- Before -->
window.addEventListener('devicemotion', revealOffer);
<!-- After -->
<button type="button" onclick="revealOffer()">Reveal offer</button>FAQ
What is WCAG 2.5.4?
Device motion or shaking cannot be the only way to trigger actions unless users can turn it off and use a standard control instead.
How does WCAG 2.5.4 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with a mobile app webview reveals discount cards when the phone is shaken. and ar try-on experiences rely on device motion without onscreen buttons. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 2.5.4 violations?
Start by auditing the live storefront, then Provide onscreen buttons for any action available through motion.; Let users disable motion activation in settings or session controls.; Do not rely on device sensors for core commerce steps like browsing or applying offers.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 2.5.4 → Free ADA Compliance Scan