W3C Web Accessibility Initiative 2026 W3C WAI-ARIA Authoring Practices Guide (APG)

Carousel Pattern (W3C WAI-ARIA Authoring Practices Guide)

The W3C’s carousel (slide show or image rotator) pattern: the controls a carousel needs, its keyboard interaction, and the ARIA roles, states, and properties for three styles of carousel.

License: W3C Software and Document License — the page’s copyright footer links to w3.org/copyright/software-license/, which permits copying, modifying, and distributing with attribution. That’s the same basis as Combobox Pattern (W3C WAI-ARIA Authoring Practices Guide), and distinct from the restrictive W3C Document License that covers the WAI tutorials and WCAG.

Key points

  • Definition: a carousel presents a set of items, called slides, by showing a subset of one or more at a time. Previous and next controls “rotate” slides into view, and some carousels rotate automatically from page load.
  • Why rotation control matters: if slides rotate automatically and a screen reader user doesn’t know it, moving to the next element can land them on an element from a new slide with no sign that the context has changed. Slides that aren’t visible must also be hidden properly, not just positioned off-screen.
  • Required controls:
    • previous and next slide buttons;
    • optionally, slide picker controls for choosing a specific slide;
    • for a carousel that rotates automatically, a button for stopping and restarting rotation. Rotation also stops when keyboard focus enters the carousel and doesn’t restart unless the user explicitly asks, and it stops whenever the mouse is over the carousel.
  • Keyboard:
    • Tab and Shift + Tab move through the carousel’s controls in normal page order.
    • Activating the rotation, next, or previous control doesn’t move focus, so people can activate them repeatedly.
    • The rotation control is the first element in the carousel’s tab sequence, before the rotating content.
  • Three styles:
    • Basic has rotation, previous, and next controls only.
    • Tabbed adds slide pickers built with the tabs pattern, a single tab stop.
    • Grouped adds slide pickers as separate buttons, each a tab stop, which makes it the least friendly style for keyboard users.
  • ARIA:
    • The container has role region or group with aria-roledescription="carousel", labeled by a visible heading via aria-labelledby or else by aria-label, without the word “carousel” in the label.
    • Controls are native buttons. The rotation control’s label changes to match its action (“Stop slide rotation” / “Start slide rotation”) rather than using aria-pressed.
    • Each slide is a group with aria-roledescription="slide" and its own name. A number and set size such as “3 of 10” can serve when slides have no unique names.
    • Optionally, the element wrapping the slides is a live region: aria-live="off" while the carousel rotates automatically, "polite" when it doesn’t.
    • In a grouped carousel, the picker button for the current slide has aria-disabled="true", so it stays in the tab sequence.

Cited In

Patterns

Source Links

Created Updated