Carousel auto-advance without pause

Problem Context

• A carousel, hero, promotion rail, onboarding slider, or recommendation strip changes visible content on a timer.
• The slide can contain text, calls to action, form fields, recommendation reasons, feedback controls, warnings, or decision-support information.
• Users may read slowly, use keyboard or assistive technology, hover for detail, switch tabs, use mobile gestures, or prefer reduced motion.
• The product wants motion for attention, but users need control over timing, focus, announcements, and recovery.

Selection Rules

• Flag the anti-pattern whenever visible carousel content changes automatically and a pause or stop control is missing, delayed, hidden, or unreachable before the moving content.
• Choose a standard carousel only when the slide set is small, supplemental, manually controllable, and safe to browse one slide at a time.
• Use tabs when users are switching among named sibling panels; tab panels should not rotate on a timer.
• Use recommendations when the rail contains ranked or personalized suggestions that need reasons, dismissal, sponsored labels, and feedback controls that must not rotate away mid-action.
• Use pagination, a list, or a grid when users need stable position, large result sets, comparison, or repeated scanning.
• Disable auto-advance for text-heavy, task-critical, form, consent, legal, eligibility, warning, checkout, or assistive-technology sensitive content.
• If auto-advance remains, put Pause or Stop before slide-changing controls in tab order and keep it visible in every responsive layout.
• Stop rotation when keyboard focus enters the carousel, when pointer hover suggests reading, when a slide control opens, and when the page returns from the background.
• Respect reduced-motion preferences by disabling timed rotation and minimizing animated transitions.
• Do not announce automatic slide changes repeatedly; reserve polite status updates for user-initiated changes or explicit motion-state changes.

Required States

• Rotation stopped by default state with visible current slide, total count, and Pause or Start rotation control.
• Pause first state where the stop control is first in the carousel tab order before previous, next, pickers, or slide actions.
• User-start rotation state that begins motion only after an explicit command and exposes how to stop it.
• Focus stop state where keyboard focus inside the carousel stops rotation and preserves focus.
• Hover stop state where pointer hover or slide interaction stops rotation while the user reads.
• Reduced-motion state where automatic rotation and nonessential animation are disabled.
• Resume safely state where rotation resumes only after explicit user action and does not skip unread slides.
• Slide action stable state where activating a slide link, save, dismiss, or feedback control does not trigger a timed advance.
• Reading lock state for long copy, captions, disclosures, warnings, or eligibility details.
• Form entry lock state where typed input, validation, and focus persist without the slide disappearing.
• Background tab return state where a hidden page does not fast-forward slides or restart motion without consent.
• Bad no-pause state with moving slides and no reachable stop control.
• Bad hidden-pause state where pause exists after anonymous dots, in an overflow, or only on hover.
• Bad focus-ignored and hover-ignored states where rotation continues during keyboard or pointer reading.
• Bad constant-announcement state where assistive technology receives unsolicited slide updates.

Interaction Contract

• Pause or Stop rotation immediately freezes the visible slide, updates the motion state, and remains available for resume or restart.
• Start rotation is explicit, reversible, and does not remove manual previous, next, picker, or slide action controls.
• Focus entering any carousel control or slide action stops rotation before timed content changes.
• Pointer hover, touch exploration, opened popovers, expanded text, recommendation feedback, and form fields keep the current slide stable.
• Reduced-motion and user-disabled animation settings override any configured auto-advance timer.
• Returning from a background tab, minimized app, or locked mobile screen does not fast-forward through missed slides.
• User-initiated slide changes may update a polite status; timer-driven changes must not create repeated unsolicited announcements.

Implementation Checklist

• Decide whether auto-advance is needed at all; default to paused or static content unless the user starts motion.
• Place Pause or Stop rotation first in the carousel DOM and visible control order when rotation can occur.
• Bind focusin, pointer hover, touch interaction, form input, popover open, and recommendation feedback states to stop or suspend rotation.
• Check prefers-reduced-motion and product-level motion settings before enabling timers or animated transitions.
• Preserve current slide, focused element, typed values, open disclosures, selected recommendation feedback, and live-region behavior while pausing and resuming.
• Use named slide controls and a visible slide count so users can recover the slide that moved.
• Throttle or suppress automatic live-region announcements and announce only user-commanded changes.
• Test keyboard, screen reader, hover, touch, mobile viewport, reduced motion, background tab return, slow reading, form entry, recommendation feedback, and failure recovery.

Common Generated-UI Mistakes

• Hiding Pause behind carousel dots, hover-only controls, or an overflow menu.
• Starting rotation automatically because marketing wants movement without testing reading time or assistive technology impact.
• Continuing to rotate while focus is inside a slide, a form field has text, or the pointer is hovering over details.
• Treating a recommendation rail as a decorative carousel and rotating away reasons, dismiss buttons, sponsored labels, or feedback.
• Announcing every timer-driven slide change to screen readers.
• Ignoring reduced-motion preferences because the slide transition seems slow.
• Fast-forwarding through several slides when the tab regains visibility.
• Using auto-advance to hide stakeholder prioritization problems instead of choosing a static hierarchy.

Critique Questions

• Can users stop the carousel before any automatic change happens?
• What exactly happens when keyboard focus enters the carousel?
• Does hover, touch exploration, or reading a long caption suspend motion?
• Does reduced motion fully disable auto-advance or only shorten the animation?
• Can a user recover a slide that moved while they were reading or typing?
• Are recommendation reasons, feedback, sponsored labels, warnings, or form fields rotating away?
• Would tabs, a static section, a recommendation list, a grid, or pagination better match the content job?