Skip to content
Rooms
Sign inCreate a Room

Accessibility

Accessibility is part of the product, not a checkbox

A room only works if everyone in it can read it. This statement covers the current sandbox reference build of Rooms, as of July 17, 2026 — what’s genuinely implemented, what we know isn’t finished, and how to tell us what we missed.

In place

What’s implemented today

  • Keyboard paths everywhere: every interactive element is reachable and operable by keyboard, with a visible 2px focus ring on every surface, in both themes.
  • Contrast by construction: every text and control color pair in the design tokens is computed against WCAG 2.x AA (4.5:1 for text, 3:1 for UI graphics) in light and dark themes, and re-verified when tokens change.
  • Reduced motion respected globally: with “reduce motion” set, every animation and transition collapses to effectively instant, and the one looping indicator (the in-flight payment stitch) pauses — its hatched texture still carries the meaning statically.
  • Money states never rely on color alone: committed, on its way, settled, and failed each pair a distinct texture (dash, stitch, solid, break) with a visible word and amount.
  • Screen-reader names: icon-only controls carry aria-labels, decorative marks are hidden from assistive tech, and progress graphics expose full text equivalents.
  • Structure: semantic landmarks, one h1 per page, labeled form fields, and touch targets of at least 40px on mobile.
  • Numbers you can compare: amounts render in tabular figures so digits align in lists and ledgers.

Not yet

Known limitations

  • No formal conformance audit yet. Contrast is computed and keyboard paths are exercised in tests, but the product has not been audited end-to-end against WCAG 2.2 by an external specialist. That audit is planned before launch.
  • Screen-reader coverage is verified structurally (names, roles, labels, landmarks), while regular testing with the full range of real screen readers and voice-control software is still being built up.
  • This is a sandbox reference stage: pages and flows change quickly between sprints, and a regression can slip in between verifications. The standards above are the contract; a miss is a bug, not a policy.

Tell us

Found something we missed?

If any part of Rooms is hard to use with your setup — keyboard, screen reader, magnification, voice control, anything — we want the specifics: the page, what you tried, and what happened. Accessibility reports get treated as bugs, not suggestions.

Sandboxaccessibility@rooms.invalid

This is a sandbox placeholder address — the mailbox isn’t wired up yet, and no real email moves in this environment. A monitored address replaces it at launch; until then, this page is the honest record of that gap.