What we test for accessibility, and what we do not
This page lists the automated accessibility checks that run on every public page of the Turbo Governance System website. It is a description of those checks. It is not a statement that the site conforms to any level of WCAG.
Last read against the test setup on October 19, 2026.
What is tested
Every public page, including each documentation topic, is scanned with axe-core in a real browser as part of our continuous-integration checks. The scan runs the WCAG 2.0, 2.1 and 2.2 level A and AA rules plus axe-core’s best-practice rules, at a 375-pixel and a 1280-pixel viewport width. A change that causes a violation on any page fails those checks.
A second scan runs each page in a simulated browser with the WCAG 2.1 level A and AA rules. It cannot check color contrast or page regions, which the real-browser scan covers.
What this does not show
Automated tools find only part of the problems that WCAG describes. We have not documented a manual keyboard or screen reader review of these pages, and no outside party has audited them. We make no claim of conformance with WCAG or Section 508.
Known barriers
No barrier is known to us as of the date above. That reflects the automated scans passing and the absence of reports, not an audit finding.
Report a barrier
If a page stopped you from reading it or finishing a task, please send us a message through the contact form. Name the page and what you were trying to do. This page covers the public website only. The application you reach through "Log in" is a separate site.