What's in place
Specific enough to check
Semantic HTML
Real headings in order, real lists and tables, one h1 per page. Drawings are hidden from screen readers; the text beside them says what they show.
Keyboard first
Every control is a real button or link, operable by keyboard, with a visible focus ring.
Native disclosure
FAQs use native <details>, so they open by keyboard and show up in the browser's find-in-page.
Zoom to 200%
Relative type sizes and a fluid layout, so browser zoom doesn't clip or overlap content.
Never colour alone
Every status is written in words as well as marked — a tick, a cross, a label.
Reduced motion honoured
Animation switches off under prefers-reduced-motion, and nothing depends on it to be positioned.
What hasn't been done
The gaps, listed
Everything above is our own testing. This is what that testing doesn't cover.
- Third-party auditNoNot yetNo independent accessibility audit has been commissioned.
- Screen-reader testingNoNot yetNot yet tested end to end with every major screen reader.
- The chat widgetPartlyIn partThe product's widget — as opposed to this site — hasn't had a dedicated accessibility review yet.
- WCAG 2.1 AA targetYesYesThe standard we build and test against, without claiming certified conformance.
Report a barrier
Treated as a bug, answered by a person
Tell us what you were trying to do and what got in the way. If a barrier stops you evaluating the product, we'll answer your questions directly.