My learning 0 of 20 lessons complete
Start lesson 1 →
Back to compare picker

Carousel auto-advance without pause vs Carousel vs Tabs vs Recommendations vs Pagination

Choose the auto-advance anti-pattern label when rotation continues during keyboard focus, pointer hover, touch exploration, form entry, recommendation feedback, or reduced-motion mode.

Learn the decision

Match the interaction to the person's task

Choose the auto-advance anti-pattern label when rotation continues during keyboard focus, pointer hover, touch exploration, form entry, recommendation feedback, or reduced-motion mode.

Carousel auto-advance without pause

Use it when: Use it when a design review needs concrete evidence that motion is interrupting reading, form entry, recommendation feedback, or assistive-technology output.

Make this state clear: Rotation stopped by default state with visible current slide, total count, and Pause or Start rotation control.

Observe the result: A keyboard user tabs into the carousel, lands on Pause rotation first, stops motion, opens the visible slide action, and focus remains stable.

Study the full pattern →

Carousel

Use it when: A small set of peer slides must share one constrained display area.

Make this state clear: Initial slide state with carousel label, slide identity, current position, and previous or next controls.

Observe the result: A keyboard user tabs to Stop rotation first, pauses the carousel, moves to Next slide, activates slide 3, and focus remains on the chosen control while the status updates.

Study the full pattern →

Tabs

Use it when: Users switch between sibling panels frequently.

Make this state clear: Default active tab and visible panel.

Observe the result: Keyboard users can move focus with arrows, activate with Enter or Space, and then reach the selected panel.

Study the full pattern →

Recommendations

Use it when: Users need discovery help in a large item, product, content, service, or action space.

Make this state clear: Default recommended state with labelled section, item identity, reason, source, and action controls.

Observe the result: A signed-out shopper sees Popular in backpacks rather than fake personalized copy, then gets personalized reasons only after activity exists and consent settings allow it.

Study the full pattern →

Pagination

Use it when: The collection has many ordered results.

Make this state clear: First page with disabled previous control.

Observe the result: Users move through pages while query, filters, and sort persist.

Study the full pattern →

Practice the judgment: Imagine this situation: The pause control is hidden after anonymous dots, appears only on hover, or is unreachable from the keyboard before motion begins. Write the person's goal, choose one of these patterns, and show the state that helps the person continue. Use the decision rules and source trail below to explain your choice.

Review the underlying principle →

Decision dimensions

Dimension Carousel auto-advance without pauseCarouselTabsRecommendationsPagination
UI or UX UI + UX - Anti-pattern where timed carousel rotation changes visible content without user controlUI + UX - Sequential slide viewer for a small peer content setUI + UX - Section-switching componentUI + UX - Ranked suggestions generated from context, behavior, item similarity, popularity, editorial rules, or recommendation modelsUI + UX - Paged navigation control
UI guidance Treat automatic slide rotation as motion that must be controlled before it changes content: expose a reachable pause or stop control, current slide position, named slide controls, and a visible motion state.Render a carousel as a labelled region with one current slide or a small visible subset, clear previous and next controls, named slide picker controls or thumbnails, current slide position, and a pause or play control if rotation exists.Render a tablist with short tab labels, selected tab styling, visible keyboard focus, and a single associated tabpanel that is visually connected to the active tab.Render recommendations as a labelled set of suggested items with clear item identity, recommendation reason, source or basis, availability, and a visible way to dismiss or tune at least the current item.Render a labeled pagination nav near the affected results with current page, previous, next, nearby pages, optional first/last or ellipsis, and clear disabled edge states.
UX guidance If the business insists on auto-advance, the pause or stop path must be first, obvious, persistent, keyboard reachable, and honored across focus, hover, background-tab return, mobile interaction, and reduced-motion states.Make user control stronger than motion: avoid auto-advance by default, stop rotation on focus or hover, preserve focus after slide changes, and keep the current slide stable while users read or interact.Avoid tabs when users must compare panels, read panels sequentially, or complete required workflow steps.Use recommendations to reduce discovery effort when the system has evidence that a small set of items, products, services, content, or next actions may be useful in the user's current context.Help users move through an ordered result set with a stable sense of position, progress, and returnability.
Good UI A campaign carousel loads paused, shows Stop rotation before Next and Previous, names each slide, and changes only after the user chooses Start rotation.A product tour carousel shows one feature slide at a time with Previous, Next, Stop rotation, labelled slide dots, and text announcing Slide 2 of 4.Tab labels are short, active tab is obvious, focused tab is distinguishable, and panel content is visually attached to the selected tab.A commerce product page shows Pairs well with this camera, hides out-of-stock accessories, limits the rail to three visible items, and marks manually selected merchant recommendations separately from generated recommendations.Current page, previous/next, disabled edges, page numbers, result range, and total count are visually clear.
Bad UI A homepage hero advances every four seconds, hides Pause after the slide dots, and keeps moving while keyboard focus is inside a slide CTA.Auto-rotation moves content before users finish reading.Tabs wrap unpredictably or look like unrelated buttons.A recommendation list keeps showing unavailable, out-of-stock, permission-restricted, or already dismissed items because the UI only validates card shape.Pagination jumps around as pages load or separates controls from the result list.
Good UX A keyboard user tabs into the carousel, lands on Pause rotation first, stops motion, opens the visible slide action, and focus remains stable.A keyboard user tabs to Stop rotation first, pauses the carousel, moves to Next slide, activates slide 3, and focus remains on the chosen control while the status updates.Keyboard users can move focus with arrows, activate with Enter or Space, and then reach the selected panel.A signed-out shopper sees Popular in backpacks rather than fake personalized copy, then gets personalized reasons only after activity exists and consent settings allow it.Users move through pages while query, filters, and sort persist.
Bad UX Slides advance before users finish reading.A user starts reading shipping details and the carousel advances to a different slide before they finish.Using tabs as primary navigation to unrelated pages.Users assume recommendations are mandatory next steps because the UI mixes them with required workflow tasks.Changing page resets filters.
Best fit Use it when a design review needs concrete evidence that motion is interrupting reading, form entry, recommendation feedback, or assistive-technology output.A small set of peer slides must share one constrained display area.Users switch between sibling panels frequently.Users need discovery help in a large item, product, content, service, or action space.The collection has many ordered results.
Avoid when Choose another interaction when the task calls for a different route.Every item is important or users need to compare items.The destinations are unrelated pages.The product has too few items for ranking to reduce effort.Users need uninterrupted reading or comparison.
Required state Rotation stopped by default state with visible current slide, total count, and Pause or Start rotation control.Initial slide state with carousel label, slide identity, current position, and previous or next controls.Default active tab and visible panel.Default recommended state with labelled section, item identity, reason, source, and action controls.First page with disabled previous control.
Accessibility burden Provide a keyboard-reachable pause or stop control before rotating content and before slide navigation controls.Label the carousel region by its purpose, such as Featured product tour or Case study slides.Expose the active tab and associated panel.Make recommendation reasons, sponsored labels, availability, and item type available as text.Use a labeled navigation region.
Common misuse Hiding Pause behind carousel dots, hover-only controls, or an overflow menu.Hiding critical content or required tasks on later slides.Using tabs as a primary site navigation system.Pretending generated suggestions are recently viewed, saved, or required steps.Using pagination for a tiny collection.

