axiom audit accessibility

Engineering Community

Skill notes

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/*

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)

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.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@CharlesWiltgen · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Map UI Hierarchy and Assistive Technology Surface

Phase 1: Map UI Hierarchy and Assistive Technology Surface

02
Step 1: Identify Interactive Surfaces

Step 1: Identify Interactive Surfaces

03
Step 2: Identify Content Surfaces

Step 2: Identify Content Surfaces

04
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)

05
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.

06
Phase 3: Reason About Accessibility Completeness

Using the Accessibility Surface Map from Phase 1 and your domain knowledge, check for what's *missing* — not just what's wrong. Question · What it detects · Why it matters Are there flows that are completely inaccessible via VoiceOver? (gesture-only interactions without accessibility equivalents) · Inaccessible critical paths · VoiceOver users can't complete core tasks — App Store rejection risk Are there screens where the only way to perform an action is via a gesture (drag, long press, pinch) with no button alternative? · Gesture-only paths · Users who can't perform gestures (motor impairments, Switch Control) are blocked

07
Phase 4: Cross-Reference Findings

Bump severity for these combinations: Finding A · + Finding B · = Compound · Severity Gesture-only interaction · No accessibilityAction · Feature completely inaccessible · CRITICAL Missing labels on buttons · In critical flow (purchase, auth) · Core transaction inaccessible · CRITICAL Fixed font sizes · No @ScaledMetric for spacing · Completely ignores Dynamic Type · CRITICAL

08
Phase 5: Accessibility Health Score

Scoring: COMPLIANT: No CRITICAL issues, 0 Level A violations, >90% VoiceOver label coverage, all gestures have accessibility equivalents GAPS: No CRITICAL issues, but Level A or AA violations present, or 70-90% label coverage, or some gesture-only paths NON-COMPLIANT: Any CRITICAL issues, or multiple Level A violations, or <70% label coverage, or critical flows inaccessible

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.