Light themes
Dark themes

Make your own

Carousel

A carousel is one row of cards that scrolls sideways and snaps to each card.

Markup

HTML
<div class="tray-carousel" data-tray="carousel">
  <ul class="tray-carousel__track" role="list" aria-label="Field notes">
    <li class="tray-carousel__slide">…a card…</li>
  </ul>
  <div class="tray-carousel__bar">
    <span class="tray-carousel__count"></span>
    <div class="tray-row tray-row--sm">…previous and next buttons with data-prev and data-next…</div>
  </div>
</div>

The track is the browser's own scroll with snapping, so swipe, trackpad and keyboard work without script; the behaviour adds the two buttons and the "2 / 5" count. Set the slide width with --tray-slide on the track (default: 78% of the track, at most 22rem), so the next card always peeks in.

Accessibility

The track is a list named by its aria-label. Keep role="list" on it: without its bullets Safari would no longer announce it as a list. The behaviour makes it one stop for Tab, where ArrowLeft and ArrowRight move one slide, mirrored under dir="rtl"; Tab also reaches every link in the slides, and the browser scrolls each into view. The previous and next buttons are icon buttons: give them aria-labels that say what they move through, such as "Next note". At either end, the button that cannot go further becomes disabled, and if it had focus, focus moves to the other button first. The count is plain text and is not announced as it changes. Under prefers-reduced-motion: reduce the buttons and keys jump to the slide instead of scrolling smoothly.

Do and don't

  • Do let the next slide show at the edge; it is the only hint that there is more.
  • Do show the count as numbers, not dots.
  • Don't auto-advance. Nothing in the system moves on its own.
  • Don't hide content that matters in slide four; a carousel is for browsing, not for must-read steps.
  • Prefer a bento of cards when everything fits.
↑↓ to moveEnter to openEsc to close