accessibility-audit

Audit UI markup against WCAG 2.1 AA criteria and output prioritized fixes.

489|254|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/me2resh/apexyard --skill accessibility-audit-me2resh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/me2resh/apexyard/tree/main/marketplace/audit-pack/.claude/skills/accessibility-audit
Command: npx skills add https://github.com/me2resh/apexyard --skill accessibility-audit-me2resh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It identifies accessibility gaps that prevent users with disabilities from perceiving, operating, understanding, and using your interface to its full potential.

Core Features & Use Cases

  • WCAG 2.1 AA deep-dive auditing: Checks perceivable, operable, understandable, and robust criteria to surface concrete issues tied to WCAG numbers.
  • Prioritized findings with fix instructions: Produces a severity-based table with actionable remediation guidance for each finding.
  • Audit trend persistence: Persists audit artifacts via the shared audit-history library so accessibility progress is measurable across runs.

Quick Start

Ask the AI to run /accessibility-audit for your app and return a prioritized WCAG 2.1 AA findings table with copy-pasteable fixes, optionally persisting the audit trend.

Frequently Asked Questions about accessibility-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my web app for WCAG 2.1 AA compliance issues?

WCAG 2.1 AA compliance audits are performed by scanning and validating UI markup against perceivable, operable, understandable, and robust criteria. The audit outputs a severity-based table with actionable remediation guidance for each finding.

How do I get prioritized fix instructions for ARIA and keyboard navigation failures?

Prioritized fix instructions for ARIA and keyboard navigation failures are generated by mapping issues to specific WCAG 2.1 criteria. The output provides a severity-based table with copy-pasteable remediation guidance for each finding.

Can I track WCAG audit progress and accessibility trends across multiple runs?

WCAG audit progress is trackable across multiple runs using audit-history persistence. The tool saves audit artifacts via the shared audit-history library, rendering measurable accessibility trends over time.

What is the best way to run a proactive accessibility audit before a user-facing app launch?

A proactive accessibility audit for app launch readiness is run by validating UI markup against WCAG 2.1 AA criteria. It surfaces concrete issues tied to WCAG numbers and provides prioritized severity output with fix guidance.

Does the accessibility audit cover all four WCAG principles for UI compliance?

The accessibility audit covers all four WCAG principles for UI compliance by validating perceivable, operable, understandable, and robust criteria. It maps found issues directly to WCAG 2.1 criterion numbers.