Contents

Components

Member status

The seven sync statuses a room shows next to each member, each with its tone, its mark and its words.

in sync
Props
status
import { StatusBadge } from "@sideby/ui/status";

<StatusBadge status="in sync" />

When to use it

StatusBadge shows where one member is in the watch: in sync with the host, catching up, or stuck. The room’s member list puts one next to each name. It is a Badge with the tone, the mark and the words already chosen, so every screen shows a status the same way.

All seven, in both themes

Every status, dark and light
in sync buffering catching up needs tap can't play reconnecting away
in sync buffering catching up needs tap can't play reconnecting away
import { MEMBER_STATUSES, StatusBadge } from "@sideby/ui/status";

{#each MEMBER_STATUSES as status (status)}
  <StatusBadge {status} />
{/each}

What each status means

StatusToneMeaning
in synccompletePlaying within the room’s tolerance of the host
bufferingin-flightWaiting on the network. They catch up on their own and nobody else waits
catching upin-flightPlaying slightly faster or jumping to close the gap to the host
needs tapin-flightThe browser blocked playback until the member taps once
can’t playdestructiveThis device cannot play this video. The only real failure in the set
reconnectingquietThe connection dropped and is coming back. An absence, not an error
awayquietThe tab is in the background or the member stepped out

The mapping lives in statusTone and the words in statusLabel, both exported from @sideby/ui/status with MEMBER_STATUSES, so product code never maps a status to a colour on its own.

Announcing changes

A member list never makes its badges live regions. If every badge spoke when it changed, a room of eight people buffering and catching up would talk over the film. Instead, the list renders one StatusAnnouncer and passes it a sentence when a status changes. It is a visually hidden, polite role="status" region, so a screen reader finishes what it is saying before it reads the change, once.

Change Leo’s status below. His badge updates, and the announcer reads the sentence shown under it.

Announcing a change
Leo's status
Leo in sync

Last announcement: none yet

import { StatusAnnouncer, StatusBadge } from "@sideby/ui/status";

let status = $state("in sync");
let message = $state("");

// When Leo's status changes:
status = "buffering";
message = "Leo is buffering";

<span>Leo</span> <StatusBadge {status} />
<StatusAnnouncer {message} />

  • One announcer per list. Not one per member, and never aria-live on a badge.
  • Write the sentence in product copy. “Leo is buffering”, “Leo can’t play this video”. The component announces whatever message it is given.
  • Repeats are read again. The announcer clears itself and writes the new message a moment later, so the same sentence twice still reaches the reader. For the same message twice in a row, call its announce() method through bind:this, because an unchanged message prop is not a change.
  • The first message is not announced. Only changes are, so a page load does not read out everyone’s status.
  • Announce what matters. Status changes for the reader themself, the host and failures (can’t play) are worth a sentence. A long room may choose to skip routine in-sync returns.

Accessibility

  • The words are always shown. Every status renders its label, so it never rests on colour or animation alone (WCAG 1.4.1).
  • Quiet has a dashed outline. Reconnecting and away read as absent by shape as well as by colour.
  • In-flight pulses, under motion-safe only. With reduced motion turned on, the mark stops and the words carry the state.
  • In sync uses the in-sync mark colour, which takes the focus-ring lightness in dark so the mark holds 3:1 on the page.
  • The source text is lowercase (“in sync”) and CSS uppercases it, so a screen reader reads words, not letters.
  • A badge is not a live region. Status changes in a member list are announced once, politely, by a single announcer (above).

Copy

The labels are fixed: in sync, buffering, catching up, needs tap, can’t play, reconnecting, away. Explanations go next to the badge in product copy, in the voice guide’s style: “Your video is buffering. You’ll catch up on your own, and nobody else is waiting.”