Optimize the Text-To-Speech experience for blind users
summary
With TalkBack on Android the practical fixes are: add semantic headings so users can jump by section, use semantics modifier and set heading, mark errors with a content description or semantic error flag, add explicit clickLabel text for actions, use liveRegion=Polite to announce dynamic messages (verification SMS shows up), merge label+value with mergeDescendants but fix clickable cards with clearAndSetSemantics, and use buildAnnotatedString verbatim annotations to force character‑by‑character TTS for ZIPs and IBANs; fixes work but behaviour varies by TalkBack version.
AI-written summary · about
chapters (14)
- 0:00TalkBack accessibility intro
- 1:48First profile screen
- 3:12How TalkBack works
- 5:04Semantic headings
- 6:30Clearer error messages
- 8:16Content descriptions for context
- 9:18Click labels for actions
- 10:42Live regions for UI changes
- 12:31Merged label-value semantics
- 14:18Semantic conflicts fix
- 16:26Semantics overrides
- 17:31Reading addresses
- 18:14TalkBack quirks
- 19:00Final accessible profile
related talks
19mCreating Narratives: Shaping TalkBack with Compose Semantics
12mThe Secrets of Android Accessibility
13mWhat's new in Android Accessibility
34mDeep Dive into Compose Semantics
15mWhat's new in Android accessibility - American Sign Language
37mAccessibility on Android in 2019
15mWhat's new in Android accessibility
35mAccessibility in Action