axiom-accessibility-diag

Diagnose iOS and macOS accessibility violations with remediation strategies and code examples.

Updated Dec 3, 2025
One-click install
npx skills add https://github.com/tuliopc23/flying-dutchman-app --skill axiom-accessibility-diag-tuliopc23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axiom-accessibility-diag
Source: https://github.com/tuliopc23/flying-dutchman-app/tree/main/.claude/skills/axiom-accessibility-diag
Command: npx skills add https://github.com/tuliopc23/flying-dutchman-app --skill axiom-accessibility-diag-tuliopc23

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers identify and fix critical accessibility issues in their iOS and macOS applications, ensuring compliance with WCAG standards and passing App Store reviews.

Core Features & Use Cases

  • Comprehensive Diagnostics: Covers VoiceOver, Dynamic Type, Color Contrast, Touch Targets, Keyboard Navigation, and Reduce Motion.
  • WCAG Compliance: Provides guidance and code examples for meeting accessibility standards.
  • App Store Review Prep: Helps prepare apps for submission by addressing common rejection reasons.
  • Use Case: A developer is preparing to submit their app to the App Store and wants to ensure it meets all accessibility requirements. They use this Skill to audit their app for VoiceOver issues, Dynamic Type support, and color contrast failures.

Quick Start

Run an accessibility audit on the current application to identify common 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 check my iOS app for VoiceOver and Dynamic Type accessibility issues?

To check VoiceOver and Dynamic Type accessibility issues, diagnose the iOS app for missing traits, insufficient touch target sizes, and improper text scaling to ensure usability for all users.

What causes App Store review rejection related to accessibility compliance?

App Store review rejection related to accessibility compliance is caused by failing to support VoiceOver, inadequate color contrast ratios, and missing keyboard navigation, which violate platform accessibility standards.

How can I fix WCAG color contrast ratio failures in macOS development?

Fix WCAG color contrast ratio failures in macOS development by adjusting foreground and background color combinations to meet WCAG 2.1 AA or AAA standards, ensuring text remains legible for visually impaired users.

Does this accessibility diagnostic approach cover Reduce Motion compliance?

Yes, this accessibility diagnostic approach covers Reduce Motion compliance by identifying animations that ignore user motion preferences and providing remediation strategies to respect system settings.

What is the best way to prepare an iOS app for WCAG 2.1 AA compliance?

The best way to prepare an iOS app for WCAG 2.1 AA compliance is to audit VoiceOver labels, verify Dynamic Type scaling, validate touch target sizes, and apply provided code examples to fix violations.

How do I ensure keyboard navigation works correctly in my macOS application?

Ensure keyboard navigation works correctly in a macOS application by diagnosing focus order, verifying tab key traversal, and implementing proper key event handling to meet accessibility requirements.