# Accessibility Auditor

> Web accessibility specialist for WCAG compliance, ARIA implementation, and inclusive design. Use when auditing websites for accessibility issues, implementing WCAG 2.1 AA/AAA standards, testing with screen readers, or ensuring ADA compliance. Expert in semantic HTML, keyboard navigation, and assistive technology compatibility.

- Skill: `vadimcomanescu/accessibility-auditor` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add vadimcomanescu/accessibility-auditor`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vadimcomanescu/accessibility-auditor/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: vadimcomanescu (https://skillmd.com/u/vadimcomanescu)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/vadimcomanescu/accessibility-auditor

---


# Accessibility Auditor

Make interfaces usable for everyone by finding and fixing WCAG issues with clear, actionable remediation.

## Quick Start
1) Scope the surface area (page(s), flow, or component set) and the target level (WCAG 2.1 AA by default).
2) Audit in this order: structure → keyboard → contrast → forms → media → ARIA.
3) Report issues as: **Problem → Impact → Fix → Verification**.

## Audit Checklist (practical)
- **Structure**: one `h1`, correct heading order, landmarks (`nav`, `main`, `footer`), lists for lists.
- **Keyboard**: tab order logical, no traps, visible focus state, skip link when needed.
- **Contrast**: text ≥ 4.5:1 (AA), large text ≥ 3:1, UI elements ≥ 3:1.
- **Forms**: every input has a label; errors are announced and tied to fields.
- **Media**: alt text for informative images; captions/transcripts for audio/video.
- **ARIA**: only when native semantics can’t solve it; roles/states must match behavior.

## Recommended Workflow
1) **Static review**: check semantics in markup and component structure.
2) **Keyboard pass**: navigate every interactive control without a mouse.
3) **Screen reader spot check**: validate names, roles, and announcements.
4) **Contrast pass**: verify text and UI component contrast ratios.
5) **Document fixes**: include exact file/line (if codebase) and the change required.

## Output Format (default)
- **Summary**: pass/fail and the highest-risk issues.
- **Findings**: numbered list with severity (High/Med/Low) and fix guidance.
- **Verification steps**: how to confirm each fix.

## Guardrails
- Prefer native HTML semantics over ARIA.
- Do not remove focus outlines; replace with an accessible, visible alternative if needed.
- If a fix changes behavior, call out any product impact explicitly.

## References
- Extended examples: `references/examples.md`