IOS Accessibility
Build and audit SwiftUI, UIKit, and AppKit accessibility for VoiceOver, Voice Control...
Install
npx skills add dpearson2699/swift-ios-skills --skill ios-accessibility -g -a claude-code -y- Repository
- dpearson2699/swift-ios-skills1.3k
- Category
- Design
- Updated
- 3mo ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Build and audit SwiftUI, UIKit, and AppKit accessibility for VoiceOver, Voice Control, Switch Control, Full Keyboard Access, Dynamic Type, focus restoration, labels/traits/actions, traversal, custom rotors, NSAccessibility, XCTest checks, adaptive system preferences, and App Store accessibility declarations. Use when implementing accessible UI, fixing an accessibility audit, testing assistive-technology behavior, or substantiating App Store Accessibility Nutrition Labels.
iOS/macOS Accessibility - SwiftUI, UIKit, and AppKit
Build SwiftUI, UIKit, and AppKit interfaces that remain operable with VoiceOver, Switch Control, Voice Control, Full Keyboard Access, and adaptive accessibility settings.
Contents
- Core Principles
- How VoiceOver Reads Elements
- SwiftUI Accessibility Modifiers
- Focus Management
- Dynamic Type
- Custom Rotors
- System Accessibility Preferences
- Decorative Content
- Voice Control
- Switch Control
- Full Keyboard Access
- Assistive Access (iOS 18+)
- UIKit Accessibility Patterns
- AppKit Accessibility Patterns
- Accessibility Custom Content
- App Store Accessibility Nutrition Labels
- Testing Accessibility
- Common Mistakes
- Review Checklist
- References
Core Principles
- Prefer semantic system controls; custom controls must expose the same name, role, value, state, and actions.
- Preserve every task across assistive input: do not make a gesture, color, motion, hover state, or visual arrangement the only path to meaning or action.
- Keep focus and traversal intentional across navigation, presentation, updates, and dismissal.
- Let text, layout, contrast, transparency, and motion adapt to the user's accessibility settings.
- Treat App Store accessibility declarations as evidence-backed product claims, not as a summary of isolated control-level support.
How VoiceOver Reads Elements
VoiceOver reads element properties in a fixed, non-configurable order:
