How to Get Accessibility Training for Teams Right
Teaching designers, developers, editors and testers what accessibility means for their own work.
Marcus Adeyemi
Why does it matter?
Accessibility fails when it is one specialist's job, and training spreads responsibility to where decisions are made.
What are the numbers?
- Role-specific editors, designers and developers need different training
- Practical hands-on exercises work better than policy overviews
- Ongoing one-off sessions fade
- Standards teams need to know which standard applies
What should I do?
- Train each role on its own responsibilities
- Use real examples from your own product
- Include assistive technology demonstrations
- Refresh training regularly
- Give teams a place to ask questions
What should I avoid?
Avoid:
- One generic session for everyone
- Training with no practical exercises
- Policy-only training
- Expecting one specialist to fix everything
When should I get help?
Short answer Bring in help when accessibility issues keep reappearing.
Where this comes from
- W3C Web Accessibility Initiative — Planning and managing web accessibility
- Deque University — Accessibility training
The figures and practices above come from the sources listed.
Working on something like this?
We take on Performance & Accessibility work for teams who want it done once, properly. Tell us what you are building and we will tell you honestly whether we are the right studio for it. Start a project.
Where to go next
Spotted something wrong? Report an error on this page. We correct on the page and say what changed.
