# Accessibility Audit

Run a comprehensive WCAG accessibility audit covering perceivable, operable...

- Repository: https://github.com/rampstackco/claude-skills (1014 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-27
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rampstackco/claude-skills --skill accessibility-audit -g -a claude-code -y`
Codex: `npx skills add rampstackco/claude-skills --skill accessibility-audit -g -a codex -y`
Cursor: `npx skills add rampstackco/claude-skills --skill accessibility-audit -g -a cursor -y`
Gemini CLI: `npx skills add rampstackco/claude-skills --skill accessibility-audit -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add rampstackco/claude-skills`

## Description

Run a comprehensive WCAG accessibility audit covering perceivable, operable, understandable, and robust principles. Use this skill whenever the user wants to audit accessibility, review WCAG compliance, fix accessibility issues, prepare for accessibility certification, address an accessibility lawsuit risk, or systematically improve a site's accessibility. Triggers on accessibility audit, WCAG audit, a11y audit, accessibility compliance, ADA compliance, screen reader test, keyboard navigation, accessibility report, fix accessibility, axe scan. Also triggers when accessibility issues have been reported and need systematic remediation.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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:**

The rest: https://github.com/rampstackco/claude-skills/blob/HEAD/dist/codex/.agents/skills/accessibility-audit/SKILL.md