What Is a Carousel? Ad Formats, UI Design, and Accessibility

July 8, 2026

Author: Shusaku Yosa
カルーセル(広告/UI)とは?種類と効果的な使い方をわかりやすく解説

A carousel is a display pattern that presents multiple pieces of content in sequence within one region. It appears in website image panels, product cards, and multi-card advertisements. The terms carousel, slider, and slideshow overlap: the name alone does not establish automatic rotation, looping, or a single visible card. Define the actual behavior and context before choosing the design.

The W3C carousel tutorial acknowledges overlapping names such as carousel, slideshow, and slider. Implementations can show one or several items and allow manual movement, automatic rotation, or both. A naming distinction is less useful than a clear interaction specification.

Specification axis

Record

Do not infer from the name

Name

Carousel, slider, or another label

Different labels may describe similar structures

Movement

Automatic, manual, or both

Automatic rotation is not mandatory

End behavior

Loop or stop

Looping is not a defining requirement

Visible items

One or several

A single-card view is not universal

Context

Own website or platform advertisement

Editable behavior differs

Answer the definition question first, then move into design, advertising, or measurement according to the reader’s task.

Separate an ad format from a website component

For your own website component, the implementation team can design pause controls, navigation, image alternatives, announcements, and focus behavior. An advertising platform controls much of the delivered interaction. Distinguish editable submission fields from behavior that can only be checked.

Area

Own website UI

Advertising format

Content

Your implementation and editorial rules

Platform submission requirements

Navigation and pause

Designed and tested by your team

Available platform behavior

Alternative information

Designed for image purpose and context

Editable fields must be checked

Measurement

Custom specification where implemented

Available platform reporting

Order

Your ordering and change logic

Platform and placement-specific rules

Do not promise to customize an advertisement’s controls as if it were a component on your own site.

Decide whether the content benefits from multiple cards

A carousel can help present related choices in a compact area or structure a short sequence. However, later cards may never be seen. Avoid hiding the essential offer, conditions, or only action on the final card and assuming every visitor will follow the sequence.

A comparison table or static list can be more useful when readers need to inspect choices simultaneously. A permanent notice can be better for essential information. Decide whether the reader is selecting, learning in order, or finding a next action before adding more cards.

Plan a three-card sequence that works at each entry point

This is a fictional booking-service example, not a NeX-Ray feature or customer result. Each card should identify the service and offer a meaningful next step even when viewed independently.

Card

Purpose and example message

Destination

Required context

1

Find an available appointment

Availability list

Service name, region, free or paid conditions

2

Compare dates, prices, and cancellation terms

Terms explanation

Verified conditions; no invented results

3

Review the conditions and continue to booking

Booking instructions

Useful action; not the only CTA

A vague “Learn more” label may obscure the destination. Check that a reader starting with card two still knows what is being booked. Update the card, linked page, and text inside images together when conditions change.

Design pause, keyboard, focus, and screen-reader behavior

The W3C carousel pattern calls for automatic rotation to stop when keyboard focus enters the carousel and not restart without explicit user action. Changing the rotation speed alone does not solve content moving while someone is reading.

  • Reach navigation and pause controls using Tab and Shift+Tab.
  • Provide understandable previous, next, pause, and resume names.
  • Stop rotation on focus and prevent unsolicited restart.
  • Keep hidden slides from becoming unintended focus or reading targets.
  • Communicate the current position and relevant changes.
  • Support keyboard operation rather than relying only on swipes.

Provide alternatives according to the image’s purpose. Test with a keyboard and assistive technology rather than accepting a visual inspection as the whole accessibility review.

Check platform-specific assets, counts, and ordering

Use the documentation for the actual format, such as Google Ads Demand Gen carousel guidance. Check image ratios, counts, text, links, supported placements, and ordering. A rule from one platform is not a universal rule for all carousel ads.

Do not invent a shared card-count limit or an image/video mixing rule across platforms. For a website, inspect cropping, text, spacing, and control access on narrow screens. Consider asset loading and size so that essential information is not delayed or obscured.

Measure exposure and clicks in your own interface

The following is a hypothetical custom measurement design for your own interface. Names such as carousel_view, slide_visible, and card_click are illustrative custom events, not automatically collected GA4 events. Use non-personal carousel_id, slide_id, and position values.

Example event

Hypothetical trigger

Counting rule

carousel_view

Region meets the chosen visibility condition

Session × carousel

slide_visible

At least 50% of the card is visible for one second

Once per session × card

card_click

A card link is activated

Click presence using the same unit

The 50% and one-second rule is an example, not a universal Google or platform standard. If 300 session-card units are exposed and 60 have a click, card CTR is 60 / 300 = 20%. Use matching exposure and click units, not all pageviews as the denominator. For ads, first establish whether the platform supplies the necessary detail.

Use a prelaunch checklist and a focused improvement test

Before launch, assign owners to check each card’s audience, terms, destination, narrow-screen layout, keyboard behavior, pause controls, announcements, imagery, and collection. A low-exposure card should not be ranked on CTR alone; inspect earlier exits, loading, and navigation.

For an improvement test, limit the change to a defined feature such as order, copy, or controls, while retaining exposure and outcome definitions. More impressions alone are not success. Review whether people could read the conditions and take the relevant next step. A three-card planning register and an interaction checklist provide a useful starting point.

Continue with the guide that matches your next task: How to Write alt Text: Examples by Image Purpose and Context; A/B Testing Tools Compared: Free Access, GA4 Integration, and Setup; GA4 Parameters: Design, Send, Register, and Validate Custom Data.

Related posts