Skip to content
Try Roooster free, cancel any time.Start free
Roooster
Start free

Accessibility Statement

Last updated: August 2026

Our commitment

Roooster is built so that home service operators, technicians, and the customers they serve can use the product regardless of ability. We treat accessibility as a product requirement, not a compliance afterthought.

Conformance target

Roooster is being designed and audited against the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. Our priority surfaces (the public booking flow, the customer-facing quote Accept page, the customer portal, the operator dashboard, and the technician day view) are audited individually and remediated as findings come in.

What works today

  • Keyboard navigation across all primary flows (Quote, Book, Dispatch, Invoice).
  • Semantic HTML and ARIA roles on interactive components built on Radix UI primitives (dialogs, menus, comboboxes).
  • Visible, high-contrast focus indicators in both light and dark themes.
  • Color choices that meet AA contrast for body text and interactive elements.
  • Form fields paired with explicit <label> elements; required and error states announced to assistive technology.
  • Mobile day-view designed for one-handed use with large tap targets and reduced motion.
  • A skip-to-content link on every public marketing page, visible on keyboard focus.
  • Marketing animations respect the operating system's reduced-motion preference.
  • Links that open in a new window say so to assistive technology.

Known limitations

We're honest about what isn't done yet:

  • The map-based dispatch and route surfaces (Mapbox-rendered) are not yet fully reachable by keyboard or screen reader. Tabular fallbacks are available for the same data.
  • Embedded marketing video does not yet ship captions; an audio-described version is on the roadmap.
  • Some lower-traffic admin tables have not yet been audited for non-table screen-reader presentation.

When we ship a remediation, we update this page.

How we audit

We combine automated and manual testing. Every public marketing page is scanned with axe-core (WCAG 2.1 A/AA rules) in a real browser during development, and a static accessibility lint runs as a required gate on every deploy, catching regressions such as missing image descriptions, suppressed focus indicators, and broken heading order before they ship. We supplement this with manual keyboard-only navigation and screen-reader testing (VoiceOver on macOS / iOS, NVDA on Windows) across our priority surfaces. Engaging an external auditor for a full WCAG 2.1 AA review before general availability remains on the roadmap: automated scanning catches many issues, but not all of them.

Report a barrier

If something blocks you from using Roooster, please tell us. Email contact@roooster.ai with the page URL, the device and assistive technology you use, and a short description of the barrier. We aim to acknowledge within two business days and to provide an alternative path to accomplish the task while we ship a fix.