Unpacking Compose Multiplatform Accessibility
summary
Compose Multiplatform draws Android UI with regular Compose and iOS UI by rendering with SKO to a canvas, giving identical pixels but adding interop and accessibility complexity. Compose semantics nodes map to platform nodes so labels, hints and traits become accessibility info on each OS; that mapping is lazy unless an assistive technology is present. UI interop defaults to nativeAccessibilityEnabled false by default so native view accessibility is ignored unless flipped, and the iOS simulator needs the accessibility sync options flag for live inspector/testing. Automated checks work with Accessibility Scanner, TalkBack, VoiceOver, Espresso accessibility checks, Paparazzi extension and performAccessibilityAudit.
AI-written summary · about
chapters (14)
- 0:00Compose Multiplatform accessibility intro
- 1:06What is Compose Multiplatform
- 3:09UI on Android in Compose
- 4:54UI on iOS in Compose
- 7:44iOS UI interoperability in Compose
- 9:09Why accessibility matters
- 10:13Android accessibility tree
- 12:25iOS accessibility mapping
- 14:08iOS accessibility in Compose
- 16:15Native iOS UI accessibility
- 17:59Testing Android accessibility
- 20:06Testing iOS accessibility
- 21:51Automated iOS accessibility testing
- 23:18Resources for Compose Multiplatform
related talks
29mUnpacking Compose Multiplatform Accessibility
13mBuilding accessibility support for Compose
13mDesigning for accessibility in Android Studio and Jetpack Compose
43mBuilding Accessible Apps with Jetpack Compose
48mAndroid for Everyone: Accessibility in Android
44mAccessibility with Compose : Experimentation & Live coding
01h 01mAndroid for Everyone: Accessibility in Android
37mDeep-Dive Into Mobile Accessibility & Interactive Quiz