Accessibility

What we're aiming at

We build toward WCAG 2.1 Level AA. We are not claiming a formal conformance audit — we haven't had one — so here is the accurate picture instead.

What's in place

• Semantic headings and landmarks, so screen readers can navigate by structure.
• Text contrast measured against the WCAG AA thresholds — 4.5:1 for body and interface text, 3:1 for large text — on every page, at phone, tablet and desktop widths, with semi-transparent layers composited rather than estimated. Last measured 2026-08-09: no failures. Two brand colours are deliberately not used as type because they cannot pass at small sizes; a darker variant is used for coral lettering instead.
• Keyboard-operable navigation, links, buttons, and forms, with visible focus indicators.
• Form fields with real labels rather than placeholder text standing in for them.
• Text that reflows without horizontal scrolling down to a 390-pixel viewport.
• Alternative text on meaningful images; decorative images left unannounced.
• No content that flashes, blinks, or plays audio or video on its own.
• Two elements on the homepage move: a slow rotating diagram of the claim loop, and a short sequence showing the same batch of claims across three months. Neither flashes, neither makes a sound, and neither is needed to understand the page — everything they show is also written in text. If your operating system is set to reduce motion, both stop entirely and you are shown the finished state instead. The three-month sequence plays once when it scrolls into view rather than looping, and carries its own replay control.

Known gaps

• The interactive demo is a data-dense application interface. It has not been through a full assistive-technology audit, and some of its tables and status indicators may be harder to use with a screen reader than the marketing pages are.
• Some monospaced interface labels are set small for visual rhythm. They meet contrast, but they are small.