By Usability & Accessibility team • A11y Consult Updated 11 May ‘26

Quick links

🔗 A11y Playground

🔗 DSS Catalog (Public facing)

🔗 WCAG 2.2 Quick Reference

🔗 Oobee web

🔗 WOGAA

🔗 WAI-ARIA Authoring Practices

<aside> 🤝🏻

Help us help you

We’d love to hear your thoughts on this accessibility playbook.

Your feedback will help us improve future editions and make the content more useful for everyone.

You may also reach us at [email protected].

</aside>

<aside> ℹ️

This playbook provides practical, component-based accessibility guidance that links with WCAG 2.2 success criteria. Each component includes Design, Development, and QA checklists, with DSS controls linked to detailed A11y Playground articles for further learning.

</aside>

<aside> 🚨

Top 20 Must-Fix Criteria — Mandatory for EMP2030

</aside>

How to use this playbook

🎨 If you're a Designer

1. Find the component you're designing in the Components gallery
2. Work through the Designer checklist before handoff
3. Cross-check Common pitfalls against your mockup
4. For research / discovery, see Usability testing with people with disabilities in Testing

💻 If you're a Developer

1. Open the component you're building
2. Tick off the Developer checklist as you implement
3. Run the QA checklist locally before opening a PR
4. Pair with the Keyboard and Screen reader testing guides

✅ If you're auditing or QA-ing

1. Start with Self-audit, zoom & reflow below
2. Layer on Keyboard then Screen reader tests
3. Use each component's QA checklist for a structured walk-through
4. Map findings back to WCAG + DSS using the property columns

Components

Filtered by category — open each component to see its checklist, WCAG mapping, and DSS section.

<aside> 💡

Why more than the Top 20? This playbook intentionally goes beyond the 20 Oobee-checkable criteria. Roughly 60–70% of accessibility issues require manual testing — keyboard sweeps, screen reader walk-throughs, and usability research with people with disabilities. The components and testing guides cover both halves.

</aside>

Components

🌐 Applies to every page

Guidance that applies across all components, not specific components.

Plain language & cognitive accessibility

Reduced motion & animation

Focus management in SPAs

Touch & mobile accessibility

Forced colours & high contrast mode

✅ Testing & QA

Four ways to verify accessibility — pick the one that matches your role and stage.

Testing guide

📋 WCAG 2.2 reference

New and changed success criteria in WCAG 2.2, with actionable implementation patterns for designers and developers.

WCAG 2.2 new criteria — implementation guide

🔄 Workflow & process

How to embed accessibility into your sprint — handoff annotations, acceptance criteria, severity classification, and CI/CD.

Accessibility workflow & process