Accessibility @ Scale
summary
Companies discover that accessibility isn’t impossible to add later: one audit takes about one workday and finds most low-hanging fixes; Android tools used are TalkBack and the built‑in accessibility scanner. Key numbers: 1 in 5 people (20%) have a disability, >50 million in the US, 8.1M vision impaired, 19.9M with lifting/grasping difficulty. Concrete actions: add content descriptions, enforce 48x48 touch targets, run linters, write Espresso accessibility tests, and create a virtual view hierarchy for custom controls.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:32Meet Amy
- 2:47Statistics
- 6:30Visual impairments
- 7:17Visual apps
- 8:48User Testing
- 10:26Timeline
- 11:58Audit
- 12:45Talkback
- 14:38Text Scaling
- 15:43Zooming in
- 16:11Display Size Increase
- 16:55Accessibility Scanner
- 18:31Adding Labels
- 22:37Priorities
- 22:49Most important fixes
- 24:39Best thing to do
- 25:12Likely problems
- 25:40Virtual view hierarchy
- 26:11Custom class
- 27:14Working with designers
- 30:10Building support
- 33:11Solving problems
- 33:47Questions
related talks
43mAccessibility Made Simple
39mEasy Android Accessibility
37mAndroid accessibility made easy
34mIs your app for everyone? A primer on accessibility for Android
36mRaise accessibility awareness at work as an Android developer
12mAccessibility-First Development: Making Applications Inclusive from Day One
48mDevelopment for all the people
48mAccessibility is not rocket science!