AgentKit

Posted on May 8 • Originally published at blog.a11yfix.dev

Image Carousels and ADA Lawsuits: Why Auto-Rotating Sliders Keep Getting Small Businesses Sued

#a11y #webdev

If you own a small business website built between 2014 and 2022, there is a very good chance your homepage starts with a giant rotating image carousel. Three to five photos, each with a headline and a button, fading or sliding from one to the next every four seconds. Your designer probably loved it. Your conversion rate consultant probably hated it. And in 2026, the plaintiff's lawyer who just sent you a demand letter probably mentioned it by name.

Image carousels are one of the most-cited widgets in ADA Title III filings against small businesses, second only to inaccessible PDFs. They are also one of the most common sources of European Accessibility Act complaints reaching national market surveillance authorities. The reason is not that carousels are impossible to build accessibly — they are, with effort — but that almost nobody actually does. The default carousel that ships with your theme is, in plain language, broken for several categories of disabled users.

This guide explains exactly why, what a plaintiff's lawyer typically argues, and what your three real options are if you find one on your site. It is written for non-developers. You do not need to know any code to make a decision today.

What a carousel does to a screen reader user

When a carousel auto-rotates, a screen reader user has no way to know that the visible content has changed. Most stock carousels do not announce slide changes through an ARIA live region. So a user who has just landed on your homepage hears the alt text of slide one, starts reading the headline, and four seconds later the visible content has switched to slide three — but the screen reader is still reading slide one. The user reaches the call-to-action button, presses Enter, and lands on a page that has nothing to do with what they thought they were clicking.

If the carousel does have a live region, it is often misconfigured to announce the entire slide every time, so the user hears headlines from three different slides while trying to read a paragraph elsewhere on the page. The carousel becomes the loudest thing in the room, and the user cannot escape it without leaving the site.

Either failure mode is a violation of WCAG Success Criterion 4.1.3 (Status Messages) and, depending on configuration, 1.3.1 (Info and Relationships) and 2.2.2 (Pause, Stop, Hide).

What a carousel does to a keyboard-only user

A keyboard-only user — including most motor-impaired users, many older users with tremor or arthritis, and most screen reader users — navigates a page with the Tab key. A well-built carousel exposes its previous, next, and pause controls in a logical tab order with visible focus rings, so a keyboard user can move into the carousel, stop it, and step through slides at their own pace.

Almost no stock carousel does this. The default behaviour for most theme carousels in 2026 is one of the following:

The previous and next arrows are decorative div elements with click handlers but no keyboard handlers, so the keyboard user cannot reach them at all.
The slide indicators (the dots beneath the carousel) are reachable by Tab but have no visible focus indicator, so the user cannot tell where they are.
There is no pause button, full stop. WCAG 2.2.2 requires that any moving content lasting longer than five seconds have a mechanism to pause, stop, or hide it. A carousel that auto-advances every four seconds and never stops fails this criterion outright.
Tabbing into the carousel moves focus into a hidden slide that is not visible on the screen, so the user's focus disappears and they cannot tell where they are.

Each of these is a separate WCAG failure under 2.1.1 (Keyboard), 2.4.7 (Focus Visible), or 2.2.2.

What a carousel does to a user with a vestibular disorder

For users with vestibular disorders, motion sensitivity, or migraine triggers, an auto-rotating carousel is not just an annoyance — it is a physical symptom trigger. The horizontal movement, particularly fast slide transitions or parallax effects, can induce nausea, dizziness, and full migraine within seconds.

WCAG 2.3.3 (Animation from Interactions) and the related prefers-reduced-motion media query require sites to respect a user's operating-system preference for reduced motion. A carousel that auto-advances regardless of that preference is a Level AAA failure today and, given the direction of WCAG 3.0 drafts, very likely a Level AA failure within the next standard cycle.

What a carousel does to a user with low vision

