swiftui-wcag-accessibility-auditor
by ramzesenokswiftui-wcag-accessibility-auditor audits SwiftUI iOS feature code for WCAG 2.2 Level A/AA and WCAG2Mobile, then returns patch-ready fixes with evidence, priorities, and user-verification checks for code-indeterminate behavior. Use it for auth, forms, settings, custom controls, and pre-merge UX audit work.
This skill scores 84/100, which means it is a solid listing candidate for directory users who need a code-only SwiftUI accessibility audit with WCAG 2.2 traceability and patch-ready remediation. The repository gives enough operational detail to understand when to use it, how to run it, and what output to expect, so install decisions can be made with confidence even though there is no install command or executable automation.
- Strong triggerability: the frontmatter clearly targets SwiftUI iOS feature audits and specifies use cases like auth, forms, settings, and custom controls.
- Operational workflow is explicit: it says to read a defined sequence of reference files, use a code-only audit process, and return prioritized Markdown findings with user-verification checks when code is insufficient.
- Good agent leverage: bundled references cover workflow, checklist, API examples, manual follow-up checks, and a patch-ready remediation guide, reducing guesswork for both detection and fixes.
- No install command or scripts are provided, so adoption depends on manually following SKILL.md and the reference files rather than invoking automation.
- The skill is intentionally code-only and will not validate live behavior, screen-reader output, or visual measurements; some findings will remain 'Needs user verification'.
Overview of swiftui-wcag-accessibility-auditor skill
What this skill does
The swiftui-wcag-accessibility-auditor skill audits SwiftUI iOS feature code for accessibility against WCAG 2.2 Level A/AA and WCAG2Mobile interpretation, then returns patch-ready fixes in a concise, priority-based format. It is designed for source review, not runtime testing, so it helps you catch likely blockers, trace evidence, and flag anything that needs user verification instead of guessing.
Who should use it
Use the swiftui-wcag-accessibility-auditor skill when you need a SwiftUI accessibility pass on screens like auth, forms, settings, lists, custom controls, or modal flows. It is a strong fit for teams doing pre-merge UX audit work, remediation planning, or reviewing app code for accessibility regressions.
What makes it different
Unlike a generic prompt, this skill centers on WCAG traceability plus SwiftUI-specific remediation. It is especially useful when you need to know not just what may be wrong, but what to change with minimal code edits, and which findings are provable from source versus requiring manual confirmation.
How to Use swiftui-wcag-accessibility-auditor skill
Install and load order
For swiftui-wcag-accessibility-auditor install, use the repo’s install command: npx skills add ramzesenok/iOS-Accessibility-Audit-Skill --skill swiftui-wcag-accessibility-auditor. After install, read references/ios-audit-workflow.md first, then references/ios-audit-checklist.md, then references/wcag2mobile-ios-reference.md for the standards framing that drives the audit.
What input gives the best results
The swiftui-wcag-accessibility-auditor usage pattern works best when you provide a scoped feature, the screen path, and the code slice to inspect. For example: “Audit the SwiftUI sign-in flow in AuthView.swift and related views for WCAG 2.2 A/AA issues, return P0/P1/P2 fixes, and mark anything not provable in code as Needs user verification.” Include any custom controls, error states, or navigation that the skill should trace.
Suggested workflow
A practical swiftui-wcag-accessibility-auditor guide is: define the feature flow, inspect the entry view and downstream states, identify semantic hooks and risky patterns, then map findings to statuses and remediation priority. If the code does not prove behavior such as VoiceOver output, focus order, or visual contrast, the skill should stop short of claiming a pass and instead request a targeted user check.
Files to read first
Start with SKILL.md, then inspect references/ios-audit-workflow.md, references/ios-audit-checklist.md, references/swiftui-remediation-guide.md, references/swiftui-manual-checklist.md, and references/ios-accessibility-api-examples.md. This sequence helps you understand audit rules before you ask for fixes, which improves both finding quality and patch quality.
swiftui-wcag-accessibility-auditor skill FAQ
Is this only for SwiftUI?
Yes, the swiftui-wcag-accessibility-auditor skill is built around native SwiftUI iOS features. If the feature also includes UIKit, mixed implementation details, or custom platform bridging, the skill may still help, but you should expect less certainty and more user verification.
How is this different from a normal prompt?
A normal prompt can produce general accessibility advice. This skill is more decision-oriented: it follows a code-only audit workflow, uses WCAG 2.2 plus WCAG2Mobile framing, and prefers minimal SwiftUI patches with evidence-backed statuses. That makes it better for UX Audit work where traceability and change scope matter.
Is it beginner-friendly?
Yes, if you can point it at a screen or feature. You do not need to know every WCAG criterion, but you do need to provide enough context for the skill to locate the right flow. The more concrete your input, the less likely it is to overgeneralize.
When should I not use it?
Do not use it if you want live simulator testing, visual QA, or a broad mobile accessibility review that is not SwiftUI-centered. It is also not ideal when you only want a quick heuristic opinion without WCAG traceability; in that case a lighter SwiftUI review skill is a better fit.
How to Improve swiftui-wcag-accessibility-auditor skill
Give it a narrower feature slice
The strongest swiftui-wcag-accessibility-auditor usage inputs name one flow, one or two files, and one task outcome. For example, “Review the password reset screen and its error states” is better than “audit the app.” Narrow scope helps the skill separate real blockers from low-value observations.
Include the hardest cases up front
If the screen uses icon-only buttons, custom gestures, overlays, sheets, validation banners, dynamic type-sensitive layouts, or keyboard-driven forms, say so. These are the areas where swiftui-wcag-accessibility-auditor for UX Audit produces the most meaningful findings and where missing context causes the biggest quality drop.
Ask for evidence and edit-level fixes
Request findings with code evidence, WCAG mapping, and minimal remediation snippets. That pushes the skill toward patch-ready output instead of abstract advice. If you need a follow-up pass, ask it to focus on unresolved Needs user verification items or the highest-priority P0 and P1 issues first.
Iterate from audit to patch
After the first pass, feed back the accepted findings and ask for a second-pass refinement on the remaining code. This is the fastest way to improve result quality: the skill can tighten remediation, remove false positives, and turn uncertain areas into specific manual checks instead of broad recommendations.