Unpacking Compose Multiplatform Accessibility
summary
Compose Multiplatform exposes the same semantics APIs as Android Compose so accessibility largely matches native Compose — roughly 99% parity — but iOS support is still beta and requires a Mac to build and test. Use accessibilitySyncOptions.always to keep the iOS accessibility tree updated on simulators; rely on contentDescription, mergeDescendants, headings, roles, stateDescription and custom actions for images, grouped controls and swipe behaviors. Known issues include incorrect focus order tracked in JetBrains’ issue tracker.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:53What is composed multiplatform
- 2:20Accessibility
- 3:13iOS Accessibility
- 6:47App Scoped Features
- 7:14Font scaling
- 9:13Color contrast
- 10:06Element Scope
- 10:36Content Descriptions
- 10:59Images
- 12:23Merge Descendants
- 14:30Custom Actions
- 17:40Heading
- 19:32Role
- 21:23State Description
- 22:47Summary
- 25:17Questions
related talks
24mUnpacking Compose Multiplatform Accessibility
48mAndroid for Everyone: Accessibility in Android
43mBuilding Accessible Apps with Jetpack Compose
13mBuilding accessibility support for Compose
44mAccessibility with Compose : Experimentation & Live coding
01h 01mAndroid for Everyone: Accessibility in Android
13mDesigning for accessibility in Android Studio and Jetpack Compose
15mWhat's new in Accessibility for developers