# Carousel

A carousel displays a sequence of content items within one bounded area, revealing one item or subset at a time through user or automatic movement.

- Type: artifact
- Domain: Experience & interface
- Level: Intermediate
- Last reviewed: 2026-10-06
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/carousel/>)

## What it means

A carousel, also called a slider or image rotator, presents an ordered set of slides in a shared viewport with controls for moving through them. It may show one or several items and may rotate automatically, although user-controlled movement is generally more predictable.

## Why it matters

Carousels can preserve space for a small related set, but later slides are easy to miss and sequential access is inefficient. Teams need evidence that the compact presentation serves users rather than merely resolving internal competition for prominent space.

## When to use it

Use a carousel for a short, coherent sequence where browsing neighboring items has value and no item is essential on its own. Prefer a visible list, grid, or single strong item when comparison, complete discovery, scanning, or reliable access matters.

## How it works

1. Confirm that sequential browsing is suitable and limit the set to a manageable number of items.
2. Provide clearly labeled previous and next controls plus an understandable position indicator.
3. Keep focus, reading order, and announcements aligned with the visible slide.
4. If content advances automatically, provide pause controls and stop movement during interaction or focus.
5. Test touch, keyboard, reduced motion, zoom, long content, loading, and whether users discover later items.

## A practical example

A property page uses a user-controlled carousel for eight photos of the same apartment, with labeled previous and next buttons, a “3 of 8” status, thumbnail access, and a grid alternative. Pricing and availability remain outside the carousel because they must not depend on viewing a particular slide.

## Where it breaks

Hidden slides receive less attention, sequential navigation scales poorly, auto-rotation can interrupt reading, and gesture areas may conflict with page scrolling. A carousel also cannot make unrelated or low-priority content coherent.

## Common mistakes

- Assuming users will see every slide.
- Auto-advancing without a visible way to pause or control movement.
- Using tiny dots as the only position and navigation controls.
- Placing essential information only on a later slide.

## Sources

1. [Carousel \(Slide Show or Image Rotator\) Pattern](<https://www.w3.org/WAI/ARIA/apg/patterns/carousel/>) — W3C Web Accessibility Initiative · Technical guidance
2. [Carousel Usability: Designing an Effective UI for Websites with Content Overload](<https://www.nngroup.com/articles/designing-effective-carousels/>) — Nielsen Norman Group · Professional guidance

## Related topics

- [Infinite Scroll](<https://wiki.soroush.uk/topic/infinite-scroll/>)
- [Pagination](<https://wiki.soroush.uk/topic/pagination/>)
- [Reduced Motion](<https://wiki.soroush.uk/topic/reduced-motion/>)
