Building Compose Apps for everyone
summary
15% of the world’s population has some form of disability and Jetpack Compose reduces friction but requires specific semantic work: use the semantics tree to expose meaning, set contentDescription & clickLabel for images and actions, prefer IconButton/TextButton or enforce a minimum touch area (use sizing and padding) to meet the 40dp touch target guideline, use mergeDescendants to compress multiple nodes into one focusable item, provide textSemantics and stateDescription for correct spoken output.
AI-written summary · about
chapters (14)
- 0:00Introduction and welcome
- 3:59Why accessibility matters
- 6:27Semantics in Jetpack Compose
- 11:20Touch targets and sizing
- 15:34Content descriptions for icons
- 18:22Click labels for actions
- 21:09Text semantics for clarity
- 24:17Merging descendants in UI
- 27:31State descriptions for toggles
- 29:41Toggle component accessibility
- 33:13Accessibility actions for multiple tasks
- 36:01Using headings for navigation
- 38:29Custom composables and semantics
- 40:33Testing with TalkBack and resources
related talks
43mBuilding Accessible Apps with Jetpack Compose
13mBuilding accessibility support for Compose
38mDesigning scalable Compose APIs
44mAccessibility with Compose : Experimentation & Live coding
01h 01mAndroid for Everyone: Accessibility in Android
48mAndroid for Everyone: Accessibility in Android
41mCompose beyond Material
13mDesigning for accessibility in Android Studio and Jetpack Compose