Carousel auto-advance without pause

UI or UX
UI + UX - Anti-pattern where timed carousel rotation changes visible content without user control
UI guidance
Treat automatic slide rotation as motion that must be controlled before it changes content: expose a reachable pause or stop control, current slide position, named slide controls, and a visible motion state.
UX guidance
If the business insists on auto-advance, the pause or stop path must be first, obvious, persistent, keyboard reachable, and honored across focus, hover, background-tab return, mobile interaction, and reduced-motion states.
Good UI
A campaign carousel loads paused, shows Stop rotation before Next and Previous, names each slide, and changes only after the user chooses Start rotation.
Bad UI
A homepage hero advances every four seconds, hides Pause after the slide dots, and keeps moving while keyboard focus is inside a slide CTA.
Good UX
A keyboard user tabs into the carousel, lands on Pause rotation first, stops motion, opens the visible slide action, and focus remains stable.
Bad UX
Slides advance before users finish reading.
Best fit
Use it when a design review needs concrete evidence that motion is interrupting reading, form entry, recommendation feedback, or assistive-technology output.
Avoid when
Choose another interaction when the task calls for a different route.
Required state
Rotation stopped by default state with visible current slide, total count, and Pause or Start rotation control.
Accessibility burden
Provide a keyboard-reachable pause or stop control before rotating content and before slide navigation controls.
Common misuse
Hiding Pause behind carousel dots, hover-only controls, or an overflow menu.

Carousel

UI or UX
UI + UX - Sequential slide viewer for a small peer content set
UI guidance
Render a carousel as a labelled region with one current slide or a small visible subset, clear previous and next controls, named slide picker controls or thumbnails, current slide position, and a pause or play control if rotation exists.
UX guidance
Make user control stronger than motion: avoid auto-advance by default, stop rotation on focus or hover, preserve focus after slide changes, and keep the current slide stable while users read or interact.
Good UI
A product tour carousel shows one feature slide at a time with Previous, Next, Stop rotation, labelled slide dots, and text announcing Slide 2 of 4.
Bad UI
Auto-rotation moves content before users finish reading.
Good UX
A keyboard user tabs to Stop rotation first, pauses the carousel, moves to Next slide, activates slide 3, and focus remains on the chosen control while the status updates.
Bad UX
A user starts reading shipping details and the carousel advances to a different slide before they finish.
Best fit
A small set of peer slides must share one constrained display area.
Avoid when
Every item is important or users need to compare items.
Required state
Initial slide state with carousel label, slide identity, current position, and previous or next controls.
Accessibility burden
Label the carousel region by its purpose, such as Featured product tour or Case study slides.
Common misuse
Hiding critical content or required tasks on later slides.

Tabs

