Trust
Accessibility statement
Last updated 22 October 2026
The public site, the customer console and the operations console are built to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. This statement says how that is checked and what does not yet meet it.
How it is checked
- Every page type, as each kind of user, is tested with axe-core against the WCAG 2.0, 2.1 and 2.2 A and AA rules, at desktop and phone widths. On 22 October 2026 no page had a violation.
- Automated rules find only part of what matters. Keyboard use and focus order are also tested on the main journeys: reading the site, the phone menu, signing in, and working through findings.
- Testing with screen readers (NVDA, JAWS, VoiceOver) and an independent audit against WCAG 2.2 AA have not yet been done. We will publish the results here.
What you can expect
- Every page can be used with a keyboard alone, starts with a link to skip to its content, and shows clearly where focus is.
- Text meets AA contrast. Links inside text are underlined, and every verdict and finding pairs a glyph with a label, so meaning never depends on colour.
- Every form field has a visible label. Errors and confirmations are announced to screen readers.
- Charts have a text summary, and the values as a table, for screen readers.
- Navigation works at phone width: the site's menu folds into a Menu button, and the consoles' side rail becomes a row of tabs.
- Pages honour the reduced-motion setting, and times are labelled with their time zone (UTC).
Known limitations
- The consoles are dark only; a light theme is not yet available.
- Wide tables scroll sideways on small screens. Each can be reached and scrolled with the keyboard.
- The Baseline report and attestation files are generated documents; the report is tested for contrast and structure, the attestation is JSON for machines and auditors.
Tell us
If something does not work for you, tell us through support or the contact form, and we will help you get what you need another way while we fix it.