WORKSHOP REFERENCE // 9 QUESTIONS ANSWERED

FAQ: Carousel Decisions Explained

Clear, practical answers to the technical and editorial questions that come up most often when building human-paced sequences.

Two front-end beginners and a senior designer reviewing annotated carousel wireframes on paper

FIG 06. Every accessibility rule becomes simpler when you trace how a real person navigates the screen.

QUESTION 01 // THE CORE ARCHITECTURE CHOICE

1. When should I use a carousel instead of a simple image gallery?

Use a carousel only when the linear sequence of frames carries meaning—such as a chronological architectural restoration, a four-step printmaking proof progression, or an annotated design walk-through where Slide 2 answers a question raised by Slide 1. If the viewer needs to compare items side by side (like choosing between six workshop rooms), a static multi-column gallery grid is always clearer.

QUESTION 02 // AUTOPLAY & MOTION

2. Why do you advise against auto-advancing slides?

People read captions and inspect visual details at widely different speeds. An automatic 5-second timer yanks the slide away while a low-vision reader is panning across the image with a screen magnifier, and forces WCAG 2.2.2 pause/stop complexity onto the interface. Manual buttons put the viewer in calm control.

QUESTION 03 // SEQUENCE LENGTH

3. How many slides should one sequence contain?

Aim for 3 to 5 slides. Five frames are enough to establish context, show process evidence, and reveal an outcome without fatiguing the reader. If you have 12 or 15 photographs, break them into thematic chapters down the page.

QUESTION 04 // KEYBOARD FOCUS

4. Where should keyboard focus go when a user clicks "Next"?

Keep focus directly on the "Next" button while announcing the new slide title via an aria-live="polite" status element. That way, a keyboard user can step through all slides with repeated presses of Enter or Space without re-tabbing.

QUESTION 05 // LAZY LOADING

5. Should I put loading="lazy" on every carousel image?

Keep Slide 1 eager (no lazy attribute) if the carousel appears near the top of the viewport so Largest Contentful Paint stays fast. Add loading="lazy" and explicit width and height attributes to Slides 2, 3, and beyond.

QUESTION 06 // ALT TEXT VS. CAPTIONS

6. Do I still need alt text if every slide has a visible caption?

Yes. Leaving alt="" empty hides the existence of the photograph from screen-reader users, leaving them with a caption commenting on an invisible object. Write concise alt text describing what is visually in the frame, and use the caption to explain historical or technical context.

QUESTION 07 // TOUCH SWIPE

7. Is touch swipe enough on mobile screens, or do I still need buttons?

You always need visible Previous and Next buttons. Many people with motor impairments use voice control ("Click Next") or single-switch scanning on mobile devices where horizontal dragging gestures are difficult or impossible.

QUESTION 08 // DOT INDICATORS

8. Are small dot indicators at the bottom of a carousel accessible?

Tiny 8-pixel dots fail touch target size guidelines (WCAG 2.5.8 requires at least 24×24px, ideally 44×44px) and convey no meaning unless labelled. Replace bare dots with numbered pill buttons like 01. Survey, 02. Joinery, and 03. Trial.

QUESTION 09 // NO-JS FALLBACK

9. What happens if JavaScript fails to load on a slow connection?

If you style your carousel slides cleanly or use progressive enhancement—only hiding slides 2 and 3 once the script initializes—visitors on restricted connections will simply see all three slides stacked vertically as a readable article.