UI or UX
UI + UX - Section-switching component
UI guidance
Render a tablist with short tab labels, selected tab styling, visible keyboard focus, and a single associated tabpanel that is visually connected to the active tab.
UX guidance
Avoid tabs when users must compare panels, read panels sequentially, or complete required workflow steps.
Good UI
Tab labels are short, active tab is obvious, focused tab is distinguishable, and panel content is visually attached to the selected tab.
Bad UI
Tabs wrap unpredictably or look like unrelated buttons.
Good UX
Keyboard users can move focus with arrows, activate with Enter or Space, and then reach the selected panel.
Bad UX
Using tabs as primary navigation to unrelated pages.
Best fit
Users switch between sibling panels frequently.
Avoid when
The destinations are unrelated pages.
Required state
Default active tab and visible panel.
Accessibility burden
Expose the active tab and associated panel.
Common misuse
Using tabs as a primary site navigation system.

Recommendations

UI or UX
UI + UX - Ranked suggestions generated from context, behavior, item similarity, popularity, editorial rules, or recommendation models
UI guidance
Render recommendations as a labelled set of suggested items with clear item identity, recommendation reason, source or basis, availability, and a visible way to dismiss or tune at least the current item.
UX guidance
Use recommendations to reduce discovery effort when the system has evidence that a small set of items, products, services, content, or next actions may be useful in the user's current context.
Good UI
A commerce product page shows Pairs well with this camera, hides out-of-stock accessories, limits the rail to three visible items, and marks manually selected merchant recommendations separately from generated recommendations.
Bad UI
A recommendation list keeps showing unavailable, out-of-stock, permission-restricted, or already dismissed items because the UI only validates card shape.
Good UX
A signed-out shopper sees Popular in backpacks rather than fake personalized copy, then gets personalized reasons only after activity exists and consent settings allow it.
Bad UX
Users assume recommendations are mandatory next steps because the UI mixes them with required workflow tasks.
Best fit
Users need discovery help in a large item, product, content, service, or action space.
Avoid when
The product has too few items for ranking to reduce effort.
Required state
Default recommended state with labelled section, item identity, reason, source, and action controls.
Accessibility burden
Make recommendation reasons, sponsored labels, availability, and item type available as text.
Common misuse
Pretending generated suggestions are recently viewed, saved, or required steps.

Pagination

UI or UX
UI + UX - Paged navigation control
UI guidance
Render a labeled pagination nav near the affected results with current page, previous, next, nearby pages, optional first/last or ellipsis, and clear disabled edge states.
UX guidance
Help users move through an ordered result set with a stable sense of position, progress, and returnability.
Good UI
Current page, previous/next, disabled edges, page numbers, result range, and total count are visually clear.
Bad UI
Pagination jumps around as pages load or separates controls from the result list.
Good UX
Users move through pages while query, filters, and sort persist.
Bad UX
Changing page resets filters.
Best fit
The collection has many ordered results.
Avoid when
Users need uninterrupted reading or comparison.
Required state
First page with disabled previous control.
Accessibility burden
Use a labeled navigation region.
Common misuse
Using pagination for a tiny collection.
Decision rules
  • Choose the auto-advance anti-pattern label when content rotates on a timer and users cannot pause or stop before the first slide change.
  • Choose the auto-advance anti-pattern label when rotation continues during keyboard focus, pointer hover, touch exploration, form entry, recommendation feedback, or reduced-motion mode.
  • Choose carousel only for a small peer slide set in one constrained visual slot, with previous, next, named picker, visible position, and first reachable pause or play controls when motion exists.
  • Choose tabs when users choose among named sibling panels; tabs should not auto-advance, hide required content, or pretend slide dots are meaningful tab labels.
  • Choose recommendations when items are ranked, contextual, sponsored, personalized, or model-selected; reasons, dismissal, save, feedback, and sponsored disclosure must remain stable even if the presentation uses a rail.
  • Choose pagination when users browse a large ordered result set with page numbers, current page, ranges, totals, previous and next, and return-position persistence.
  • Prefer static page sections, a list, or a grid over any carousel when every item matters, comparison is important, or users need stable reading time.
  • If rotation exists, Pause or Stop must be first reachable in the carousel tab order, visible on mobile, and honored for focus, hover, reduced motion, and background tab return.
  • Do not use auto-advance for legal terms, eligibility warnings, consent choices, required forms, checkout details, or any content where missing one slide changes the user's outcome.
  • Do not announce timer-driven slide changes repeatedly; reserve status changes for user-initiated controls and explicit motion-state changes.
Inspect live examples
Failure modes
  • A hero carousel advances every few seconds with no pause and users lose the sentence they were reading.
  • The pause control is hidden after anonymous dots, appears only on hover, or is unreachable from the keyboard before motion begins.
  • A focused slide button remains in the tab order while the visible slide rotates away.
  • Reduced-motion users still receive automatic rotation and large animated transitions.
  • A recommendation carousel rotates away reasons, dismiss controls, sponsored labels, or feedback while the user is deciding.
  • Tabs are implemented as auto-rotating panels, so named sections change without user choice.
  • A large ordered result set is squeezed into a carousel, losing current page, result range, total count, and return position.
  • Screen reader users hear constant unsolicited announcements for timer-driven slide changes.

Saved items