Accessibility at Google: Lessons Learned
summary
Ten years of concrete choices: Google builds a hub-and-spoke model with centralized standards launched December 2013 and education in Noogler orientation, adds an Android Accessibility Scanner, integrates accessibility checks into the Play Store pre-launch report, and runs a trusted tester program with several hundred participants since 2017 for early feedback. Product areas adopt launch requirements and executive sponsors, tooling and linting catch regressions, and measurement plus testing-on-demand show steady, incremental improvements rather than a single mandate.
AI-written summary · about
chapters (21)
- 0:00Introduction and journey
- 3:58First accessibility failure
- 5:29Systematic company-wide approach
- 7:40Hub and spoke model
- 9:10Education and training programs
- 11:42Internal standards creation
- 15:51Standards adoption and growth
- 18:12Incremental progress lessons
- 20:01Tooling and workflow integration
- 21:49Maintaining relationships
- 23:16Building with users
- 25:45Accessibility champs program
- 26:50Measuring usability
- 28:13Material design integration
- 29:38Employee experience focus
- 32:11Executive sponsorship
- 34:06Scaling accessibility teams
- 36:42Hub functions summary
- 39:41Key learnings and advice
- 41:34Personal reflections
- 43:00Q&A session
related talks
34mIs your app for everyone? A primer on accessibility for Android
21mGetting started with accessibility and product inclusion
42mAccessibility @ Scale
22mBill and Ted’s accessibility adventure: Accessibility testing for developers
36mRaise accessibility awareness at work as an Android developer
43mAccessibility Made Simple
41mMake 2021 the Year You Tackle Accessibility
48mAccessibility is not rocket science!