Most accessibility training fails because it teaches the standard rather than the work. A developer who has sat through a WCAG 2.1 overview can recite the four principles. That same developer will still build an inaccessible modal when they get back to their desk, because nobody showed them what a properly implemented focus trap looks like in their stack.
Here is what workshops that actually change how teams build look like — and what generic ones get wrong.
What most accessibility training gets wrong
Generic training covers the what: what WCAG is, what the four principles mean, what screen readers are used by disabled people. It rarely covers the how: how to implement a skip link in your specific framework, how to write ARIA labels that make sense to screen reader users, how to structure error messages so they are announced correctly.
The other problem is audience. A half-day WCAG overview aimed at developers, designers, and product managers simultaneously tends to go too deep for some and not deep enough for others. Role-specific training lands better.
What developer-focused WCAG training covers
A developer-specific accessibility workshop covers the practical implementation patterns that come up most often:
- Semantic HTML: when a button is a button, and when a div is never acceptable as a button
- Focus management: skip links, modals, single-page application route changes
- ARIA: when to use it, what attributes are commonly misused, and the first rule of ARIA
- Form patterns: input association, error announcement, fieldset and legend usage
- Dynamic content: aria-live regions, loading states, async updates
- Testing workflow: how to use NVDA and VoiceOver for quick manual checks alongside automated tooling
Workshops are run against real code where possible: your component library, your design system, or representative examples from your product.
What designer-focused WCAG training covers
A designer-specific workshop covers the decisions made in design that cause accessibility failures in production:
- Colour contrast: checking ratios, designing within accessible palettes, handling brand colour challenges
- Focus indicators: why they matter, GOV.UK and WCAG 2.2 focus requirements
- Touch target sizing: minimum sizes, spacing between targets
- Typography: accessible body sizes, line length, spacing
- Error states and form design: how to communicate errors clearly to all users
- Annotation practice: how to hand off accessible intent to developers
Formats available
Workshops can be run remotely or in person, half-day or full-day, and can include follow-up review sessions where I look at work your team produces after the training. That feedback loop is what makes training stick.