Nearly every small-business home page has one: a hero carousel that slides to the next photo every four seconds, forever, whether you asked it to or not. It is the default in most themes, it ships turned on, and almost nobody thinks of it as an accessibility problem. It is one. Motion that starts by itself and never stops is a genuine barrier for people with attention-related disabilities, who cannot keep their eyes on the paragraph next to a thing that keeps moving; for people with vestibular disorders, for whom large sliding motion can provoke nausea and dizziness; and for anyone using a screen magnifier, where a slide change yanks the content out from under a zoomed viewport. WCAG has had a rule about this since 2008. It is Level A, the most basic tier there is, and it sits inside the standard Ontario actually enforces. The fix is usually one button.
Key facts
- WCAG (Web Content Accessibility Guidelines) Success Criterion 2.2.2 Pause, Stop, Hide is Level A and has been in the standard since WCAG 2.0 - the most fundamental conformance tier (W3C).
- The rule bites when moving, blinking, or scrolling information does all three: it starts automatically, it lasts more than 5 seconds, and it is presented in parallel with other content. Then a mechanism to pause, stop, or hide it is required, unless the motion is essential to the activity (W3C).
- 1.4.2 Audio Control is Level A: audio that plays automatically for more than 3 seconds needs a way to pause or stop it, or to control its volume independently of the system volume (W3C).
- 2.3.1 Three Flashes or Below Threshold is Level A: pages must not contain anything that flashes more than three times in any one second period (W3C).
- Ontario's IASR (Integrated Accessibility Standards Regulation, O. Reg. 191/11) s.14 requires organizations with 50 or more employees to meet WCAG 2.0 Level AA on public websites, and Level AA includes every Level A criterion (ontario.ca).
- The next ACR (Accessibility Compliance Report) for organizations with 20 or more employees is due December 31, 2026 (ontario.ca).
What does "Pause, Stop, Hide" actually require?
Less than people assume. 2.2.2 does not ban motion, animation, or carousels. It does not say your slider must be gone. It says that when content moves on its own, for a meaningful stretch of time, next to content a person is trying to read, that person must be given a way to make it stop.
Read the three conditions carefully, because a great deal turns on the word and. The motion has to start automatically, meaning the user did not trigger it. It has to last more than five seconds - W3C chose that threshold because five seconds is long enough to catch attention but short enough that a user can simply wait out a brief animation. And it has to run in parallel with other content, meaning there is something else on the page the user might reasonably be trying to read while it moves. A loading spinner that resolves in two seconds fails none of these. A splash animation that plays alone and ends does not either. A hero carousel that cycles indefinitely beside your headline, your value proposition, and your call to action meets all three, every time.
The escape hatch is narrow. The criterion exempts motion that is essential, which W3C defines as content that, if removed, would fundamentally change the information or functionality. A progress bar during a file upload is essential; it is the information. A rotating photo of your storefront is not. Marketing preference is not essentiality, and this is where most sites quietly fail: they read "unless essential" as "unless we want it," which is not what the word means.
There is a second half of the criterion that catches a different pattern: auto-updating information, such as a live feed, a ticker, or a price that refreshes on a timer. For auto-updating content there is no five-second grace period. If it starts automatically and runs beside other content, the user needs a way to pause it, hide it, or control how often it updates.
Why is the auto-rotating hero carousel the classic Ontario failure?
Because it is the one piece of motion that ships enabled by default in nearly every commercial theme, and because the people who install it are rarely the people who read WCAG. A Shopify or WordPress theme offers a slider, the rotation interval is preset, autoplay is checked, and there is no pause control anywhere in the settings panel. Nobody added a barrier on purpose. It arrived with the template.
It compounds, too. The same carousel that fails 2.2.2 on motion frequently fails on other counts at once: the slide arrows are unlabelled buttons a screen reader announces as "button, button," the slides rotate away while a keyboard user is still tabbing through the links inside one of them, and the whole component depends on a drag gesture with no tap alternative. That last one is 2.5.7 Dragging Movements, which we cover in the mobile and touch guide; the keyboard trap is its own category of failure. One component, several distinct criteria, all of them Level A or AA.
Worth being precise about what the law here is. The IASR points at WCAG 2.0 Level AA, and 2.2.2 is Level A, so it is inside the target by definition. This is the gap between what Ontario enforces and what current best practice looks like: the enforceable floor is the older version, and this criterion is old enough that the distinction does not rescue anyone. It has been Level A for the entire life of the standard.
And because motion lives in your theme's own JavaScript, a bolt-on widget does not fix it. An overlay script cannot reliably reach inside a third-party slider and give it a pause button that survives the next theme update, which is the general reason an overlay is not remediation.
What about autoplay video, audio, and flashing content?
Three neighbouring rules, each Level A, each easy to trip.
Autoplay audio (1.4.2). If sound plays automatically for more than three seconds, you owe the user a pause or stop control, or independent volume control. Three seconds, not five. The reason this criterion exists is specific and often missed: a screen-reader user cannot simply reach for the volume knob, because the screen reader's own speech is coming through the same output. Background music that starts on page load talks over the software they navigate with. If your video hero autoplays with sound, that is the failure; muted autoplay does not trigger 1.4.2, though the video's motion may still put you inside 2.2.2. Captions and audio description are a separate obligation on the media itself.
Flashing (2.3.1). Nothing on the page may flash more than three times in any one-second period. This one is not about annoyance. It exists to protect people with photosensitive epilepsy, for whom flashing in the wrong frequency band can trigger a seizure. It is rare on business sites and serious when present, most often arriving through an embedded ad, a video, or a decorative animation nobody screened.
Interaction-triggered animation. Parallax, motion on scroll, and elements that fly in as you move down the page fall under 2.3.3 Animation from Interactions, which is Level AAA - above both the enforceable Ontario line and the AA target. It is not required. It is still worth doing, and it is nearly free: honouring the prefers-reduced-motion media query lets a visitor who has already asked their operating system to reduce motion get a calmer page from you automatically, with no setting to find on your site. Treat it as best practice rather than compliance, and do not let anyone sell it to you as a legal requirement.
How do you check it, and what's the risk if you don't?
You can audit this yourself, in about five minutes, with no tools:
- Load your home page and do nothing. Start a timer. Anything still moving, sliding, blinking, or refreshing after five seconds, next to text, is in scope. Now look for a pause control. If there is not one, that is a 2.2.2 failure.
- Listen. Does anything make sound on its own? If it runs past three seconds without an obvious pause or independent volume control, that is 1.4.2.
- Check the pause button works for everyone. A control that only appears on mouse hover does not help a keyboard user. Tab to it. It should be reachable, clearly labelled ("Pause slideshow", not an unlabelled icon), and it should actually stop the rotation rather than restart it on the next slide.
- Check your interior templates. Sliders breed on home pages but also hide in testimonial sections, logo strips, and product galleries.
An automated scanner will not do this for you. A scanner can detect that an element has a CSS animation attached; it cannot judge whether that motion runs longer than five seconds, whether it sits beside content someone is reading, whether it is essential, or whether the button you added actually stops it. This is squarely one of the judgment calls that makes a scan not an audit, and it is the same reason a clean automated report is thin evidence of anything.
As for stakes, the honest picture is the one that applies to every access barrier. In Ontario the AODA (Accessibility for Ontarians with Disabilities Act) has no private right of action, so nobody sues you under it directly. The live route for an individual is the HRTO (Human Rights Tribunal of Ontario), which hears complaints under the Ontario Human Rights Code, and that is how a single complaint actually unfolds. If you sell into the United States, moving content and autoplay media are routine allegations in ADA (Americans with Disabilities Act) web litigation. The durable answer is not a disclaimer or a widget. It is documented remediation: a dated record of what you found and what you fixed, which is what an honest ACR should reflect by December 31, 2026.
The good news, unusually, is that this is one of the cheapest categories of failure to close. A pause control on a carousel is a small, contained change. It is on the list because it is everywhere, not because it is hard.
See whether your site has unstoppable motion and check for other accessibility issues, free Vayle Report, about 30 seconds: vayle.art. It detects overlay widgets, surfaces real WCAG failures, and tells you exactly what legally applies to your organization in Ontario. No obligation.
Vayle is a remote-first accessibility-engineering studio serving Ontario. General information, not legal advice.