Accessibility
What we build to, what is already in place, and the limitations we know about and have not fixed yet.
Effective 19 August 2026Last updated 19 August 2026
Our commitment
is used in short moments — on a phone, one-handed, often tired. That is close enough to the conditions accessibility work is designed for that we treat the two as the same problem.
We build to WCAG 2.2 Level AA as our target. This statement describes where we actually are against it, including where we fall short.
What is in place
- Keyboard — every interactive control is reachable and operable by keyboard, with a visible focus indicator that meets the contrast requirement.
- Screen readers — semantic headings, landmarks, labelled form fields, and tabular data marked up as real tables with row and column headers.
- Contrast — body text meets or exceeds 4.5:1, and large text and interface components meet 3:1. Colour is never the only carrier of meaning.
- Text sizing — the site is fluid and readable at 200% zoom without horizontal scrolling, and honours Dynamic Type on iOS.
- Motion — every animation is suppressed under
prefers-reduced-motion. Nothing autoplays, moves for longer than five seconds, or flashes. - Targets — interactive targets are at least 44 by 44 pixels on touch surfaces.
- Voice notes — recordings are transcribed, so the content of a check-in is available as text.
Known limitations
We would rather list these than let you discover them. As of the date at the top of this page:
- Voice note transcription accuracy varies with accent and background noise, and transcripts are not manually corrected.
- Some product screenshots used on marketing pages carry a descriptive alt text of the screen rather than a full transcription of every value shown in it.
- The iPad app currently runs the iPhone layout, which is not ideal at large sizes.
- We have not yet commissioned an independent third-party audit. Our testing is internal, with screen readers and keyboard-only passes.
Telling us about a problem
Send the page or screen, what you were trying to do, what happened, and the assistive technology and browser or device you were using. None of that is required — write what you can and we will follow up.
We aim to acknowledge within two working days and to give you a realistic timeline rather than a vague one.
Standard and scope
This statement covers the marketing website, the web application, and the iOS app. It is a self-assessment against Web Content Accessibility Guidelines 2.2 Level AA, and it is reviewed when significant changes ship.
