Accessibility statement
We aim for WCAG 2.1 level AA on this site. We do not claim conformance: the checks below are automated, and automated rules find only part of what WCAG covers. This statement is dated 2026-10-20 and says only what we have run.
What we check
These run on every public page, and again in CI for each change we make:
- Automated accessibility rules (axe, WCAG 2.0 and 2.1 level A and AA) in a real browser (Chromium), in the light and the dark color scheme, with the cookie banner showing and with it dismissed. The same rules run on the not-found page.
- The same rules without a browser, which find structure problems (names, labels, heading order) but not color contrast.
- No sideways scrolling at 320 pixels wide, which is what 400 percent zoom gives.
- Keyboard use: the cookie banner and the skip link come first in the tab order, focus moves to the page after a cookie choice, and the phone menu opens and closes from the keyboard.
- No animation runs when your device asks for reduced motion.
- No text is clipped when you set line, paragraph, letter and word spacing.
- Lint rules for accessible markup in React (jsx-a11y), with no findings.
The browser checks run as a separate check in our CI. It is not one of the seven checks a change must pass before it merges.
What we have not done
- No audit by a person, and no third-party accessibility report. We have not commissioned one.
- No testing with a screen reader, and no testing on a real phone or tablet.
- Our capabilities statement and leave-behind (PDF files) are tagged with a structure, a language and a title. We have not run them through a PDF accessibility checker.
Report a barrier
If something on this site is hard to use, tell us through the contact form or at contracts@turboclientsystems.com. Say which page, what you were trying to do and what got in the way. We reply by email and promise no time.
