Android for Everyone: Accessibility in Android
summary
Practical guide to making Android apps accessible with concrete fixes and tools: run Accessibility Scanner and UI Automator Viewer to find issues (scanner flags touch targets under 48dp, contrast failures, missing content descriptions), add minHeight/minWidth or padding to meet the 48dp target, and use Espresso accessibility checks in UI tests. Compare XML vs Jetpack Compose semantics: Compose exposes contentDescription, semantics modifiers, liveRegion and mergeDescendants so fewer scanner warnings appear; Material buttons default to 48dp while Compose Button defaults to 36dp. Also cites WCAG 2.1 ratios (4.5:1) and the business case: about one in four people worldwide.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 1:59The importance of inclusivity
- 3:40Why accessibility matters
- 7:07Understanding disabilities
- 10:08Accessibility guidelines
- 14:44Testing accessibility
- 22:54Technical implementation
- 46:45Advanced accessibility tips
- 50:22Q&A session
related talks
48mAndroid for Everyone: Accessibility in Android
13mDesigning for accessibility in Android Studio and Jetpack Compose
32mMaking Android accessibility easy
15mWhat's new in Accessibility for developers
34mIs your app for everyone? A primer on accessibility for Android
15mWhat's new in Accessibility for developers
39mEasy Android Accessibility
22mA Structured Guide to Accessibility on Android