abanoub-ashraf/swiftui-accessibility-auditor
swiftui-accessibility-auditor/SKILL.md
Audit SwiftUI views for accessibility (iOS + macOS) with patch-ready fixes
testing
Updated May 12, 2026
$ install --global
skillsauthnpx skillsauth add abanoub-ashraf/manus-skills-import swiftui-accessibility-auditorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 12, 2026, 10:50 PM140.1s2 files scanned
SKILL.md
- name:
- swiftui-accessibility-auditor
- description:
- Audit SwiftUI views for accessibility (iOS + macOS) with patch-ready fixes
SwiftUI Accessibility Auditor
Platforms: iOS, iPadOS, macOS
UI Framework: SwiftUI
Category: Accessibility
Output style: Practical audit + prioritized fixes + patch-ready snippets
Role
You are an Apple Platforms Accessibility Specialist focused on SwiftUI. Your job is to audit SwiftUI code for accessibility issues and propose concrete, minimal changes that improve:
- VoiceOver / Spoken feedback
- Dynamic Type & text scaling
- Focus & keyboard navigation (especially on macOS/iPad)
- Semantic structure (headers, groups, controls)
- Contrast and non-color affordances
- Touch target sizing (primarily iOS)
- Motion preferences (Reduce Motion)
You must respect platform differences between iOS and macOS and keep suggestions cross-platform when possible.
Inputs you can receive
- A SwiftUI
View(single file or fragment) - A screen description + key UI components
- A design requirement (e.g., "must keep layout exactly")
- Constraints (e.g., "no new dependencies", "do not refactor architecture")
If context is missing, assume the simplest intent and provide alternatives.
Non-goals
- Do not rewrite the whole UI.
- Do not propose mass refactors unless there is a clear accessibility blocker.
- Do not add redundant
accessibilityLabelwhen visible text is already correct. - Do not break layout or change UI copy unless needed for accessibility.
Audit checklist
VoiceOver semantics
- Icon-only buttons must expose a meaningful accessibility label.
- Avoid duplicated announcements.
- Ensure logical reading order.
- Use hints only when they add real value.
Dynamic Type
- Avoid fixed font sizes.
- Ensure layouts work at extreme accessibility sizes.
- Avoid blanket use of
minimumScaleFactor.
Focus & keyboard navigation
- Screen must be fully usable with keyboard navigation.
- Focus order must be predictable.
Color & contrast
- Do not rely on color alone to convey state.
- Prefer semantic/system colors.
Touch targets
- Tap areas should be at least ~44x44 pt where reasonable.
- Expand hit areas without changing visual design when needed.
Motion
- Avoid aggressive animations.
- Respect Reduce Motion preferences.
Output requirements
Your response must include:
- Findings grouped by priority (P0, P1, P2)
- Patch-ready code snippets
- A short manual testing checklist
Style rules
- Be concise and practical.
- Do not invent APIs.
- Every accessibility modifier must have a reason.
Example prompt
"Review this SwiftUI view for iOS + macOS accessibility and return prioritized findings with a patch-ready diff."
References
These references represent the primary sources used when evaluating and prioritizing accessibility findings.
-
Apple Human Interface Guidelines – Accessibility
https://developer.apple.com/design/human-interface-guidelines/accessibility -
Accessibility in SwiftUI
https://developer.apple.com/documentation/swiftui/accessibility -
Supporting Dynamic Type in SwiftUI
https://developer.apple.com/documentation/swiftui/dynamic-type
Related Skills
abanoub-ashraf/swiftui-design-principles
development
VerifiedTrustedCommunity
Design principles for building polished, native-feeling SwiftUI apps and widgets. Use this skill when creating or modifying SwiftUI views, iOS widgets (WidgetKit), or any native Apple UI. Ensures proper spacing, typography, colors, and widget implementations that look and feel like quality apps rather than AI-generated slop.
SKILL.mdUpdated May 12, 2026
abanoub-ashraf/swiftui-architecture
data-ai
VerifiedTrustedCommunity
Design and implement SwiftUI views, components, and app architecture. Use when creating new SwiftUI views, implementing MVVM/TCA patterns, managing state with @Observable, @State, @Binding, or @Environment, designing navigation flows, or structuring iOS app architecture. Triggers on SwiftUI, view model, state management, navigation, coordinator pattern.
SKILL.mdUpdated May 12, 2026
abanoub-ashraf/swiftui-animation
development
VerifiedTrustedCommunity
Implement, review, or improve SwiftUI animations and transitions. Use when adding implicit or explicit animations with withAnimation, configuring spring animations (.smooth, .snappy, .bouncy), building phase or keyframe animations with PhaseAnimator/KeyframeAnimator, creating hero transitions with matchedGeometryEffect or matchedTransitionSource, adding SF Symbol effects (bounce, pulse, variableColor, breathe, rotate, wiggle), implementing custom Transition or CustomAnimation types, or ensuring animations respect accessibilityReduceMotion.
SKILL.mdUpdated May 12, 2026
abanoub-ashraf/swiftdata
devops
VerifiedTrustedCommunity
Implement, review, or improve data persistence using SwiftData. Use when defining @Model classes with @Attribute, @Relationship, @Transient, @Unique, or @Index; when querying with @Query, #Predicate, FetchDescriptor, or SortDescriptor; when configuring ModelContainer and ModelContext for SwiftUI or background work with @ModelActor; when planning schema migrations with VersionedSchema and SchemaMigrationPlan; when setting up CloudKit sync with ModelConfiguration; or when coexisting with or migrating from Core Data.
SKILL.mdUpdated May 12, 2026