Accessible Carousel: Pause, Controls and Focus
Also called: Accessible slider, Accessible slideshow, Image rotator
Definition
An accessible carousel is a slider or image rotator that every visitor can control: auto-rotation can be paused or stopped, it stops while the mouse or keyboard focus is on it, previous, next and slide controls have names, and screen readers know which slide is shown. Auto-rotation falls under WCAG 2.2.2 Pause, Stop, Hide at Level A.
An accessible carousel is a slider that visitors control, not one that controls them. Hero sliders, testimonial rotators and product carousels often change slides every few seconds with no way to stop them, hide their arrows from the keyboard and leave screen reader users guessing what is on screen. For people who read slowly or are easily distracted, a slide that moves on before they finish is a real barrier.
What it means
A carousel that advances by itself is auto-updating content in the sense of WCAG 2.2.2 Pause, Stop, Hide (Level A). W3C lists "auto-advancing presentations" as an example. The rules:
| Content | When it applies | What users need |
|---|---|---|
| Moving, blinking or scrolling | Starts automatically, lasts more than five seconds, shown next to other content | A way to pause, stop or hide it |
| Auto-updating (e.g. auto-advancing slides) | Starts automatically, shown next to other content – no five-second exception | A way to pause, stop, hide it or control how often it updates |
Content that starts when a user hovers or scrolls it into view also counts as starting automatically. The full criterion is explained in pause, stop, hide.
The W3C carousels tutorial and the WAI-ARIA Authoring Practices add what a good carousel does:
- one button that starts and stops rotation, with a label that changes with its action
- rotation stops when the mouse hovers over the carousel or keyboard focus enters it
- buttons for the previous and next slide, optionally a control to pick a slide
- the container has
aria-roledescription="carousel", each sliderole="group"witharia-roledescription="slide"and a label such as "3 of 6"
Examples
<section aria-roledescription="carousel" aria-label="Customer stories">
<button type="button" class="rotation">Stop slide rotation</button>
<button type="button" aria-label="Previous slide">‹</button>
<button type="button" aria-label="Next slide">›</button>
<div aria-live="off">
<div role="group" aria-roledescription="slide" aria-label="1 of 3">
<img src="story-anna.jpg" alt="Anna in her bakery in Graz">
<p>"Our online orders doubled."</p>
</div>
<!-- slides 2 and 3 -->
</div>
</section>The rotation button is the first control, so keyboard users reach it right away. Its label switches to "Start slide rotation" when stopped. The arrows are icon buttons with an aria-label. The slide wrapper uses aria-live="off" while rotating and "polite" when stopped – an ARIA live region that announces manual changes without interrupting users all the time. Every image needs alt text.
Offer a visible pause or stop button, stop rotation on hover and focus, give arrows and dots clear names, let users reach every control by keyboard, and keep important content readable without waiting.
Auto-rotate with no way to stop, restart rotation by itself after the user stopped it, use unlabeled arrows or dots, hide slide content from screen readers while it is visible, or put essential information only on later slides.
How to check an accessible carousel
Questions
What makes a carousel accessible?
Visitors can pause or stop auto-rotation, rotation stops on hover and keyboard focus, all controls work by keyboard and have names, slides have labels, and images have alt text. That covers WCAG 2.2.2, 2.1.1, 1.1.1 and 4.1.2.
Does every carousel need a pause button?
A carousel that advances by itself needs a way to pause, stop or hide it under WCAG 2.2.2 – there is no five-second exception for auto-updating content. A carousel that only moves when users click needs no pause button.
How fast should a slider rotate?
WCAG does not set a slide duration, and neither does the W3C carousels tutorial. What it requires is control: users must be able to stop rotation, and it should stop while they hover over it or focus it.
Is pausing on hover enough?
No. Hover does not help keyboard users or people using a screen reader without moving the mouse. W3C recommends a dedicated start and stop button in addition to pausing on hover and focus.
Which WCAG criteria apply to carousels?
Mainly 2.2.2 Pause, Stop, Hide, 2.1.1 Keyboard, 4.1.2 Name, Role, Value for the controls and 1.1.1 for slide images – all Level A in WCAG 2.2.
Related terms
Pause, Stop, Hide: Control Moving Content
Pause, Stop, Hide is WCAG success criterion 2.2.2. Moving, blinking or scrolling content that starts automatically, lasts more than five seconds and appears alongside other content needs a way to pause, stop or hide it; auto-updating content needs a way to pause, stop or control how often it updates.
Read definition: Pause, Stop, Hide: Control Moving ContentKeyboard Navigation: WCAG 2.1.1 Explained
Keyboard navigation means that every function of a website can be reached and operated with a keyboard alone – usually with Tab, Shift+Tab, Enter, Space and the arrow keys. WCAG 2.1.1 requires it at Level A.
Read definition: Keyboard Navigation: WCAG 2.1.1 ExplainedIcon Button: How to Give It an Accessible Name
An icon button is a button that shows only a symbol – a magnifier, a cross, three lines – and no visible text. To be accessible it needs an accessible name in code that tells assistive technology what the button does.
Read definition: Icon Button: How to Give It an Accessible NameARIA Live Regions: Announce Status Messages
An ARIA live region is a part of the page marked with aria-live or a live role such as status or alert. When its content changes, screen readers announce the new text without the user having to move focus to it.
Read definition: ARIA Live Regions: Announce Status Messages