# Accessibility Compliance Accessibility Audit

Audit pages and user journeys against a declared WCAG scope.

- Repository: https://github.com/sickn33/agentic-awesome-skills (48984 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

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

## Description

Audit pages and user journeys against a declared WCAG scope. Use when identifying keyboard, screen-reader, focus or contrast barriers and planning verified remediation.

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

# Accessibility Audit and Testing

Assess the supplied pages and user journeys against the agreed WCAG edition and level. Record observed barriers, actual test coverage, remediation priorities and unresolved manual checks; automated scans alone do not establish conformance.

## Use this skill when

- Auditing web or mobile experiences for WCAG compliance
- Identifying accessibility barriers and remediation priorities
- Establishing ongoing accessibility testing practices
- Preparing compliance evidence for stakeholders

## Do not use this skill when

- You only need a general UI design review without accessibility scope
- The request is unrelated to user experience or compliance
- You cannot access the UI, design artifacts, or content

## Context

Combine automated evidence with keyboard, screen-reader, focus and contrast inspection in the actual target environment. Keep untested journeys and incomplete checks visible.

## Requirements

Use the supplied WCAG edition/level, target pages and flows, authorized test environment, available audit tools and representative interaction states. Missing scope or UI access is an explicit limitation, not a passing audit.

## Instructions

- Confirm scope (platforms, WCAG level, target pages, key user journeys).
- Run automated scans to collect baseline violations and coverage gaps.
- Perform manual checks (keyboard, screen reader, focus order, contrast).
- Map findings to WCAG criteria, severity, and user impact.
- Provide remediation steps and re-test after fixes.
- If detailed procedures are required, open `resources/implementation-playbook.md`.

## Example

**Request:** “Audit keyboard use in our checkout staging flow against WCAG 2.2 AA.”

The rest: https://github.com/sickn33/agentic-awesome-skills/blob/HEAD/plugins/agentic-awesome-skills-claude/skills/accessibility-compliance-accessibility-audit/SKILL.md