Carousel: Rotating Slides That Show Related Items One at a Time
A carousel shows related items one or a few at a time. Learn its parts, its options, when to skip it, and the rules that keep it usable for everyone.
In short
A carousel shows related items one or a few at a time, and a design system sets its parts, options and rules, including when to skip it, to keep it usable.
15 min readFree
What You Will Learn
This lesson teaches the carousel as a design system component. A design system is a shared set of parts and rules that a product team reuses across screens. You will learn how a carousel is built, which options and states the system should expose, when to avoid one, and how to make it work with a keyboard, a screen reader, and a touch screen.
Key words
- Carousel
- A strip of related items shown one at a time, or a few at a time, that users move through.
- Slide
- One item inside a carousel, such as one photo or one banner.
- Pagination
- The row of dots or numbers that shows how many slides exist and which one is showing.
- Autoplay
- When the carousel moves to the next slide by itself, on a timer.
- Peek
- A small slice of the next or previous slide at the edge, as a hint that more content exists.
- Loop
- When the last slide leads back to the first one.
- Focus
- The visible marker that shows which control a keyboard user is currently on.
- Screen reader
- Software that reads the page out loud for people who cannot see it well.
- Live region
- An area of the page that tells screen reader users about a change, without moving their place on the page.
- Reduced motion
- A device setting a person turns on to ask apps and sites to reduce movement and animation.
- Target size
- How big a button or tap area is, so a finger or a mouse pointer can hit it easily.
What is a carousel?
A carousel is a horizontal strip that holds a set of related items. It shows one item, or a small group, and lets the user reach the others with arrow buttons, dot buttons, a swipe on a touch screen, or automatic movement. The W3C, the group that writes many web accessibility standards, describes it the same basic way: a collection of items shown one at a time.
In a design system, the team defines the carousel once, with rules for its structure, its behavior, and the situations where it should be used. Product teams then reuse that shared definition instead of building their own. That shared definition is the main value of a design system component.
What is the anatomy of a carousel?
Every carousel is built from the same basic parts. A design system gives each part a name, so designers and builders use the same words.
Slides
The items in the strip. A slide can hold text, an image, or a video. The Sainsbury's design system asks that every slide take the height of the tallest slide, so the frame does not change size as a user moves through it.
Previous and next controls
Arrow buttons that move the strip one slide back or forward. They sit close to the carousel and need clear names such as Previous slide and Next slide.
Pagination indicators
The row of dots or numbers that shows how many slides there are and which one is showing. The current item should look clearly different. The Sainsbury's design system caps the number of visible dots at five.
Play and pause control
A button that starts or stops the motion. It appears only when autoplay is on, and a user can stop the movement at any time.
Each part needs its own documented look, spacing rules, and states, such as a current dot and a dot that is not current. Some parts can be switched on or off. The Sainsbury's banner carousel, for example, can use default arrows or custom controls placed elsewhere on the page. The system should say which combinations are allowed.
Which options change behavior?
Peek
A small slice of the neighboring slide shows at the edge. It hints that more content exists, which helps on touch screens where people need a reason to swipe.
Looping
The last slide leads back to the first. Looping hides where the list ends, so use it only when the content has no true start or finish.
Autoplay
The carousel moves forward on a timer. This is the riskiest option, and it has its own section below.
Visible slide count
The strip can show one slide or several. Several slides suit small items to browse. One large slide suits a hero image or a single feature.
Which props and states should the system expose?
A prop is a setting a team chooses when it places the component on a page. A state is the condition the component is in at a given moment. A good system lists both, so teams do not invent their own version of the same carousel.
Props to list
Autoplay on or off, looping on or off, peek on or off, pagination style (dots, numbers, thumbnails, or none), arrows shown or hidden, the number of visible slides, and the time each slide stays on screen.
States to show
Playing, paused, focused by keyboard, hovered by a mouse, at the first slide, at the last slide, and being dragged by a finger. Each state needs a visual design, so a user can always tell what the carousel is doing.
Defaults to decide
The Sainsbury's design system says that if autoplay is enabled, it is turned on by default, but many guides argue autoplay should be off unless there is a strong reason. Write each default and its reason in the rules.
Tip
When a state has no visual design, teams will guess. Write a short description and a picture for every state, including paused, focused, and the state where a control is unavailable.
When should you use a carousel and when not?
A carousel suits content that people browse, where each item has about the same importance and the space on the page is limited. A set of photos or a row of similar offers fits well. The Sainsbury's design system draws this line clearly. It recommends a banner carousel for attention-grabbing banners, and a separate carousel for sequences of similar items, such as product cards, that people browse or compare.
Good fit
Browsing equal-weight items: product photos, gallery images, or similar cards where any one item is as useful as the next.
Poor fit
The most important offers, warnings, required steps, or any action such as a checkout button. These should not sit in a strip that a user must move through.
Better choice
If the content must be seen, place it in the normal page flow, as a simple list or grid where every item is visible without a click.
Why Carousels Get a Bad Reputation
He also says they often show low click-through rates, meaning few visitors click them, and that people often scroll past them. Small progress dots with tiny tap areas and faint labels make the problem worse.
The lesson is not that carousels are always wrong. A carousel hides content by design, so every item in it must earn a place where it can be missed.
Autoplay: Use It Rarely and With Strict Rules
Autoplay is the setting that most often makes a carousel annoying. If a team must use it, the rules below apply.
The W3C guidance says users must be able to pause movement, because movement can be distracting and can make text hard to read.
Timing the Slides
In Smashing's own tests, five to seven seconds worked for a short heading, and longer text needed more time.
The Sainsbury's banner carousel uses a default of five seconds between transitions. A three-second timer is faster than that default, and it may be too fast for a slide with a full sentence.
Tip
Do not set one timer for every slide. Count the words on each slide, give longer slides more time, or drop autoplay altogether.
Autoplay Rules to Write Into the Component
Stop on hover or focus
Movement stops when a mouse pointer rests on the carousel or when keyboard focus enters it. It resumes only after the user moves away and has not taken another action.
Visible pause control
Show a clearly labeled Pause and Play control to every user, including those on touch screens and screen readers.
No surprise restart
Once a user pauses the carousel, do not restart it for them. Only the user's own press of Play should start it again.
Respect reduced motion
When a user's device asks for reduced motion, start paused or turn autoplay off entirely.
No autoplay with video
The Sainsbury's rules say autoplay should be disabled when a slide holds video or animation, because moving content can stop some users from reading or interacting.
Accessible and Usable Behavior
A carousel must work for people who use a keyboard, a screen reader, or a touch screen, and for people who are easily distracted. The W3C tutorial names four core needs: every function must work from the keyboard, every change must reach screen reader users, keyboard focus must move in a way that makes sense, and users must be able to pause carousel movement.
Keyboard use
Every control must work without a mouse. The W3C keyboard guidance places the pause, previous, and next buttons before the slide content in the tab order, which is the order the Tab key moves focus through the page, so a keyboard user meets the controls first.
Visible focus
The focus marker must be easy to see on every control. The W3C styling guidance describes indicating button status with color and shape, and a dotted border on hover or keyboard focus, and a marked control should look different from one that is not current.
Labelled controls
The carousel needs a name that describes its content, such as Product photos. Each arrow needs a name such as Previous photo or Next photo, so a screen reader user knows what each button does.
Slide announcements
A live region tells screen reader users which slide is showing, such as item 2 of 6. The W3C example turns this live region off during autoplay, because constant announcements would interrupt everything else a user is reading.
Contrast
Arrows, dots, and captions need enough contrast with the image behind them. The W3C styling guidance asks for sufficient contrast and warns that small controls must be easy to tell apart.
Touch Swipes and Target Size
The W3C styling guidance says buttons and links that are not inside a block of text should be at least 44 by 44 CSS pixels, with whitespace around them. CSS pixels are the units a web page uses to measure size. A large target helps people with reduced dexterity and people using a finger on a phone.
Placement matters on phones too.
Tip
Swipe is helpful, but it should never be the only way to move. Keep visible arrows or dots so people who cannot swipe can still reach every slide.
Worked Example: A Product Photo Carousel
Picture an online store's product page. A shopper wants to see a pair of running shoes from several angles. The store uses one large photo, a row of small thumbnails, arrow buttons, swipe on touch screens, and no autoplay. Here is how a team would build and check it.
- 1
Check the content
The six photos show the same shoe and have equal importance. This is browsing content in limited space, so a carousel fits. The price, size picker, and buy button stay outside the carousel, in the normal page flow.
- 2
Choose the props
Autoplay is off, because shoppers need time to look at each angle. Arrows are on, pagination uses thumbnails, peek is on to hint at swiping, and looping is off so the shopper can see where the set ends.
- 3
Place the controls
The arrows sit next to the large photo. On a phone, the controls sit below the image so a thumb does not cover the picture while tapping.
- 4
Size the targets
Each arrow and thumbnail is at least 44 by 44 CSS pixels, with space around it.
- 5
Make it work by keyboard
A shopper using only the keyboard can reach the arrows and thumbnails, activate them, and see a clear focus marker on the current one.
- 6
Name and announce
The region is named Product photos. The arrows are named Previous photo and Next photo. When the shopper changes photo, a screen reader hears a short message such as Photo 2 of 6.
- 7
Test the states
The team checks playing and paused, the first and last photo, a single-photo product, and a product with a missing image. Each state gets a written rule in the component documentation.
The result is that shoppers can browse every photo without losing any content or control. The price and buy button are never inside the strip, and the photos never move while a shopper is still looking.
Tip
Before you write a carousel rule, ask one question: if a person never clicks an arrow, would they miss anything they need? If yes, that content belongs outside the carousel.
Writing the Carousel Rule Once
The carousel's entry in the design system should be short enough to read in a few minutes. Use the same order every time, so any team can find an answer fast.
- 1
Name and purpose
State what the carousel is for and give one clear example of a good use.
- 2
When not to use it
List the content that must never sit inside a carousel, such as critical warnings, required steps, and primary actions.
- 3
Anatomy and props
Name each part, list the options, and give the default for each option.
- 4
States
Describe each state with a visual example, including playing, paused, focused, and the end of the list.
- 5
Accessibility checklist
Put the keyboard, focus, label, announcement, pause, reduced-motion, and target size rules in one place.
Check Your Understanding
Quick check
A team wants to put its three most important sign-up offers in a homepage carousel. The carousel moves to the next offer every 3 seconds, and users cannot pause it. What is the main problem, and what should change?
Quick check
On a phone, a product photo carousel has arrow buttons that measure about 20 by 20 pixels and sit tight against the photo's edge. Which fix best follows the component rules?
Quick check
A designer adds autoplay to a product photo carousel because it looks lively. A shopper whose device has reduced motion turned on opens the page, and the photos begin to move. Which behavior should the component have?
Summary
A carousel is a shared design system component that shows related items one or a few at a time. It is made of slides, previous and next controls, pagination, and an optional play and pause control. Its options include peek, looping, and autoplay, and the system should list the props and states each team can use.
Use a carousel for browsing items of equal importance in limited space. Keep critical content and actions out of it, and be very careful with autoplay. Make every carousel work by keyboard, show clear focus, label every control, announce slide changes, offer a pause control, respect reduced motion, and give touch targets enough room. When a team follows these rules, shoppers can browse without losing content or control.
Sources
- Sainsbury's Design System: Banner Carousel
- W3C WAI ARIA Authoring Practices: Auto-Rotating Image Carousel Example
- W3C WAI: Carousels Tutorial
- W3C WAI: Carousels Tutorial, Functionality
- W3C WAI: Carousels Tutorial, Styling
- W3C WAI: Carousels Tutorial, Structure
- Smashing Magazine: Usability Guidelines For Better Carousels UX
- Ramotion: Website Carousel Best Practices & Examples
- ADA Compliance Pros: Accessible Carousel Guide
- uxpatterns.dev: Carousel Pattern
- M&R Group: Rethinking the Carousel Trend
- 21st.dev: React Carousel Components, Swipe, Autoplay and the Accessibility Trap
- WP Dean: What Is a Carousel UI in Web Design?
Last updated on 17 November 2026
Related lessons
- Design systemsBadges: Small Status Marks That Show Counts, New Items, and States
- System designLatency vs Throughput: Time for One Request vs Work Done Over Time
- Design systemsTabs: Switch Between Related Views on One Screen Without Losing Your Place
- Design systemsSemantic Versioning: How Version Numbers Show What a Design System Change Does
Learn with me
Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.