Users with low vision who zoom their browser to 200 or 400 percent need content to reflow without horizontal scrolling, per WCAG 1.4.10 (Reflow). Most carousels are built with fixed pixel widths or absolute positioning that does not reflow. At 320 pixels of effective viewport width — the standard reflow target — the carousel often stops working entirely, with text running off the side of the screen and buttons becoming unreachable.

Color contrast is the other problem. Most carousels overlay headline text on a photo. The photo's brightness varies across the image, so a single text colour cannot meet the 4.5:1 contrast ratio required by WCAG 1.4.3 across the entire span of the headline. The accessible solution is a solid or near-solid overlay between the photo and the text, but that often gets removed during a redesign because it does not look as polished.

What plaintiffs actually claim

Demand letters and complaints filed in 2024-2026 against small businesses with carousels typically allege some combination of the following:

The carousel auto-advances and provides no pause, stop, or hide control, citing WCAG 2.2.2.
The slide change is not announced to screen reader users, citing WCAG 4.1.3.
The previous, next, and indicator controls are not reachable by keyboard or have no visible focus indicator, citing WCAG 2.1.1 and 2.4.7.
The headline text fails colour contrast against the underlying photograph, citing WCAG 1.4.3.
The carousel does not respect the user's reduced-motion preference, citing WCAG 2.3.3.

In most cases, the plaintiff's expert simply opens the homepage with a screen reader and a keyboard, and screenshots or records the failures. The carousel is often the easiest thing to demonstrate, which is why it shows up so frequently as the lead exhibit.

Your three options

If you have just discovered a carousel on your homepage and your lawyer is asking what to do, you have three realistic choices.

Option 1: Remove the carousel entirely

This is the cheapest, fastest, and most defensible option, and it is what most accessibility consultants quietly recommend. Replace the carousel with a single hero image and a single call-to-action. The conversion data is on your side: most studies of carousel performance show that only the first slide gets meaningful clicks, with each subsequent slide capturing under two percent of attention. You are not giving up much.

This option resolves every WCAG failure listed above in a single change. From a liability standpoint, it eliminates the most-cited element in your demand letter. From a content standpoint, it forces you to decide what your homepage's single most important message is, which is usually a healthy exercise.

Option 2: Stop the auto-rotation

If your designer or your boss insists on multiple slides, stop the carousel from auto-advancing. The user can then click previous and next to move through slides at their own pace, and the most severe failures (2.2.2 and 2.3.3) go away. You still need to fix keyboard focus, screen reader announcements, contrast, and reflow, but you have removed the failures that are typically cited first.

This is a middle-ground option. It is cheaper than rebuilding the carousel from scratch but more expensive than removing it, and it leaves several WCAG criteria still requiring work.

Option 3: Rebuild the carousel correctly

A correctly built carousel is possible. It uses an accessible pattern such as the ARIA Authoring Practices Guide carousel pattern, with proper pause and play buttons, keyboard-reachable slide controls, an ARIA live region for slide change announcements, visible focus indicators, contrast-checked text overlays, reflow at 320 pixels, and a prefers-reduced-motion check that disables the rotation for users who request it.

This is real engineering work. Expect to spend anywhere from several hundred to several thousand dollars depending on your platform and the complexity of your carousel. It is the right choice if the carousel is genuinely critical to your conversion strategy and you have the budget. For most small businesses, options one or two are more proportionate.

What to actually do this week

If you have a demand letter in hand, talk to your lawyer first. The list above is not legal advice.

If you do not have a demand letter and you are reading this proactively — which is the right time to act — open your homepage on a desktop browser and try three things. Press Tab from the URL bar and count how many tab stops it takes to escape the carousel. Open your operating system's accessibility settings, turn on the reduced-motion preference, and reload the page. Then turn on your built-in screen reader (VoiceOver on Mac, Narrator on Windows) and listen to what happens when the slides change.

If any of those tests fails or surprises you, you have a finding. Document what you saw, decide which of the three options fits your budget and your business, and act on it. Carousel issues do not get better on their own, and the cost of a single ADA demand letter — typically several thousand dollars in legal fees plus the cost of remediation — is almost always higher than the cost of just removing the widget.

DEV Community