Driving inclusive design at your company
summary
At Monzo a small group pushes inclusive design across ~15–20 Android engineers split into ~10–20 teams by using an accessibility Slack channel for escalations and updates, targeted workshops (ideal size 4–6), paired one‑to‑ones to land cross‑discipline fixes, and measurement. Example: baseline funnel shows 76% → 53% but TalkBack users drop to 21%, prompting a form redesign; a company experiment asked ~1,000 people to turn on large text for a week and collected screenshots to find common fixes.
AI-written summary · about
chapters (14)
- 0:00Introduction and background
- 1:31Starting inclusive design at scale
- 2:54Using Slack for accessibility feedback
- 4:58Avoiding an inactive accessibility channel
- 6:01One-to-ones for buy-in
- 7:45Cross-team collaboration on inclusive design
- 8:49Analyzing user data for accessibility gaps
- 10:13Tailoring presentations for engagement
- 10:54Running screen reader workshops
- 13:23Android team accessibility workshop
- 14:29Promoting accessibility at all-hands meetings
- 15:33Encouraging large text usage company-wide
- 16:57Key takeaways and next steps
- 18:01Closing and call for feedback
related talks
45mDigital Accessibility and Knowing When to Flex
36mRaise accessibility awareness at work as an Android developer
20mInclusive design as the new norm
29mClose Encounters of an Inclusive Design: A Case Study Introducing IDX into One Compan...
32mDesigning for Accessibility
42mAccessibility @ Scale
38mYes You Can! Improving Accessibility
43mBuilding a Design Culture for Inclusivity