axiom-accessibility-diag

Diagnose accessibility issues in iOS and macOS apps for WCAG compliance.

61|3|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/joelhooks/joelclaw --skill axiom-accessibility-diag-joelhooks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axiom-accessibility-diag
Source: https://github.com/joelhooks/joelclaw/tree/main/.agents/skills/axiom-accessibility-diag
Command: npx skills add https://github.com/joelhooks/joelclaw --skill axiom-accessibility-diag-joelhooks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses critical accessibility issues in iOS/macOS apps, ensuring compliance with App Store guidelines and improving user experience for individuals with disabilities.

Core Features & Use Cases

  • Comprehensive Diagnostics: Identifies and provides solutions for VoiceOver, Dynamic Type, color contrast, touch target, keyboard navigation, and Reduce Motion issues.
  • WCAG Compliance: Aligns with Web Content Accessibility Guidelines (WCAG) AA and AAA standards.
  • App Store Review Preparation: Helps prepare apps to meet Apple's strict accessibility requirements, preventing rejections.
  • Use Case: A developer needs to ensure their new app is fully accessible before submission. They use this Skill to audit all screens, identify VoiceOver label deficiencies, and fix low color contrast ratios, guaranteeing a smooth App Store review process.

Quick Start

Run a full accessibility audit on the current application to identify all critical issues.

Frequently Asked Questions about axiom-accessibility-diag

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an accessibility audit for my iOS app before App Store submission?

Run an accessibility audit by evaluating VoiceOver labels, Dynamic Type scaling, color contrast ratios, and touch target sizes. This diagnostic process identifies WCAG compliance issues and remediation steps to prevent App Store review rejections.

What's the best way to fix VoiceOver navigation issues in macOS development?

Fix VoiceOver navigation issues by auditing accessibility traits, labels, and keyboard focus order. Diagnostic guidance provides code examples and testing strategies to ensure proper screen reader interaction and WCAG compliance.

Does my app meet WCAG AA and AAA color contrast requirements?

WCAG color contrast requirements are met by evaluating foreground and background color ratios against AA and AAA standards. Diagnostic tools identify low contrast elements and provide remediation guidance for better readability.

How do I add Reduce Motion and Dynamic Type support to prevent App Store rejection?

Add Reduce Motion and Dynamic Type support by implementing scalable fonts and motion alternatives. Diagnostic guidance identifies missing implementations and provides code examples to ensure accessibility compliance for App Store review.

Can I check keyboard navigation and touch target sizes for iOS accessibility compliance?

Keyboard navigation and touch target sizes are checked by auditing focus order and interactive element dimensions. Diagnostics identify target sizes below standards and navigation gaps, offering code fixes for full accessibility compliance.

Why does my iOS app fail App Store review for accessibility issues?

Apps fail App Store review for accessibility issues when VoiceOver labels are missing, contrast ratios are low, or Dynamic Type is unsupported. Diagnostics identify these specific deficiencies and provide remediation guidance to ensure approval.