Easy Android Accessibility
summary
Accessibility work pays off: Android accessibility reaches over a billion people (about 1 in 7) and ~200–250 million with visual impairment, so make apps usable early. The demo counter app yields five Scanner issues: contrast 3.86 (needs 4.5), unlabeled image buttons, and 24×24 dp touch targets (aim for 48×48 dp or larger hit areas). Use Accessibility Scanner for quick audits, the Accessibility Test Framework with Espresso or Robolectric for one-line automated checks, and the Play Console pre-launch report to catch problems before release.
AI-written summary · about
chapters (14)
- 0:00Introduction to accessibility
- 1:18What is accessibility
- 5:56Accessibility services overview
- 8:02Standard views and APIs
- 13:34Common accessibility problems
- 15:43Accessibility Scanner tool
- 18:56Fixing contrast and labels
- 20:44Pre-launch reports
- 22:33Automated testing with ATF
- 28:11Manual testing with services
- 34:15User testing strategies
- 35:59Key takeaways summary
- 36:41When to implement accessibility
- 38:53Q&A and closing
related talks
34mIs your app for everyone? A primer on accessibility for Android
42mAccessibility @ Scale
01h 01mAndroid for Everyone: Accessibility in Android
48mAndroid for Everyone: Accessibility in Android
32mMaking Android accessibility easy
43mAccessibility Made Simple
41mMake 2021 the Year You Tackle Accessibility
38mYes You Can! Improving Accessibility