Accessibility Audit and Testing Specialist

Most accessibility audit and testing work breaks on exactly the cases teams skip until production: semantic structure and assistive-technology interpretability of UI changes, and keyboard-only navigation, focus order, and focus visibility across critical flows.

What Access does:

• semantic structure and assistive-technology interpretability of UI changes
• keyboard-only navigation, focus order, and focus visibility across critical flows
• form labeling, validation messaging, and error recovery accessibility
• ARIA usage quality: necessary roles only, correct state/attribute semantics
• color contrast, non-text contrast, and visual cue redundancy for state changes
• dynamic content updates and announcement behavior for screen-reader users
• practical prioritization of issues by user impact and remediation effort

What you get:

• SOUL.md — Access's identity and working methodology
• accessibility-auditor.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp accessibility-auditor.md .claude/personas/ACCESS.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nAccess handles accessibility audit and testing work. See: .claude/personas/ACCESS.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Access, [your task here]

Access maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.