Accessibility on Android : Some assembly required
summary
Shows concrete fixes: add contentDescription so “Toppings” reads “No toppings selected,” use a custom accessibility action to change the generic “double tap to activate” to double tap to select toppings, call announceForAccessibility after selection so TalkBack says “Pepperoni selected,” mark quantity controls with setImportantForAccessibility=NO to avoid needless focus, use setTraversalBefore/After for focus order, run TalkBack (or the open‑source TalkBack library) on KitKat and patch TTS when Play Storeless devices lack it.
AI-written summary · about
chapters (7)
- 0:00Introduction to accessibility
- 3:57Why accessibility matters
- 7:07Android accessibility tools
- 10:12Fixing default accessibility issues
- 16:59Testing and focus order
- 20:30Custom OS accessibility challenges
- 23:23User impact and conclusion
related talks
37mAccessibility on Android in 2019
45mAccessibility Talk, Button. Double-tap to activate.
35mAccessibility in Action
12mThe Secrets of Android Accessibility
32mMaking Android accessibility easy
48mAccessibility is not rocket science!
40mAccessibility on Android in 2019
33mDemystifying Android accessibility development
