Training in this field usually fails in the same way: a day of standards, a certificate, and a team that goes back to shipping the same components. What works is smaller and more specific, aimed at the four roles that make the decisions, and it ends with something in the codebase rather than in a slide deck. This page is what to ask for, and what web accessibility best practices look like once the trainer has gone.
Train the four roles differently
Designers need the palette, states, colour-alone rule and reflow. Developers need semantics, keyboard, focus management and ARIA restraint. Content editors need alt text, headings and link text, and they need it inside the CMS they use. QA needs the keyboard and screen reader passes. One session covering all four teaches everybody a quarter of what they needed.
End with artefacts, not certificates
A conformant component in the library, a CMS field made required, a scanner in the pipeline, and a written definition of done that includes the keyboard pass. Those four outlive any training day, and they are the difference between a site that stays fixed and one that regrows 401 issues over two years.
The practices that hold
Run the scanner on every pull request for the templates. Keyboard-test every new component before merge. Review alt text in the content review, not afterwards. Re-audit annually and after every redesign. That is the whole programme, and it costs less each year than the audit it prevents.
Questions people ask about ada compliance training
How long should training be?
Half a day per role, done separately, beats a full day for everybody together.
Do certificates matter?
To procurement occasionally, to the site never. What matters is what changed in the codebase afterwards.
Who should own accessibility afterwards?
One named person with time allocated, and the component library as their first responsibility.