The cheapest accessibility issue is the one your team never ships. After remediating the same patterns across hundreds of pages — unlabelled icon buttons, focus traps in modals, ARIA copied from the wrong Stack Overflow answer — we built training that targets exactly what developers and content teams get wrong in practice.
What the training covers
- For developers: semantic HTML before ARIA, the five ARIA attributes that cover 90% of real needs, focus management in SPAs (React patterns included), and how to test your own work with a keyboard and a screen reader in under ten minutes.
- For designers: colour contrast that passes WCAG 2.2 without killing the brand, focus states worth shipping, and how to annotate designs so accessibility survives handoff.
- For content teams: alt text that actually helps, heading structure, link text, and accessible documents.
- For QA: building WCAG checks into your test plan, what automated tools catch and what they miss, and screen reader basics with NVDA and VoiceOver.
How it runs
Live and remote, in half-day blocks, on your codebase wherever possible — we would rather fix your real components together than walk through slide-deck examples. Sessions are recorded for your internal wiki, and every attendee gets a checklist they can use the next morning.
Hands-on, opinionated, and specific to your stack. Ask about a session for your team.
Frequently Asked Questions
Who is the training for?
Developers, designers, content editors and QA - each track is tailored. Mixed-team sessions work well for smaller companies; larger teams usually book separate developer and design sessions.
Is it remote or on-site?
Remote by default, run live (not pre-recorded). Sessions are recorded so you can keep them on your internal wiki.
Do you train on our actual codebase?
Yes, wherever possible - fixing your real components together teaches more than any slide deck. We sign NDAs as needed.
