agentleFS
gygantskiyMatilyockgygantskiyMatilyock/ios-developer-agents/.claude/skills/ios-accessibility-validator/SKILL.md

ios-accessibility-validator

Skill30 starsChanged 11 months agoMITView on GitHub

Use this skill to audit iOS apps for accessibility compliance with Apple Human Interface Guidelines, WCAG 2.2 standards, and iOS accessibility best practices. Read the full agent prompt from agents/accessibility-validator/accessibility-validator.md in the ios-developer-agents repository. Follow the audit process: Provide structured findings with: - Compliance summary (Apple HIG, WCAG 2.2 Level A/AA) - Critical issues (blocks users) - VoiceOver audit table - Dynamic Type audit - Color contrast audit - Touch target audit - Accessibility settings support table

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to audit iOS apps for accessibility compliance with Apple Human Interface Guidelines, WCAG 2.2 standards, and iOS …

    line 3
  2. Distinctive:

    When building new UI components

    line 7
  3. Distinctive:

    When targeting accessibility certifications

    line 10
  4. Distinctive:

    After receiving accessibility feedback

    line 11
  5. Distinctive:

    When building apps for enterprise/government (Section 508)

    line 12
  6. Very specific:

    Read the full agent prompt from agents/accessibility-validator/accessibility-validator.md in the ios-developer-agents repository.

    line 16
  7. Distinctive:

    Follow the audit process:

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

iOS Accessibility Validator

Use this skill to audit iOS apps for accessibility compliance with Apple Human Interface Guidelines, WCAG 2.2 standards, and iOS accessibility best practices.

When to Use

  • When building new UI components
  • Before app releases
  • When improving accessibility
  • When targeting accessibility certifications
  • After receiving accessibility feedback
  • When building apps for enterprise/government (Section 508)

How to Apply

Read the full agent prompt from agents/accessibility-validator/accessibility-validator.md in the ios-developer-agents repository.

Follow the audit process:

  1. VoiceOver Compatibility - Labels, hints, traits, element grouping, reading order
  2. Dynamic Type Support - Text scaling, layout adaptation
  3. Color & Visual - Contrast ratios (4.5:1/3:1), color independence, Dark Mode
  4. Motion & Animation - Reduce Motion support, flashing content
  5. Touch Targets - 44x44pt minimum, gesture alternatives
  6. Switch Control & Voice Control - Keyboard access, scanning
  7. Audio & Haptics - Captions, audio descriptions, alternatives
  8. Cognitive Accessibility - Clear language, predictable behavior
  9. Accessibility APIs - UIKit/SwiftUI implementation review

Output Format

Provide structured findings with:

  • Compliance summary (Apple HIG, WCAG 2.2 Level A/AA)
  • Critical issues (blocks users)
  • VoiceOver audit table
  • Dynamic Type audit
  • Color contrast audit
  • Touch target audit
  • Accessibility settings support table

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.