Usable without a screen.
KaiCalls is a phone service, and we think the phone should stay the interface. This page sets out the standard we build the website and dashboard against, what we have and have not verified, and how to tell us when we have got it wrong.
What we build the website and dashboard against.
The whole service can be operated by calling it.
No form, no ticket queue — email a person.
Our approach
How we think about it
Accessibility on a phone service is not only a question of markup. The most useful thing we do is make sure nothing important requires a screen at all.
The phone is a first-class interface
Running your phone service does not require a screen. You can check messages, change your greeting, follow up with a caller, and adjust how your line behaves by calling your own number and speaking to Kai. For someone who finds a dashboard hard to use, that is not a fallback — it is the primary way the product is meant to be operated.
Calls come back as text
Voicemail and calls are transcribed, and what happened on a call arrives as a written summary by text or email. A caller who would rather not listen to a recording does not have to.
Standards we build against
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA: semantic markup, labeled controls, text alternatives for meaningful images, visible focus, keyboard-reachable interactive elements, and color contrast that holds up in both light and dark themes.
Where we stand
What we have and have not verified
An accessibility statement is worth reading only if it is honest about its limits, so here are ours.
We have not completed a third-party audit
WCAG 2.1 AA is the standard we build against and test against ourselves. We have not commissioned an independent conformance audit, and we do not claim a certification we have not earned. If your organization needs a formal accessibility conformance report before purchasing, write to us and we will tell you exactly where we are.
Conformance varies across the product
The public website and the main dashboard flows get the most attention. Denser, less-traveled screens — detailed analytics tables and some configuration surfaces — are more likely to have gaps, particularly for screen-reader users. We fix what gets reported, and reports are the fastest route to a fix.
Some content comes from outside the product
Call transcripts are produced by automatic speech recognition and contain errors, particularly with names, accents, and background noise. Where call recording is turned on, the recording sits alongside the transcript, so nothing depends on the transcription being perfect. Embedded third-party content, such as payment pages, follows its provider's accessibility support rather than ours.
Tell us what is not working
If any part of KaiCalls is difficult or impossible for you to use, we want to hear about it — it is treated as a defect, not a suggestion. Tell us the page or screen, what you were trying to do, and the assistive technology and browser you were using, if you know them. We will reply, tell you whether there is a workaround in the meantime, and say when we expect to have it fixed.
You can also just call us. Speaking to a person is a supported way to get anything done here, including reporting this.