accessibility-audit

# Accessibility Audit Run a thorough accessibility audit and produce a remediation plan. Stack-agnostic. Anchored to WCAG 2.1 AA, with notes on AAA where relevant. This skill goes deeper than the accessibility checks in `qa-testing` and `design-standards`. Use this when accessibility itself is the goal. --- ## When to use - Pre-launch accessibility verification - Compliance preparation (ADA, EN 301 549, AODA, Section 508) - Remediation after an audit finding or complaint - Annual or quarterly accessibility health check - Onboarding accessibility into a team that hasn't prioritized it before ## When NOT to use - General QA after deploys (use `qa-testing`) - Component-level accessibility implementation (use `frontend-component-build`) - Color contrast for design tokens (use `design-standards` or `brand-identity`) --- ## Required inputs - The site or product under audit - The scope (full site, specific section, specific user flow) - The target standard (WCAG 2.1 AA is most common) - Any specific concerns or known issues - Tools available (automated scanners, screen readers, manual testing) --- ## The framework: WCAG's 4 principles WCAG organizes accessibility around four principles. The audit covers each in depth. ### 1. Perceivable Information and UI must be presentable in ways users can perceive. **Audit checks:** - **Text alternatives.** All non-decorative images have descriptive `alt` text. Decorative images use `alt=""`. Complex images (charts, infographics...