← ClaudeAtlas

ios-accessibility-skilllisted

Use when iOS or iPadOS accessibility design, implementation, review, or testing involves VoiceOver, Voice Control, Switch Control, Full Keyboard Access, Dynamic Type, contrast, motion, focus, media alternatives, or Assistive Access. Do not use for generic visual styling or platform-neutral UI work with no accessibility requirement.
fal3/claude-skills-collection · ★ 18 · AI & Automation · score 79
Install: claude install-skill fal3/claude-skills-collection
# iOS Accessibility Skill Treat accessibility as part of the product contract, not a modifier pass at the end. Preserve the semantics of native controls, support user settings, and verify behavior with the actual assistive technologies in scope. ## Baseline and availability Core guidance applies broadly. Copy-ready examples use Xcode 15, Swift 5.9, and iOS/iPadOS 17. - Assistive Access exists as a system experience on iOS/iPadOS 17. - `accessibilityAssistiveAccessEnabled` is available from iOS/iPadOS 18. - The SwiftUI `AssistiveAccess` scene and `assistiveAccessNavigationIcon` are stable Xcode 26 APIs requiring iOS/iPadOS 26. - OS 27-cycle material is beta relative to stable Xcode 26.6. Include it only on explicit request, label it beta, and gate it. Always check the user's deployment target before emitting newer API code. ## Audit order 1. Identify essential tasks, content, and destructive actions. 2. Inspect the accessibility tree: roles, labels, values, hints, ordering, grouping, and hidden decoration. 3. Exercise VoiceOver, Voice Control, Switch Control, and Full Keyboard Access as relevant. 4. Test every Dynamic Type size, including accessibility categories. 5. Test Increase Contrast, Reduce Motion, Reduce Transparency, Differentiate Without Color, Bold Text, and button shapes. 6. Verify localization, right-to-left layouts, captions/transcripts, and audio descriptions where applicable. 7. Run Accessibility Inspector, then test on device and with disabled users whe