Loading…
Loading…
We aim for WCAG 2.1 AA across the web app and the marketing site. Below is what we’ve done, what is in flight, and the known gaps. If you hit a barrier, email contact@agiworkforce.com · we treat it as a P0.
What we’ve done
| Keyboard | A skip-link is mounted on every page, and keyboard reachability is a requirement we hold new interactive components to. We have not completed a keyboard-operability audit across all six surfaces and hold no VPAT, so we do not claim every element passes. If you find one that does not, it is a bug and we will treat it as one. |
| Screen reader | Semantic HTML · landmarks, headings in order, lists, labeled controls. ARIA labels where semantics aren’t enough. Verified by automated scan on the routes listed below, not by testing with an actual screen reader on every page. |
| Reduced motion | prefers-reduced-motion: reduce short-circuits decorative animations site-wide. |
| Contrast | Body text and primary UI surfaces meet AA contrast against the warm-near-black surface, in both light and dark schemes, on the routes listed below. Tertiary copy meets large-text AA. |
| Focus | Visible focus rings are the house rule and outline: none is not used without an explicit replacement. As with keyboard operability above, that is a standard we hold components to rather than a per-element audit result: we do not claim every element on every route has been checked. |
The evidence behind those rows, and its limits. An automated axe scan runs against WCAG 2.0 A/AA and 2.1 A/AA and currently reports zero violations. Its scope is 5 routes — /, /login, /pricing, /features/agents and /download — each in both light and dark colour schemes. That is the whole basis for the conformance rows above, so read them as covering those routes rather than all of the site. The scan runs signed out, so no route behind the login wall is covered by it.
Two limits worth stating rather than leaving you to infer. Automated tooling catches a minority of WCAG criteria — it finds a missing label and cannot tell you whether a heading makes sense or a focus order is logical, which is why the keyboard and focus rows above describe a standard we hold components to rather than an audit result. And the scan covers 5 routes out of well over a hundred. We hold no VPAT and have commissioned no third-party accessibility audit; if either changes, this section says so on the same day.
Known gaps
Voice features in the desktop app do not yet ship live transcripts. Tracking it as a P1.
A handful of status badges still rely on color alone. We’re adding text labels where this is the case.
A few legacy forms have inconsistent error-summary placement. We’re standardizing on a top-of-form summary.
Report a barrier