WCAG 2.2 Handbook
Chapter 05
Guidance for Engineering
Engineering is not this handbook's strong suit — so here is the best external resource for your engineering counterparts.
This handbook covers the design side of WCAG 2.2. But engineers have their own set of responsibilities in making the world more accessible. Fortunately, there's an excellent free resource built specifically for them.
The Recommended Resource
Authors Jaan Jaap de Groot and Paul van Workum have published code snippets for each WCAG guideline — covering iOS, Android, Flutter, React Native, and the web — to bring each criterion to life in real code.
appt.org/en/guidelines/wcag — Free, comprehensive, and available to everyone. It's the best engineering implementation guide for WCAG that exists.
What It Covers
- Code snippets for every WCAG success criterion
- iOS (Swift / SwiftUI), Android (Kotlin / Jetpack Compose), Flutter, React Native, and Web
- Practical examples showing how to implement each guideline
- Community contributions — if you've solved a guideline for a specific technology, you can contribute your solution back
Designer ↔ Engineer Handoff Tips
When handing off accessible designs, be explicit about:
- Accessible names — specify what screen readers should announce for every interactive element
- Roles and states — define the ARIA role, expanded/collapsed states, selected states for custom components
- Focus order — annotate the intended keyboard tab sequence on complex layouts
- Error states — provide designs for every error condition, not just the happy path