Our target
We aim for the client portal and our public pages to meet WCAG 2.2 Level AA. That is the standard we build and test against, including for keyboard use, motion, target size and focus visibility, not only the checks that automated tools can see.
What we test today
- Our public pages — sign-in, sign-up, email confirmation and this page — are scanned with axe-core on every change, in light and dark themes, at desktop and phone widths, against the WCAG 2.2 A and AA rule sets. Serious and critical violations fail the build.
- The signed-in portal pages are covered by a scan that uses the same rules and the same light/dark, desktop/phone matrix, but it needs a signed-in session and is run on demand rather than automatically on every change.
- New screens are built from our shared components, which are checked for labels, roles and focus order.
What we have not verified yet
Automated scanning catches a minority of real barriers. We are honest about the gap:
- Screen-reader and switch-control testing with real assistive technology is done manually and is not yet part of every release.
- Generated documents — PDF reports, invoices, proposals and exports — are outside the automated scan and are being reviewed separately.
- Transactional email and third-party embedded content are outside our direct control beyond choosing accessible templates and vendors.
We are therefore not claiming full conformance with WCAG 2.2 AA today. This page will say so when an independent audit supports that claim.
Telling us about a barrier
If any part of the portal or this site is hard to use with your setup, tell us and we will fix it or give you the information another way. Email [email protected] with the page and what happened. If you cannot use a feature, we will give you the same information or service another way while we fix it.