axiom-audit-accessibility

Detects WCAG accessibility violations and anti-patterns in Swift/SwiftUI codebases.

34|2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/DengNaichen/Stet --skill axiom-audit-accessibility
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axiom-audit-accessibility
Source: https://github.com/DengNaichen/Stet/tree/main/.agents/skills/axiom-audit-accessibility
Command: npx skills add https://github.com/DengNaichen/Stet --skill axiom-audit-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill identifies accessibility violations, missing assistive technology support, and anti-patterns that prevent users with disabilities from using your application and often lead to App Store rejections.

Core Features & Use Cases

  • Automated Audit: Scans codebase for missing VoiceOver labels, fixed font sizes, and low-contrast elements.
  • Compliance Verification: Checks against WCAG 2.1/2.2 standards for Level A, AA, and AAA compliance.
  • Use Case: Before submitting your app to the App Store, run this audit to ensure all interactive elements are reachable by VoiceOver and that your layout supports Dynamic Type scaling.

Quick Start

Use the axiom-audit-accessibility skill to perform a full accessibility audit on the current project directory.

Frequently Asked Questions about axiom-audit-accessibility

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

FAQPage Schema
How do I audit my SwiftUI codebase for WCAG compliance and VoiceOver support?

To check Swift code for accessibility violations, scan UI hierarchies and gesture interactions to validate VoiceOver labels, Dynamic Type scaling, and touch target sizes. This process detects missing assistive technology support and ensures WCAG Level A, AA, and AAA compliance.

What accessibility anti-patterns cause App Store rejections in Swift apps?

Common accessibility anti-patterns causing App Store rejections include missing VoiceOver labels on interactive elements, fixed font sizes that ignore Dynamic Type scaling, and insufficient touch target sizes. Scanning your SwiftUI codebase detects these violations and verifies WCAG compliance.

Can I verify Dynamic Type scaling and touch target sizes in an automated SwiftUI audit?

Yes, you can verify Dynamic Type scaling and touch target sizes by analyzing SwiftUI UI hierarchies and font scaling strategies. The audit detects fixed font sizes and insufficient touch targets, ensuring interactive elements meet WCAG standards and support assistive technologies.

How do I check if my Swift app meets WCAG 2.1 and 2.2 Level AA requirements?

To check if your Swift app meets WCAG 2.1 and 2.2 Level AA requirements, run an automated audit against your codebase to validate VoiceOver support, font scaling, and touch target sizes. This identifies missing assistive technology features and confirms compliance.

What is the best way to find missing VoiceOver labels in a SwiftUI project?

The best way to find missing VoiceOver labels is running an automated accessibility audit on your SwiftUI project directory. This scans UI hierarchies and interactive elements to detect missing assistive technology support and verify WCAG compliance before App Store submission.