It's All About Focus - and Accessibility
summary
Explains that Android has two distinct focuses—input/keyboard focus and accessibility/screen‑reader focus—and shows Compose fixes: use clickable/selectable/focusable correctly, create a FocusRequester + focusRequester modifier (order matters) to move keyboard focus, use semantics { focused = … } with a launchedEffect toggle to move accessibility focus, change traversal with focusProperties / semantics(isTraversalGroup=true, traversalIndex), and meet WCAG: visible focus requires a ≥2px indicator and ≥3:1 contrast — example: onFocusChanged + border(2.dp, color) and optional padding.
AI-written summary · about
chapters (9)
- 0:00Focus and accessibility
- 1:25Introduction
- 2:27Focus on Android
- 9:16Controlling focus
- 13:30Focusable components
- 13:50Moving focus
- 19:18Traversal order
- 25:31Visible focus
- 35:09Summary
related talks
38mHandling focus in 2024: supporting different navigation ways with Compose
36mNavigation focus in 2024: Supporting keyboard navigation with Compose
46mFocusing on Focus
39mManaging Focus for Accessible Digital Applications: From the Essential to the Unnecessary
25mStuck in a Focustrap: Mastering Keyboard Accessibility
12mThe Secrets of Android Accessibility
40mAccessibility on Android in 2019
38mStuck in a Focus Trap