kotlin-multiplatform-accessibility

When to Use This Skill

Use when:

• A screen must be navigable by TalkBack (Android) or VoiceOver (iOS)
• Interactive elements (buttons, links, custom composables) need meaningful labels
• Touch targets need to meet the 48×48dp minimum size requirement
• Adding accessibility snapshot tests alongside visual screenshots
• An existing screen is failing an a11y audit

Trigger keywords: accessibility, a11y, TalkBack, VoiceOver, contentDescription, semantics, screen reader, semantic role, mergeDescendants, touch target, WCAG, accessibility test, Roborazzi a11y, traversal order, live region, role = button, accessibility label, semantic tree, accessible, screen reader support, accessible app, a11y compliance, accessibility audit, accessible design, make accessible.