For most small-business websites, the right move is to delete the autoplaying hero slider, not fix it. As shipped by most themes, it fails WCAG 2.2.2 — a Level A requirement, the most basic tier — and the University of Notre Dame’s own analytics found that only about 1% of visitors ever click a homepage carousel at all. Fixing one properly is real development work; replacing it with a static hero takes an afternoon and removes the risk entirely.
That’s the short answer. The rest of this post shows the evidence behind it, what WCAG actually requires if you keep your slider, and where the autoplay switch hides on each major platform.
Are carousels bad for accessibility?
Carousels aren’t banned by any standard — but the default slider your theme shipped with almost certainly fails one. The problem isn’t the concept of rotating slides; it’s that stock implementations autoplay with no pause control, hide half their content from keyboards, and say nothing useful to screen readers.
WebAIM, one of the most cited accessibility training organizations, doesn’t mince words: “We discourage the use of carousels.” Its reasoning is that they’re complex to build correctly, introduce significant barriers, and most users ignore them anyway. WebAIM also notes that “for people with cognitive and learning disabilities, animation can make task completion difficult or even impossible.”
The W3C WAI carousels tutorial — the standards body’s own guidance — takes the same position on movement: “Users must be able to pause carousel movement because it can be too fast or distracting, making text hard to read.” The W3C maps carousels to four Level A success criteria: 1.3.1, 2.1.1, 2.2.2, and 4.1.2. Your theme’s slider has to pass all four.
The WCAG rule your autoplay slider is failing right now
WCAG 2.2.2 Pause, Stop, Hide is the specific rule autoplay breaks. Per the W3C’s Understanding document, any moving content that starts automatically, lasts more than five seconds, and appears alongside other content needs “a mechanism for the user to pause, stop, or hide it.”
A typical theme slider rotates every four to seven seconds, forever, with no pause button. That’s a textbook failure — and it’s Level A, meaning it fails even the loosest conformance target. It’s also usually sitting on your homepage, the first page any visitor, customer, or plaintiff’s tester loads.
Autoplay isn’t the only issue. Most stock sliders also fail keyboard operability — arrow controls you can’t reach with Tab, or hidden slides whose links still catch keyboard focus so a user Tabs “into” content they can’t see. You can catch both problems yourself with a 10-minute keyboard test.
Almost nobody clicks your slider anyway
Here’s the part that makes “delete” an easy business decision, not a sacrifice. When Erik Runyon, a web developer at the University of Notre Dame, instrumented the carousel on ND.edu from October 2012 to January 2013, his published data showed that about 1% of visitors clicked any slide — and 84% of those clicks went to slide one, with the remaining four slides splitting roughly 4% each.
| Measurement (ND.edu homepage carousel) | Result |
|---|---|
| Visitors who clicked any slide | ~1% |
| Share of those clicks on slide 1 | 84% |
| Share on each of slides 2–5 | ~4% each |
In plain terms: whatever you put on slides two through five, effectively nobody sees it. Each of those slides is a message your team fought to get “on the homepage” that reaches a rounding error of your traffic.
One honest caveat from the same dataset: a different Notre Dame site with an auto-advancing carousel saw an 8.8% click rate, versus 1.7–2.3% on static ones. Auto-rotation can force more clicks — but usability research explains why that’s not a win. Nielsen Norman Group’s Jakob Nielsen wrote in 2013 that because a carousel moves on its own, “users automatically assume that it might be an advertisement” and ignore it, and that moving targets are especially hard “for users with motor skill issues who have difficulty clicking something before it’s taken away.” His recommendation: carousels “should show a new panel only when users ask for it.”
Does a slider really create lawsuit exposure?
A failing slider is one documented WCAG barrier, and barriers on high-traffic pages are what accessibility complaints are built from. According to UsableNet’s year-end tracking, more than 5,000 digital accessibility lawsuits were filed in U.S. federal and state courts in 2025, and e-commerce sites drew nearly 70% of them.
Nobody can tell you a carousel alone will get you sued, and we won’t pretend otherwise. But plaintiffs’ testers work from the homepage down, and an auto-rotating banner that can’t be paused or operated by keyboard is among the easiest failures to document. It rarely travels alone, either — sites that ship a broken slider usually have the missing alt text and unlabeled buttons to match. The 2025 lawsuit numbers show who’s being targeted; a Level A failure above the fold is not where you want to start that conversation.
If you keep it: the six fixes an accessible image slider needs
An accessible image slider is achievable — the W3C tutorial proves it — but it’s a component rebuild, not a checkbox. Here’s the minimum, in priority order:
- Stop the autoplay, or add a real pause button. The control must be a genuine
buttonelement, reachable early in the Tab order, and the slider must stay paused once paused. Better yet, don’t auto-start at all — that satisfies 2.2.2 by design. - Make every control keyboard-operable. Previous/next arrows and slide-picker dots must work with Tab and Enter, per WCAG 2.1.1.
- Keep focus visible. A keyboard user needs to see which arrow or dot they’re on — that’s WCAG 2.4.7, and theme CSS often strips the outline.
- Keep hidden slides out of the Tab order. Links on off-screen slides shouldn’t receive focus; if focus lands on invisible content, you’ve built a maze.
- Label the controls. “Next slide” and “Go to slide 2,” not two unlabeled arrow icons — that’s name, role, value territory, and it’s what a screen reader reads aloud.
- Respect motion preferences. WebAIM recommends honoring the
prefers-reduced-motionsetting so users who’ve told their device to reduce animation don’t get a spinning banner anyway.
If your slider comes from a theme or plugin, you don’t control most of this code. That’s the real trap: you can toggle autoplay, but you can’t relabel the vendor’s buttons without a developer.
Where to turn off autoplay on your platform
Killing autoplay is the highest-value five minutes available to you today, whatever you decide long-term. Where to look:
- WordPress: Your slider is usually a plugin (Slider Revolution, MetaSlider, Smart Slider) or a theme feature under Customizer settings. Open the slider’s settings and disable the autoplay/auto-rotate option. More theme-level issues in our WordPress accessibility guide.
- Shopify: In the theme editor, select your Slideshow section and look for the auto-rotate toggle in the section settings — untick it. Our Shopify ADA compliance page covers what the theme editor can and can’t fix.
- Squarespace: Gallery and banner slideshow blocks have an autoplay switch in the block or section design settings.
- Wix: Select the slideshow, open its settings panel, and turn autoplay off.
- Webflow: Select the Slider component and clear the autoplay checkbox in the element settings panel.
That single toggle resolves the 2.2.2 failure. The keyboard, focus, and labeling items above still depend on how your theme built the component.
Hero slider alternatives that actually work
The strongest alternative is boring on purpose: one static hero image, one headline, one call to action. The Notre Dame numbers explain why — 84% of carousel clicks went to slide one, so a well-chosen single message loses almost nothing and gains speed, clarity, and compliance.
If you genuinely have multiple messages, stack them. Two or three static sections down the page each get seen by everyone who scrolls, instead of four slides seen by nobody. Rotate the hero content on a schedule (this month’s offer) rather than every five seconds. And if stakeholders push back, the carousel-vs-static debate is a good moment to make the broader case that accessibility fixes tend to boost conversions rather than cost them.
The bottom line
Your theme’s hero slider is a Level A WCAG failure that roughly 1% of visitors use. Delete it and put your best message in a static hero, or budget real developer time to rebuild it to the W3C pattern. Turning off autoplay today is the free move either way.
The slider is also rarely the only thing wrong on the page it lives on. At Curbcut we do manual remediation — fixing components like this in the actual code, not layering a widget over them. Want to know what else your homepage is failing before a tester finds it? Start with a free accessibility scan.