Our commitment
Trainwork should be usable by everyone on a team, including people who navigate by keyboard, use a screen reader, or need reduced motion. We build toward the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.
Where we are
We are candid about our current state: Trainwork has not yet completed a full third-party WCAG 2.1 AA audit, and we do not claim conformance we have not tested. What is in place today, verified in the code rather than intended:
- A skip-to-content link on every page, public and signed in, with a main landmark on each surface to skip to
- A visible keyboard focus indicator on every interactive element, measured at 5.45:1 against the page background
- Form fields programmatically associated with their labels on the sign-in, checkout, contact, and settings flows, so a screen reader announces what each field is for
- Reduced-motion preferences honored across the whole product, not per component: if your system asks for less motion, animation stops everywhere
- AI responses announced to screen readers when they arrive, in both the practice conversation and the AI Tutor
- Completion certificates carry a document title and language, so a screen reader reads the certificate rather than the filename
- Text-based learning throughout: the core product is written conversation, with no audio- or video-only content
Known gaps we are working through, stated plainly: no independent audit has been performed, so nothing here is third-party verified. A full color-contrast pass of the learner app is not finished. Completion certificates are readable text but are not tagged PDFs, so reading order comes from the text layer rather than from document structure. Our admin console has not been audited, since only we use it.
A formal audit and an accessibility conformance report (VPAT) are planned. Schools and districts that need one sooner should contact us and we will scope it around your timeline.
Tell us what is in your way
If any part of Trainwork is difficult or impossible for you to use, email admin@trainwork.org with the page and what happened. Accessibility reports go to the top of the queue: we respond within one business day and treat blockers as bugs, not feature requests.