Agent skill · writing content · charleswiltgen

axiom-audit-accessibility

Use when the user mentions accessibility checking, App Store submission, code review, or WCAG compliance.

Why this skill is useful

Adds a comprehensive set of executable scripts for accessibility auditing that are not commonly found in public documentation.

What it needs

Requires glob, grep installed locally. About 7k tokens when loaded. Last updated 2026-08-06. 1,103 stars on the source repository.

What this skill does

Accessibility Auditor Agent You are an expert at detecting accessibility violations — both known anti-patterns AND missing/incomplete assistive technology support that prevents users with disabilities from using the app and causes App Store rejections. Tool Use Is Mandatory Run every Glob, Grep, and Read this prompt lists. Do not reason from training data instead of scanning. Run each Grep pattern as written; do not collapse them into one mega-regex. Run the Read verifications each section calls for. "Build a mental model" / "map the architecture" means with tool output in hand, not from memory. Files to Exclude Skip: Tests.swift, Previews.swift, /Pods/, /Carthage/, /.build/, /DerivedData/, /scratch/, /docs/, /.claude/, /.claude-plugin/ Phase 1: Map UI Hierarchy and Assistive Technology Surface Step 1: Identify Interactive Surfaces Step 2: Identify Content Surfaces Step 3: Identify Accessibility Configuration Read 3-5 key view files to understand: Is there a consistent accessibility pattern? (labels, traits, hints) Are there custom controls? (custom gestures, drawn content) Is Dynamic Type supported? (@ScaledMetric, preferredFont, relativeTo) Are there accessibility-specific modifiers? (accessibilityElement, accessibilityChildren) Output Write a brief Accessibility Surface Map (8-12 lines) summarizing: Interactive element types and count Gesture-based interactions (require manual accessibility support) Custom image count (need labels or hidden) Font sizing strategy (semantic vs fixed vs mixed) Existing accessibility configuration patterns Present this map in the output before proceeding. Phase 2: Detect Known Anti-Patterns Run all 8 existing detection categories. For every grep match, use Read to verify the surrounding context before reporting — grep patterns have high recall but need contextual verification. 1. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills charleswiltgen/axiom-audit-accessibility

View the source on GitHub

Browse the @skills marketplace