Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rshankras/accessibility-audit
Run a structured accessibility audit on an iOS/macOS app — automated XCUITest audits, Accessibility Inspector, manual VoiceOver/Dynamic Type passes, and App Store Accessibility Nutrition Label evaluation. Use before release, when preparing Nutrition Label declarations, or for EU Accessibility Act compliance.
Passed 17 of 22 test cases with the skill, and 16 of 22 without it.
and 2 more in the full report
3 fixed14 passed either way3 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our iOS development team wants to begin an accessibility audit workflow. What must be established in step 1 before running automated tools or manual assistive tech passes?
| Checked | Without skill | With skill |
|---|---|---|
| Define primary user tasks and core flows like onboarding, login, purchase, and settings. | Missed | Passed |
The instructions your model reads when the skill loads.
A repeatable audit workflow that takes an app from "we think it's accessible" to evidence: automated audits in CI, an Inspector pass, manual assistive-tech passes, and an Accessibility Nutrition Label evaluation you can defend. Distilled from Apple's WWDC23 "Perform accessibility audits" (10035), WWDC19 "Accessibility Inspector" (257), WWDC25 "Evaluate your app for Accessibility Nutrition Labels" (224), and the 2026 Tech Talk "Prepare your app for Accessibility Nutrition Labels" (111433).
Why it matters: Accessibility Nutrition Labels on the App Store make your support (or its absence) visible before download.
performAccessibilityAudit, Accessibility Inspector, or automated a11y testingrelease-review)List the primary tasks people download the app for, plus the fundamentals: first-launch experience, login, purchase, settings. Every subsequent pass evaluates these tasks, on every device family the app supports.
try app.performAccessibilityAudit() audits the current view exactly as the Inspector does; the test fails automatically on findings. Full API, audit-type table, issue filtering, and CI patterns: automated-audits.md. Baseline rules:
continueAfterFailure = true before the audit to surface all issues in one run.Xcode → Open Developer Tool → Accessibility Inspector, target the app:
Classic findings and fixes: filename-as-label (give a real accessibilityLabel; move technical IDs to accessibilityIdentifier), text drawn via CATextLayer invisible to VoiceOver (isAccessibilityElement = true + label), contrast below threshold (Inspector flags pairs; fix with darker/lighter variants until it passes).
test cases passed, vs 16 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.