What's new in Accessibility for developers
summary
Android Studio adds built‑in accessibility checks driven by the Accessibility Test Framework (same checks as Accessibility Scanner and Espresso), flagging missing content descriptions, insufficient 48x48dp minimum touch target sizes, and poor contrast; currently those checks run for view‑based layouts only. Android T exposes a global preference and the isAudioDescriptionRequested API so apps can honor audio description tracks by default. Jetpack Compose sets touch targets and requires contentDescription for images, uses a parallel semantics tree with node merging via mergeDescendants, and shows semantics in Layout Inspector (Bumblebee).
AI-written summary · about
chapters (8)
- 0:00Introduction to accessibility
- 0:37Android Studio tool updates
- 1:43Audio description API
- 2:46Compose touch targets
- 5:23Adding accessibility info
- 6:44Semantics tree explained
- 9:29Merging and clearing semantics
- 14:06Testing and conclusion
related talks
13mDesigning for accessibility in Android Studio and Jetpack Compose
01h 01mAndroid for Everyone: Accessibility in Android
48mAndroid for Everyone: Accessibility in Android
37mAccessibility on Android in 2019
32mMaking Android accessibility easy
40mAccessibility on Android in 2019
33mDemystifying Android accessibility development
12mThe Secrets of Android Accessibility
