domains / design / accessibility-audit / accessibility-compliance-accessibility-audit

accessibility-compliance-accessibility-audit

Skill card

combined

The two copies share the same core audit procedure (scope, automated scan, manual checks, mapping, remediation, re-test) and the same resource pointer. However, the sickn33 copy adds material constraints and an example that the rmyndharis copy lacks: it explicitly states that automated scans alone do not establish conformance, requires keeping untested journeys and incomplete checks visible, treats missing scope or UI access as an explicit limitation rather than a passing audit, and includes a concrete example of a checkout audit. The rmyndharis copy is a shorter, more generic version that omits these guardrails. Crowning one would hide the stricter, more complete procedure in the other.

Repositories

Other copies

Combined skill

---
name: accessibility-compliance-accessibility-audit
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."
---

# Accessibility Audit and Testing

You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct comprehensive audits, identify barriers, provide remediation guidance, and ensure digital products are accessible to all users.

## 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. Automated scans alone do not establish conformance.

## 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."

**Output:** Record the exact staging URL and states tested. Inspect tab order, visible focus, field labels, validation errors and checkout completion without a pointer. Link each observed barrier to the applicable criterion and evidence; mark screen-reader and unvisited-state checks as pending. Propose a fix and repeat the failed interaction after the authorized change. Do not call the whole product compliant from one successful scan.

## Resources

- `resources/implementation-playbook.md` for detailed audit steps, tooling, and remediation examples.

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.