DocsReference
Accessibility
What is in place, what is not, and how to tell us when something blocks you.
By the Callaroo team. Updated November 2026
We want the public site, the documentation and the dashboard to work with a keyboard, a screen reader, a zoomed page and either colour theme. This page describes what is in place today and what still needs work. It is an honest status, not a certification.
What is in place
- Semantic headings, landmarks and lists on the public site and in the documentation.
- A skip link to the docs content, so a keyboard user can bypass the navigation.
- Visible focus styles on links, buttons and form controls.
- A light, dark and system theme. The default follows the operating system, and the choice is available in the site footer and the docs sidebar.
- Text that can be resized. The public site and documentation reflow at phone widths; dashboard screens are being reviewed at the same widths.
- Loading, success and error messages announced to assistive technology in the main dashboard workflows.
- Transcripts as a text record when a recording is missing or when audio is not usable.
- Reduced-motion handling on the public site for visitors who ask the operating system to limit animation.
- An automated check on 2026-11-08 covered form labels, link and button names, heading order, main landmarks and text contrast in both themes. It found and fixed the missing main landmark on the auth screens and low-contrast light-theme docs and auth labels.
Known limitations
- We have not completed an independent accessibility audit, and we do not claim WCAG conformance.
- The phone assistant is a voice channel. There is no text-only phone line or relay integration today.
- Recordings do not have captions. The transcript is the text alternative, and it can contain errors.
- Some dense dashboard tables and older screens have not been tested with every screen reader and browser combination.
- Stripe checkout and other third-party pages have their own accessibility behaviour, which we do not control.
- A generated summary may be shorter or less accurate than the transcript.
If something blocks you
Note the page or the task, and what you expected to happen.
Include the browser, the operating system and any assistive technology you used.
Say whether the barrier is visual, keyboard, screen reader, hearing or cognitive.
Email support@heycallaroo.com with those details. If you prefer, use the Support page.
We will not ask you to prove a disability to report a barrier. A clear description of the task and the point where it failed is enough.
For callers
The assistant answers by voice. If you cannot use a voice call, contact the business through its published website, email or in-person channel instead. The business decides which contact methods it offers; Callaroo does not currently provide a text telephone or relay service.
The public Data use page explains what happens to call data. The Privacy policy explains how to ask for a copy or deletion. The Support page explains how to reach us.