Last updated 2 August 2026. PrivyHealth is built to be usable by everyone, including people who use screen readers, keyboard navigation, voice control, or magnification.
Our target
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, the standard referenced by the Americans with Disabilities Act and the European Accessibility Act. We measure ourselves against it as we build, rather than claiming a completed audit.
What we've done
• Every screen works with keyboard alone, with visible focus outlines.
• Buttons, icons, and images carry text labels or alternative text.
• Colour is never the only signal — shared/private states, plan differences, and macro changes all carry text or icons too.
• Text meets AA contrast against our dark palette and scales with your device settings.
• Forms use real labels, and errors are announced, not just coloured red.
• Animation is subtle and respects your reduce-motion preference.
Known limitations
We'd rather be honest than tick a box. These are the areas we know need work:
• The swipe-to-confirm gesture when approving a meal estimate is easiest with a pointer or touch. A keyboard and screen-reader accessible confirm button is always available alongside it.
• Charts and macro comparison bars convey trends visually; the same figures are always given as text, but the charts themselves aren't yet fully described.
• The payment checkout is provided by Paddle, so its accessibility is outside our direct control.
Tell us about a barrier
If any part of PrivyHealth is hard to use, we want to hear about it and we'll help you get what you need in the meantime. We aim to reply within five working days.