ios-accessibility
Skill0 starsChanged 3 months agoMITView on GitHub
Procedure for reviewing and verifying iOS accessibility — VoiceOver, Dynamic Type, contrast, hit targets, Switch Control, Reduce Motion — with an explicit static-vs-runtime split. Use when asked to "make this accessible", check VoiceOver support, or evaluate accessibility beyond the visual-consistency checks ios-ux-reviewer already does.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- VelimirMueller/claude-skillstheir own version, first seen Nov 1, 2026
- VelimirMueller/ai-development-skillstheir own version, first seen Nov 1, 2026
- The-Artificer-of-Ciphers-LLC/skills-from-the-artificertheir own version, first seen Nov 1, 2026
- thienqo/ios-skillstheir own version, first seen Oct 11, 2026
- rusel95/ios-agent-skillstheir own version, first seen Apr 16, 2026
- dadederk/iOS-Accessibility-Agent-Skilltheir own version, first seen Mar 9, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- dadederk/iOS-Accessibility-Agent-Skill★ 167same name
- rusel95/ios-agent-skills★ 13same name
- VelimirMueller/ai-development-skills★ 7same name
- VelimirMueller/claude-skills★ 7same name
- The-Artificer-of-Ciphers-LLC/skills-from-the-artificer★ 6same name
- thienqo/ios-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Check accessibility with the same static-vs-runtime discipline this repo applies everywhere else.
- Distinctive: line 75
Read the actual view code and check the static patterns above.
- Very specific: line 79
If the project's test target has performAccessibilityAudit() available, recommend running it — and if it's already run, use its actual …
- Very specific: line 86
If accessibility identifiers for UI testing (not VoiceOver labels) are what's actually needed, hand off to ios-ui-test-engineer — related …
- Distinctive: line 120
Never say "fully accessible" or "accessible" as a blanket claim — report per-category findings (labels, contrast, Dynamic Type, motion, …
- Very specific: line 123
Never claim VoiceOver reading order is correct without actually having heard it (RUNTIME_VERIFIED) or run an automated audit …
- Very specific: line 126
Never claim performAccessibilityAudit() passing covers everything — it audits specific categories.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
iOS Accessibility
Purpose
Check accessibility with the same static-vs-runtime discipline this repo applies everywhere else. A code read can find real, concrete problems (a missing label, a fixed font size) — it cannot confirm "fully accessible," which is a claim only actual assistive-technology use can support.
When to Use
Any request to review or improve accessibility beyond
ios-ux-reviewer's visual/HIG checklist — VoiceOver behavior,
Dynamic Type, contrast, tap targets, Switch Control, Reduce Motion, or
accessibility notifications.
Inputs
- The actual view code — labels, traits, hints, font choices, frame/padding values, animation code.
- Whether the project's test target uses
XCUIApplication().performAccessibilityAudit()(Xcode 15+) — a real automated audit API, not a manual checklist substitute (see Verification).
Core Knowledge
- STATIC REVIEW (reading code) can find: a missing
accessibilityLabelon an icon-only control, a missingaccessibilityTraitson a custom (non-standard) control, a fixed point-size font instead of a Dynamic-Type-scalable one, a tap target smaller than 44×44pt, and state conveyed by color alone with no icon/text backup. - RUNTIME ACCESSIBILITY VERIFICATION (actually running with VoiceOver/Switch Control/Reduce Motion enabled, or running an automated audit) is a different, stronger claim — it can catch things static review cannot, like whether VoiceOver's reading order actually makes sense, or whether a custom gesture has no alternative action for Switch Control users.
XCUIApplication().performAccessibilityAudit()(Xcode 15+) runs a real automated audit against categories including contrast, hit-target size, and missing labels — this isTEST_VERIFIEDevidence when it's actually run, not a manual checklist substitute.- Reduce Motion (
UIAccessibility.isReduceMotionEnabled) — custom animations/transitions that don't check this setting force motion on users who've explicitly asked to reduce it, which for some users is a vestibular-disorder trigger, not just a preference. - Accessibility notifications — dynamic content changes that don't
trigger navigation (an async load finishing, a form field appearing)
need an explicit
UIAccessibility.post(notification:)(.screenChangedor.announcement) or VoiceOver users get no signal anything changed.
Detection Patterns
| Pattern | Risk | Detect by |
Icon-only button/control with no accessibilityLabel | VoiceOver reads the asset filename or just "button" — the control is functionally unusable | grep for image-only buttons/icons; check for a matching label |
Custom (non-standard) control with no accessibilityTraits | VoiceOver doesn't announce it as a button/toggle/etc. — users can't tell what it does or that it's interactive | Any hand-rolled tappable view not using a standard Button/Toggle/etc. |
Fixed point-size font (.font(.system(size: 14))) instead of a Dynamic-Type-scalable style | Text doesn't grow for users who've increased their text size — a real usability barrier, not a preference | grep fixed-size font modifiers on user-facing text |
| Tap target smaller than 44×44pt | Mis-taps for users with limited dexterity or larger fingers | Check frame/padding values against the 44pt minimum |
| State conveyed by color alone (e.g. a red border for an error, no icon/text) | Inaccessible to colorblind users and to VoiceOver (color has no audible representation) | Look for color-only state changes with no accompanying icon/text |
| Custom animation/transition with no Reduce Motion check | Forces motion on users who've explicitly disabled it | grep for custom animation code with no isReduceMotionEnabled check |
| Swipe-only or gesture-only interaction with no alternative action | Unusable via Switch Control, which can't perform complex gestures | Check whether an accessibilityAction alternative exists alongside the gesture |
| Compound view (icon + label) exposed as separate VoiceOver elements when they should announce together | VoiceOver users hear two fragments instead of one coherent announcement | Check for .accessibilityElement(children: .combine) (or .ignore with an explicit combined label) on compound controls |
| Async content change with no accessibility notification | VoiceOver users get no signal that new content appeared without a navigation event | grep for state updates from async work with no UIAccessibility.post(notification:) call |
Procedure
- Read the actual view code and check the static patterns above.
- For each finding, state the concrete assistive-technology consequence (which user, using what technology, hits what problem) — not "may have accessibility issues."
- If the project's test target has
performAccessibilityAudit()available, recommend running it — and if it's already run, use its actual output asTEST_VERIFIEDevidence, not a description of what it would probably find. - Explicitly separate what was found by static review from what would need VoiceOver/Switch Control/Reduce Motion actually enabled to confirm.
- If accessibility identifiers for UI testing (not VoiceOver labels)
are what's actually needed, hand off to
ios-ui-test-engineer— related but a different concern (testability, not assistive tech).
Common Mistakes
- Treating a comprehensive static checklist pass as "fully accessible" — static review cannot confirm VoiceOver's actual reading order or Switch Control usability.
- Adding an
accessibilityLabelthat just restates the visible text redundantly instead of describing function ("Photo of sunset" vs. "photo" when the surrounding text already says "sunset"). - Confusing
accessibilityIdentifier(for UI test selectors) withaccessibilityLabel(for VoiceOver) — they serve different purposes and a control usually needs both, not one standing in for the other.
Verification
- A missing-label/trait/Dynamic-Type/tap-target/color-only finding from
reading code is
STATIC_ANALYSIS. performAccessibilityAudit()actually run and its output shown isTEST_VERIFIED.- VoiceOver/Switch Control/Reduce Motion actually enabled and the
behavior actually observed is
RUNTIME_VERIFIED.
Evidence Requirements
Per ios-evidence-reporting's matrix, "fully accessible" is never
claimable from static inspection — state what was checked (which
categories, which screens) and what remains unverified rather than
implying completeness.
Claim Restrictions
- Never say "fully accessible" or "accessible" as a blanket claim — report per-category findings (labels, contrast, Dynamic Type, motion, Switch Control) with their own evidence tier each.
- Never claim VoiceOver reading order is correct without actually
having heard it (
RUNTIME_VERIFIED) or run an automated audit (TEST_VERIFIED) — a logical code read is not the same evidence. - Never claim
performAccessibilityAudit()passing covers everything — it audits specific categories; state which ones, don't imply total coverage.
Output Format
Findings grouped by category (labels/traits, Dynamic Type, contrast,
tap targets, motion, Switch Control, notifications), each with
file:line, the concrete assistive-technology consequence, and the fix.
Close with the ios-evidence-reporting status block, explicit about
which lines are STATIC_ANALYSIS vs. TEST_VERIFIED/RUNTIME_VERIFIED.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

