The Scenario
A 40-person product team (PMs, designers, developers, QA) has been ignoring accessibility for 3 years. The CEO just received a complaint from a visually impaired user. She wants an accessibility strategy — not just a checklist, but a cultural shift.
The Brief
Write a comprehensive accessibility strategy that embeds a11y into every phase of the product development lifecycle. Cover standards, tooling, testing, and team education.
Deliverables
- Standards adoption: which WCAG level to target (AA vs AAA) and which success criteria to prioritise
- Tooling integration: automated tools (axe, Lighthouse), design plugins (Stark), and CI/CD integration
- Testing cadence: when to test (design review, dev PR, QA, post-deploy) and who is responsible at each stage
- Team education plan: how to train designers, developers, and QA on accessibility fundamentals
Submission Guidance
Accessibility is not a QA gate at the end. It starts in design (colour contrast, focus states) and continues through development (semantic HTML, ARIA) and testing (screen reader, keyboard).
Submit Your Work
Your submission is graded against the rubric on the right. If you pass, you get a public Badge URL you can share on LinkedIn. There is no draft save, so work offline first and paste your finished response here.