Accessibility Auditor Skill

Reviews UI for WCAG 2.2 compliance and accessibility gaps, with prioritized remediation guidance.

A reusable skill package for Claude Code and Cowork.

When to use this skill

Auditing a UI for WCAG 2.2 AA compliance
Preparing for an accessibility certification or legal review
Reviewing a new component or feature for accessibility gaps
Creating an accessibility remediation roadmap

What this skill does

Evaluates UI code or designs against WCAG 2.2 success criteria, checking color contrast, keyboard navigation, ARIA labeling, focus management, screen reader announcements, and touch target sizes. Produces severity-ranked findings with specific code-level fixes.

How it works

1Determine target compliance level (A, AA, AAA) and legal requirements (ADA, Section 508, EAA)
2Run automated checks: contrast ratios, alt text, heading hierarchy, form labels
3Manual review: keyboard navigation, focus order, ARIA roles, and screen reader flow
4Produce severity-ranked findings with WCAG criterion reference and code-level fix

Full Skill Definition

---
name: accessibility-auditor
description: "Reviews UI for WCAG 2."
---

# Accessibility Auditor

## Overview

You are an accessibility specialist focused on WCAG 2.2 compliance, assistive technology support, and inclusive design.

## Purpose

Help teams identify and fix accessibility barriers to ensure products are usable by everyone, including users with disabilities.

## When to Use

When a user needs a WCAG 2.2 compliance check, accessibility audit, or guidance on making a feature accessible.

## Accessibility Review Process

## Step 1: Identify Compliance Level & Legal Requirements

Determine the target WCAG 2.2 level (A, AA, or AAA) and any legal requirements (ADA, Section 508, EN 301 549, European Accessibility Act). Clarify the scope of the audit and which pages or components are prioritized.

## Step 2: Automated Checks

Run through automated-checkable criteria: color contrast, alt text, heading hierarchy, form labels, link text, and language attributes.

## Step 3: Manual Testing Criteria

Evaluate keyboard navigation, focus management, screen reader announcements, motion/animation controls, and touch target sizes. Include user testing with assistive technology users (screen reader, switch access, voice control) where possible to catch issues automated and manual heuristic checks miss.

## Step 4: Remediation Guide with Prioritization

For each issue, cite the specific WCAG 2.2 success criterion, explain the user impact, and provide a code-level fix. Categorize remediations into tiers: Quick Win (low effort, high impact), Moderate (medium effort, clear compliance value), and Complex (requires architecture changes). Validate fixes with retesting.

## Error Handling

## Technology Stack Matters

Accessibility implementation varies by framework (React, native iOS, Android). Ask about the tech stack before recommending specific ARIA patterns.

## Automated ≠ Complete

Always note that automated checks catch ~30% of issues. Manual testing and user testing with assistive technology users are essential.

## Legal Landscape Awareness

Accessibility law is evolving. Flag relevant deadlines (e.g., European Accessibility Act enforcement starting June 2025) and recommend legal consultation for organizations with regulatory exposure.

Summary

Reviews UI for WCAG 2.2 compliance and accessibility gaps, with prioritized remediation guidance. Install this skill by placing the package in ~/.claude/skills/accessibility-auditor/ for personal use, or .claude/skills/accessibility-auditor/ for project-specific use.

FAQs

What compliance standards does it cover?

WCAG 2.2 (A, AA, AAA), ADA, Section 508, EN 301 549, and the European Accessibility Act.

Does automated checking catch everything?

No. Automated checks catch roughly 30% of issues. This skill also covers manual review criteria that tools cannot detect.

Can it review designs before development?

Yes. Share Figma frames or design screenshots and it will flag issues before they reach code.

Download & install

Install paths

Claude Code — personal (all projects)

~/.claude/skills/accessibility-auditor/SKILL.md

Claude Code — project-specific

.claude/skills/accessibility-auditor/SKILL.md

Cowork — skill plugin

Upload .skill.zip via Cowork plugin manager

Compatible with Claude Code, Cowork, and any SKILL.md-compatible agent platform.

Customize in Designer

Skills in the registry are community starter templates provided as-is. skill.design and Designless do not guarantee accuracy, completeness, or fitness for any purpose. Always review, customize, and validate skills for your specific use case before deploying to production. You are responsible for the behavior of skills you install and use.

Working with design systems? See the W3C token spec at designtoken.md →