playbooks

home / skills / charleswiltgen / axiom / axiom-ios-accessibility

axiom-ios-accessibility skill

/.claude-plugin/plugins/axiom/skills/axiom-ios-accessibility

This skill helps you audit and fix iOS accessibility issues across VoiceOver, Dynamic Type, color contrast, and App Store readiness.

npx playbooks add skill charleswiltgen/axiom --skill axiom-ios-accessibility

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.2 KB
---
name: axiom-ios-accessibility
description: Use when fixing or auditing ANY accessibility issue - VoiceOver, Dynamic Type, color contrast, touch targets, WCAG compliance, App Store accessibility review.
license: MIT
---

# iOS Accessibility Router

**You MUST use this skill for ANY accessibility work including VoiceOver, Dynamic Type, color contrast, and WCAG compliance.**

## When to Use

Use this router when:
- Fixing VoiceOver issues
- Implementing Dynamic Type
- Checking color contrast
- Ensuring touch target sizes
- Preparing for App Store accessibility review
- WCAG compliance auditing

## Routing Logic

### Accessibility Issues

**All accessibility work** → `/skill axiom-accessibility-diag`
- VoiceOver labels and hints
- Dynamic Type scaling
- Color contrast (WCAG)
- Touch target sizes
- Keyboard navigation
- Reduce Motion support
- Accessibility Inspector usage
- App Store Review preparation

## Decision Tree

1. ANY accessibility issue → accessibility-diag

## Anti-Rationalization

| Thought | Reality |
|---------|---------|
| "I'll add VoiceOver labels when I'm done building" | Accessibility is foundational, not polish. accessibility-diag prevents App Store rejection. |
| "My app doesn't need accessibility" | All apps need accessibility. It's required by App Store guidelines and benefits all users. |
| "Dynamic Type just needs .scaledFont" | Dynamic Type has 7 common violations. accessibility-diag catches them all. |
| "Color contrast looks fine to me" | Visual assessment is unreliable. WCAG ratios require measurement. accessibility-diag validates. |

## Critical Pattern

**accessibility-diag** covers:
- 7 critical accessibility issues
- WCAG compliance levels (A, AA, AAA)
- Accessibility Inspector workflows
- VoiceOver testing checklist
- App Store Review requirements

## Example Invocations

User: "My button isn't being read by VoiceOver"
→ Invoke: `/skill axiom-accessibility-diag`

User: "How do I support Dynamic Type?"
→ Invoke: `/skill axiom-accessibility-diag`

User: "Check my app for accessibility issues"
→ Invoke: `/skill axiom-accessibility-diag`

User: "Prepare for App Store accessibility review"
→ Invoke: `/skill axiom-accessibility-diag`

Overview

This skill routes any iOS accessibility work to a focused diagnostic flow that finds and fixes VoiceOver, Dynamic Type, color contrast, touch target, and WCAG problems. It is the required entry point for accessibility audits, App Store accessibility preparation, and developer checks across iOS, iPadOS, watchOS, and tvOS projects. Use it to prevent regressions and App Store accessibility rejections.

How this skill works

When invoked, the router directs the request to a comprehensive accessibility diagnostic module that inspects labels, traits, hints, Dynamic Type scaling, contrast ratios, touch target sizes, keyboard navigation, and Reduce Motion behavior. It enforces a checklist-based workflow tied to WCAG levels (A, AA, AAA) and provides concrete remediation guidance and verifier steps using Accessibility Inspector and VoiceOver. The flow ensures every reported accessibility issue triggers the same rigorous audit and fix recommendations.

When to use it

  • Fixing VoiceOver labels, hints, or focus order
  • Implementing or verifying Dynamic Type support
  • Measuring and correcting color contrast to meet WCAG
  • Checking touch target sizes and tappable areas
  • Preparing or pre-auditing for App Store accessibility review

Best practices

  • Run the accessibility diagnostic early and on each release cycle
  • Treat accessibility as foundational, not as polish
  • Measure contrast ratios instead of relying on visual checks
  • Test with VoiceOver and Accessibility Inspector on real devices
  • Verify Dynamic Type at all predefined content size categories

Example use cases

  • Button voiceover label not read correctly — route to diagnostic to find missing traits or container issues
  • App fails contrast check in a dark theme — run the diagnostic to calculate WCAG ratios and suggest color swaps
  • Forms have tiny tappable targets — detect touch target violations and recommend layout fixes
  • Preparing an app for App Store review — full accessibility audit to catch common rejection causes

FAQ

Do I always use this for any accessibility-related task?

Yes. All accessibility work should start with this router to ensure consistent coverage across VoiceOver, Dynamic Type, contrast, touch targets, and WCAG checks.

Will this catch App Store accessibility issues?

Yes. The diagnostic maps findings to App Store accessibility review requirements and offers remediation steps to avoid rejection.