Accessibility is not rocket science!
summary
A practical Android talk demonstrating that a single developer change can fix many accessibility problems, backed by statistics (about 1 in 5 people affected, ~2 million visually impaired in France, <10% of sites accessible). It shows a broken shopping app and applies Android accessibility techniques—TalkBack attributes (contentDescription, stateDescription, clickLabel), merged Compose semantics, Coil image fixes, AccessibilityManager checks, and adding an extra FAB—with live coding and onstage testing to show what works and what still causes issues.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:18What is digital accessibility?
- 5:11Most common visual impairments
- 7:051,700,000 people with visual impairments
- 8:30Swipe right or left to
- 9:25Double-tap to activate
- 9:58Single-tap to move focus to an element
- 20:17When to use contentDescription?
- 28:05Just because it's text doesn't mean it's accessible
- 34:41Grouping components to simplify navigation
- 41:34Different states of the Quantity Selector
- 46:46To go further
related talks
35mAccessibility in Action
43mAccessibility Made Simple
34mIs your app for everyone? A primer on accessibility for Android
37mAccessibility on Android in 2019
22mAndroid Accessibility: Understanding Blind Users to Meet Their Needs
24mBenefits of Making Your Apps Accessible
12mThe Secrets of Android Accessibility
39mEasy Android Accessibility