accessibility-audit
This skill performs rapid accessibility assessments on web pages and UI components to catch compliance gaps before deployment. It helps teams integrate accessibility testing into their release workflows, ensuring WCAG standards are met without slowing down development cycles.
accessibility-audit performs rapid accessibility assessments on web pages and UI components to catch compliance gaps before deployment. You can run it as a quick smoke test in your pre-release workflow to verify that your page meets basic accessibility standards without requiring extensive manual testing or slowing down your development cycle.
AI-generated summary based on this skill's SKILL.md
Install
NickCrew/Claude-Cortex/accessibility-audit · repository language: Python
git clone https://github.com/NickCrew/Claude-Cortex
cp -r Claude-Cortex/skills/accessibility-audit ~/.claude/skills/accessibility-auditFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How can I run a quick accessibility check on a page or component before release?
accessibility-audit performs rapid accessibility assessments on web pages and UI components to catch compliance gaps before deployment. You can run it as a quick smoke test in your pre-release workflow to verify that your page meets basic accessibility standards without requiring extensive manual testing or slowing down your development cycle.
Does accessibility-audit verify WCAG 2.2 AA compliance and identify accessibility issues?
Yes, accessibility-audit is designed to verify WCAG 2.2 AA compliance and identify accessibility issues across your pages and components. The skill helps teams integrate accessibility testing into their release workflows, ensuring that WCAG standards are met and potential compliance gaps are caught early in the development process.
Can accessibility-audit test keyboard navigation and screen reader compatibility?
accessibility-audit includes testing for keyboard navigation and screen reader compatibility as part of its comprehensive accessibility assessment. This helps ensure that your pages are navigable via keyboard alone and work correctly with assistive technologies, which are critical requirements for accessible web experiences.
What accessibility-audit checks does it perform for semantic HTML, labels, and contrast ratios?
accessibility-audit validates semantic HTML structure, proper labeling of form elements and interactive components, and contrast ratios to ensure they meet WCAG standards. These checks help identify common accessibility issues that can prevent users with disabilities from effectively using your website or application.
How can accessibility-audit help with accessibility regression testing in pull requests?
accessibility-audit can be integrated into your pull request review process to detect accessibility regressions before code is merged. By running the tool on changes, you can catch new accessibility issues introduced by recent modifications and ensure that existing accessible features remain functional.
Is accessibility-audit available under an open-source license?
Yes, accessibility-audit is released under the MIT license, making it freely available for both commercial and personal use. The open-source nature of the tool allows teams to integrate it into their accessibility testing workflows without licensing restrictions.
SKILL.md
rendered from the published skill — quoted content, verbatim
Accessibility Audit Skill
Fast, high-signal accessibility triage for pages, components, or PRs. This is a lightweight check, not a full compliance audit.
When to Use This Skill
- Quick accessibility triage before releases
- Component-level a11y verification
- PR review for accessibility regressions
- Smoke checks for WCAG compliance
- Validating keyboard navigation on new features
Quick Audit Checklist
1. Automated Snapshot (Recommended)
Run one of these automated tools first:
- npx @axe-core/cli <url> - Quick axe-core scan
- npx pa11y <url> --standard WCAG2AA - Pa11y audit
- Lighthouse Accessibility score (Chrome DevTools > Lighthouse > Accessibility)
2. Keyboard Basics
| Check | Expected |
|---|---|
| All interactive elements reachable via Tab | Yes |
| Focus indicator always visible | Yes |
| No keyboard traps |
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
skills/accessibility-audit/SKILL.md