What is built, what is untested, and how to tell us it is wrong.
The standard we build to is WCAG 2.2 level AA. This statement says what has actually been done, what has not been independently verified, and what to do when you hit something that does not work. It does not claim conformance, because nobody outside this team has tested it yet.
Status
Haven has not been independently audited for accessibility. There is no VPAT, no accessibility conformance report, and no assistive-technology testing by anybody who does it for a living. Everything below is what the code does, checked by us.
A statement that claimed conformance on that evidence would be the same kind of claim this product spends the rest of the site refusing to make.
What is built
- Keyboard. A skip link to the main content, and visible focus rings that appear for keyboard users without following a mouse around the page.
- Screen readers. Live regions announce what changes without a page reload — a message arriving, a send failing, a call state changing — and the document declares its language.
- Motion. Animation is dropped when the operating system asks for reduced motion, in six places across the interface.
- Targets. Controls that are only reachable by touch — the call pill's buttons among them — are held at a 44-pixel minimum.
- Colour and theme. Light, dark and a true-black theme, all built from the same tokens rather than hard-coded values, and numbers rendered with tabular figures so a changing count does not shift the layout under a reader.
- Text. The interface scales with the browser's text size; nothing here is drawn as an image of words.
What we know is not good enough yet
- No independent audit and no conformance report, as above.
- No testing with VoiceOver, NVDA, JAWS or TalkBack by an experienced user of any of them. Our own testing is not a substitute and we are not going to pretend otherwise.
- The call interface is the densest part of the product and the least exercised with a keyboard alone.
- Some on-device features — translation, voice-note transcription — exist only in browsers that ship the underlying model. Where they are absent the control is hidden rather than shown as broken, which is the right behaviour but does mean the feature set differs by browser.
Telling us something does not work
Use the contact form, and say what you were trying to do, what happened, and what you use to browse. We would rather have a report that turns out to be our misunderstanding than not hear about it.
If you are procuring this for an organisation with a legal accessibility duty — a UK public body under the 2018 regulations, or a service in scope of the European Accessibility Act — tell us that too. It changes what evidence you need from us, and it is better to find that out before a contract than after one.
Statement prepared 17 September 2026. It will be revised when the gaps above change.