WCAG Accessibility Audit

VerifiedSafe

Conduct comprehensive accessibility audits for WCAG compliance, identify barriers, and provide remediation guidance.

Sby Skills Guide Bot
TestingIntermediate
7/25/2026
Claude CodeCursorCopilotCodex
#accessibility#wcag#audit#inclusive-design#screen-reader

Recommended for

Automated summary

Runs a digital accessibility audit by combining automated scans, manual checks (keyboard, screen reader, focus order, contrast) and remediation guidance mapped to WCAG criteria.

Strengths

  • Maps each finding to a WCAG criterion with a severity rating and user impact
  • Pairs automated scanning with manual verification instead of relying on a scanner alone
  • Points to a detailed playbook in resources/implementation-playbook.md for full procedures
  • Includes a re-test step after fixes and supports producing compliance evidence for stakeholders

Limitations

  • Does not substitute for testing with real users and real assistive technologies
  • Requires access to the UI, design artifacts or user journeys; otherwise the audit stays generic
  • Automated tooling only catches a subset of WCAG criteria, and the skill gives no coverage estimate
When to use it

Use it when a site or app must be audited against a specific WCAG level and accessibility fixes need to be prioritized.

When not to use it

Skip it for a general visual UI critique with no accessibility or compliance scope.

Security analysis

Safe
Quality score85/100

The skill provides guidance for accessibility auditing, WCAG compliance, and remediation. It does not instruct any destructive, exfiltrating, or obfuscated actions, and declares no allowed tools. The instructions are advisory and analytical, with no meaningful execution risk.

No concerns found

How this analysis is made

Examples

WCAG 2.2 AA audit
Audit our React checkout flow against WCAG 2.2 AA: run automated scans, do a keyboard and screen reader pass on the payment steps, and give me a prioritized remediation list with the failing criteria.
Ongoing testing practice
Set up an ongoing accessibility testing practice for our design system — which automated checks to run in CI, what to verify manually each release, and how to record the evidence.
Remediation of findings
Here are 14 axe-core violations from our marketing site. Group them by user impact, map each to the WCAG criterion, and tell me what to fix first and how to re-test.

name: accessibility-compliance-accessibility-audit description: "You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance." risk: safe source: community date_added: "2026-02-27"

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

The user needs to audit and improve accessibility to ensure compliance with WCAG standards and provide an inclusive experience for users with disabilities. Focus on automated testing, manual verification, remediation strategies, and establishing ongoing accessibility practices.

Requirements

$ARGUMENTS

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.

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.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/wcag-accessibility-audit-mrzxuql3/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/wcag-accessibility-audit-mrzxuql3' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/wcag-accessibility-audit-mrzxuql3/download' --output '.skill-downloads/wcag-accessibility-audit-mrzxuql3/SKILL.md.part' && mv '.skill-downloads/wcag-accessibility-audit-mrzxuql3/SKILL.md.part' '.skill-downloads/wcag-accessibility-audit-mrzxuql3/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Original excerpt: Requirements

$ARGUMENTS

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/wcag-accessibility-audit-mrzxuql3/SKILL.md' && test -s '.skill-downloads/wcag-accessibility-audit-mrzxuql3/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/accessibility-compliance-accessibility-audit' && cp -R '.skill-downloads/wcag-accessibility-audit-mrzxuql3' '.claude/skills/accessibility-compliance-accessibility-audit'

Cursor
test -f '.skill-downloads/wcag-accessibility-audit-mrzxuql3/SKILL.md' && test -s '.skill-downloads/wcag-accessibility-audit-mrzxuql3/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/accessibility-compliance-accessibility-audit' && cp -R '.skill-downloads/wcag-accessibility-audit-mrzxuql3' '.cursor/skills/accessibility-compliance-accessibility-audit'

Codex
test -f '.skill-downloads/wcag-accessibility-audit-mrzxuql3/SKILL.md' && test -s '.skill-downloads/wcag-accessibility-audit-mrzxuql3/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/accessibility-compliance-accessibility-audit' && cp -R '.skill-downloads/wcag-accessibility-audit-mrzxuql3' '.agents/skills/accessibility-compliance-accessibility-audit'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/wcag-accessibility-audit-mrzxuql3'

openskills read 'wcag-accessibility-audit-mrzxuql3'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/wcag-accessibility-audit-mrzxuql3/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills