Android for Everyone: Accessibility in Android
summary
Jetpack Compose and legacy XML comparisons land on concrete takeaways: the Accessibility Scanner works with Compose and flags missing labels, contrast and small targets; touch targets should be 48×48 touch targets not inferred sizes; color contrast aims for 4.5:1 (AA) or 3:1 for large text; semantics modifiers and contentDescription map accessibility into Compose; use TTS span for digits to fix spoken numbers; and run automated accessibility checks in Espresso/Robolectric while also doing manual and user testing.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 7:24Accessibility matters in Android
- 12:06Disabilities and tools
- 15:36Testing apps for accessibility
- 18:50Touch target size issues
- 23:50Color contrast in your app
- 25:15Labels and descriptions
- 32:33Jetpack Compose vs XML
- 37:12Grouping elements for screen readers
- 40:00Text scaling and dark mode
- 41:03Custom views and APIs
- 42:51Media controls and subtitles
- 43:12Automated accessibility testing
- 45:19Resources and next steps
related talks
01h 01mAndroid 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
15mWhat's new in Accessibility for developers
39mEasy Android Accessibility
34mIs your app for everyone? A primer on accessibility for Android
37mAccessibility on Android in 2019