What is the accessibility compliance audit skill?
The accessibility-compliance-audit skill is a SKILL.md in the sickn33/agentic-awesome-skills library. It casts your agent as an accessibility expert who confirms scope, runs automated scans, checks keyboard and screen reader behavior, maps findings to WCAG criteria and severity, and re-tests after fixes.
In the repository this skill is named accessibility-compliance-accessibility-audit. Its description frames the agent as an accessibility expert in WCAG compliance, inclusive design and assistive technology compatibility, tasked with auditing, finding barriers and advising on fixes.
It is one entry in a library of 2,658+ installable SKILL.md playbooks. The folder holds the SKILL.md plus a resources/implementation-playbook.md for detailed steps, tooling and remediation examples.
How the audit runs
- Confirm scope first: platforms, WCAG level, target pages and key user journeys.
- Run automated scans to collect baseline violations and coverage gaps.
- Perform manual checks of keyboard use, screen reader output, focus order and contrast.
- Map each finding to a WCAG criterion, a severity and a user impact.
- Give remediation steps, then re-test after the fixes.
When to use it, and when not to
- Use it to audit web or mobile experiences for WCAG compliance and to rank remediation work.
- Use it to set up ongoing accessibility testing, or to prepare compliance evidence for stakeholders.
- Skip it for a general UI design review with no accessibility scope.
- Skip it when you cannot reach the UI, design artifacts or content.
Honest limits
The skill's own limitations say its output does not replace environment specific validation, testing or expert review. It also tells the agent to stop and ask when inputs, permissions or success criteria are missing.
Who the skill is for
Best for
- Teams that need a repeatable audit checklist their agent can follow on web or mobile screens.
- Producing a prioritized findings list with criteria and severity attached.
- See also accessibility-review, another skill in the same area.
Not for
- A signed compliance opinion. Treat the output as a working audit, not a certificate.
- Fixing code in one pass. For fix focused guidance, see fixing-accessibility.
Use it with UiChemy
Audit the design or the build before conversion. If you design in Figma and convert with UiChemy Figma to WordPress, or build pages in UiChemy Composer, rerun the keyboard and contrast checks on the resulting WordPress page. Click Get Started on uichemy.com. For a code level pass, see web-accessibility-skill.
How to install Accessibility Compliance Audit Skill: A WCAG Audit Routine
npm exec --yes --ignore-scripts [email protected] -- agentic-awesome-skills --release 19.0.1 --path .agents/skills --skills accessibility-compliance-accessibility-audit --dry-runPreview the install
Run the command above. It is the README's direct installer form for chosen skill IDs, with this skill's ID filled in and a dry run so nothing is written yet.
Apply it
Review the preview, then repeat the same command without --dry-run. The README example targets .agents/skills, and other hosts use their own paths or flags listed in its table.
Or use AAS Core
The README also describes a local MCP for Codex or Claude that searches the catalog and records the skills the agent selects. Follow the host guide under docs/users.
Ask for an audit
Tell the agent the platforms, WCAG level, pages and user journeys, then ask it to audit using the skill. It should confirm scope before it scans.
Check that it loaded
Check that a folder named accessibility-compliance-accessibility-audit now sits under the path you chose, with SKILL.md and resources/implementation-playbook.md. Then ask for an audit and see that the agent confirms scope first.
Key features
- Expert role promptThe description sets the agent up as an accessibility expert in WCAG compliance, inclusive design and assistive technology compatibility.
- Scope confirmationBefore testing, the agent confirms platforms, WCAG level, target pages and key user journeys, so the audit has clear edges.
- Automated baselineAutomated scans collect baseline violations and coverage gaps, which tell you what a tool can and cannot see.
- Manual verificationManual checks cover keyboard use, screen reader behavior, focus order and contrast, the areas scanners often miss.
- Findings with contextEach finding is mapped to a WCAG criterion, a severity and a user impact, which makes triage straightforward.
- Remediation and retestThe routine ends with remediation steps and a re-test after fixes, instead of stopping at a list of problems.
- Implementation playbookA bundled resources/implementation-playbook.md carries detailed audit steps, tooling and remediation examples for deeper work.
- Use and skip rulesExplicit guidance covers when to use the skill and when not to, such as a design review with no accessibility scope.
- Stated limitationsThe output is not a substitute for environment specific validation or expert review, and the agent stops to ask when success criteria are missing.
Frequently asked questions
What is the accessibility compliance audit skill?
It is a skill in the sickn33/agentic-awesome-skills library, listed as accessibility-compliance-accessibility-audit. It tells an AI coding agent to confirm scope, run automated scans, perform manual checks, map findings to WCAG criteria and severity, and give remediation steps with a re-test.
How do I install the accessibility compliance audit skill?
Use the README's direct installer form with the skill ID accessibility-compliance-accessibility-audit and a dry run first. Review the preview, then rerun without --dry-run. The README example installs into .agents/skills, and its host table lists other targets and flags.
Does the skill run an automated scanner by itself?
The SKILL.md instructs the agent to run automated scans to collect baseline violations, but it does not name a specific scanner. Tooling details sit in the implementation playbook it references, so read that file before choosing a given tool.
When should I not use this skill?
The skill lists three cases. Do not use it for a general UI design review with no accessibility scope, for requests unrelated to user experience or compliance, or when you cannot access the UI, design artifacts or content that need auditing.
Can the audit output serve as a compliance certificate?
No. The skill's limitations say the output is not a substitute for environment specific validation, testing or expert review. Use it to find and prioritize barriers, then confirm results with real assistive technology and, where required, a qualified auditor.
Which AI agents can use the accessibility compliance audit skill?
The repository README lists install routes for Claude Code, Cursor, Gemini CLI, Codex CLI, Antigravity, Kiro, GitHub Copilot, OpenCode, AdaL CLI and Autohand Code, plus a custom path. It adds that Core helps Codex or Claude search the catalog, so confirm your agent loads SKILL.md folders.
What is in the implementation playbook?
The SKILL.md says resources/implementation-playbook.md holds detailed audit steps, tooling and remediation examples, and tells the agent to open it when detailed procedures are required. This page does not describe its contents beyond that summary.
What license does the skill use?
The sickn33/agentic-awesome-skills repository is licensed under MIT according to GitHub. The skill's own frontmatter labels it risk safe and source community, which describes how the catalog classifies it rather than a guarantee about your environment.