Accessibility with Compose : Experimentation & Live coding
summary
Live coding shows an actual shopping app built in Jetpack Compose with accessibility problems and then fixed: missing contentDescription on images, confusing split price text, unreachable FAB when TalkBack is enabled, and no feedback after changing quantity — a volunteer struggles to add five packs of spaghetti. Fixes use TalkBack heuristics plus Compose APIs: set meaningful labels, use modifier.semantics to merge descendants, expose stateDescription for quantity and detect accessibility to reposition primary actions; the app becomes navigable with far fewer swipes.
AI-written summary · about
chapters (11)
- 0:00Accessibility with Compose intro
- 1:26Disability focus
- 6:26Live TalkBack demo
- 15:40Accessibility issues found
- 17:31Fixing image descriptions
- 24:11Text and ratings accessibility
- 27:06Semantics modifier
- 31:29Grouping elements
- 34:02FAB accessibility fix
- 38:00State feedback for quantity
- 42:17Best practices recap
related talks
43mBuilding Accessible Apps with Jetpack Compose
48mAccessibility is not rocket science!
13mDesigning for accessibility in Android Studio and Jetpack Compose
34mDeep Dive into Compose Semantics
42mBuilding Compose Apps for everyone
35mAccessibility in Action
33mBuild adaptive apps with Jetpack Compose
18mCompose: Implementing responsive UI for larger screens