We build ViaCara to a standard called WCAG 2.2 AA. This page says how we test for it. It also says what we have not fixed yet and how to tell us about a barrier.
ViaCara is not a public body. The accessibility rules that bind a government website do not apply to us. We use the same shape of page because you may know it already.
We test to WCAG 2.2 AA
WCAG 2.2 is a technical standard for making websites and apps usable by more people. AA is the level most services aim for. We check our design system against a named set of AA rules.
These rules cover colour contrast, the size of a link and where your keyboard focus shows.
How we test it
We compute colour contrast straight from our design values, using the standard's own formula. We check target size and keyboard focus too. An automated accessibility check then tests every component as rendered, in light and dark themes.
Both checks run before a change reaches the site.
Where we fall short
No part of our design system carries a recorded shortfall against these numbers today. When we find one, we record it and the reason, and keep it on a list until it is fixed. That list can only get shorter, never longer.
Report a barrier
If something on our site or in our product is hard to use, tell us. Use our contact page and say what you found and where.
We do not wait to be asked before we fix a barrier we already know about.
Ask for another format
If you need this page, or any part of our service, in a different format, ask us the same way. Tell us what would help.
When this page changes
We review this page when the standard changes and when our service changes. We first published it, and last reviewed it, on 25 September 2026.
References
- World Wide Web Consortium (2023). Web Content Accessibility Guidelines (WCAG) 2.2. Link
