⏸️ Free · no signup · no app install · read-only
Can a visitor stop the things on your store that move by themselves?
Auto-rotating slideshows, scrolling announcement bars and background video all start without being asked. WCAG success criterion 2.2.2 says anything that starts on its own, runs longer than five seconds and sits next to other content needs a way to pause, stop or hide it — and EN 301 549, the accessibility standard EU rules point to, references WCAG. We read the HTML and CSS your server actually sends and list what moves and what can be stopped. We cannot time a page, so we never rule on whether a criterion is met.
Based on publicly available data only. Informational, not legal advice.
What this checks
- <video>, <audio> and YouTube/Vimeo embeds that autoplay with no controls
- Legacy <marquee> tags and CSS scrolling-text tickers
- Carousel libraries on the page (Swiper, Slick, Splide, Flickity, Glide…) and whether their autoplay option is switched on
- Announcement-bar and slideshow section settings — auto_rotate, change_slides_speed
- Any pause / stop control in the markup: aria-label, class name, or a theme autoplay toggle
- A prefers-reduced-motion media query in your inline styles or theme CSS
- CSS animations set to run infinite with no reduced-motion escape hatch
FAQ
Why does it say 'could not tell' for whether my slider runs past 5 seconds?
Because measuring how long something moves needs a rendered page and a clock. We read the HTML as your server sent it and never execute JavaScript, so we can quote the interval you configured but not the total run time. Same reason a pause button that a script injects after load is invisible to us. We would rather say we could not tell than invent a pass.
Does this mean I'm compliant with the European Accessibility Act?
No, and this tool never says a store is or is not compliant. The EAA (Directive (EU) 2019/882) has applied to e-commerce services since 28 June 2025; the European standard EN 301 549 is the accessibility standard EU rules point to, and it references WCAG. This tool checks a handful of motion-related signals visible in served HTML. Two of the three conditions in WCAG 2.2.2 — how long the motion lasts and whether it runs beside other content — cannot be observed by fetching a page, so we report what the markup contains and stop there. Keyboard access, contrast, screen-reader labelling and everything else are outside it. Information, not legal advice.
I have no carousel at all. Why are the carousel and pause checks still 'could not tell'?
If nothing auto-moving shows up in the served HTML, there is nothing for a pause control to control — but a slideshow built entirely in JavaScript would also produce exactly that picture. Both cases look identical from here, so we mark them unknown instead of guessing which one you are. Unknowns are left out of the score rather than counted against you: a check nobody could perform should not be quietly rounded up to a pass.
Want pause controls and reduced-motion handling built in properly?
We are a Shopify studio. The audit is free; the fix is yours to make — or ours to ship.