Help us improve
Share bugs, ideas, or general feedback.
Scans web components or project for WCAG 2.1 accessibility violations, reporting issues by A/AA/AAA levels with file locations, criterion numbers, and fix code snippets.
npx claudepluginhub rohitg00/awesome-claude-code-toolkit --plugin accessibility-checkerHow this command is triggered — by the user, by Claude, or both
Slash command
/accessibility-checker:a11y-scanThe summary Claude sees in its command listing — used to decide when to auto-load this command
Scan web application components for accessibility violations against WCAG guidelines. ## Steps 1. Identify the target: component file, page, or entire project. 2. Scan for common WCAG 2.1 violations: - **Perceivable**: Images without alt text, videos without captions, low color contrast. - **Operable**: Non-keyboard-accessible elements, missing focus indicators, no skip links. - **Understandable**: Missing form labels, no error descriptions, inconsistent navigation. - **Robust**: Invalid HTML, missing ARIA roles, incorrect heading hierarchy. 3. Check component-level issues: ...
/a11y-scanScans pages or components for WCAG 2.1/2.2 accessibility issues, ARIA errors, keyboard navigation, screen reader compatibility, and color contrast. Produces markdown audit report with prioritized fixes and code examples.
/run-auditRuns WCAG 2.1 accessibility audit (AA default) on a URL or component via axe-core and manual checks for keyboard nav, ARIA, contrast, forms, media. Outputs prioritized report with remediation.
/a11y-auditAudits accessibility for live URLs, UI components, or screenshots against WCAG A/AA/AAA standards, generating a markdown report with tiered issues and fixes.
/accessibility-auditAudits UI code for WCAG 2.1/2.2 compliance at A/AA/AAA level, identifies issues across perceivable/operable/etc. criteria, and provides remediation. Accepts file/component path or prompts for target.
/a11yAudits accessibility with WCAG 2.1 AA/AAA using Axe, Pa11y, Lighthouse scanners; analyzes color contrast, keyboard navigation, screen readers. Outputs Markdown report, auto-fixes, Git commits. Supports flags for focus areas.
Share bugs, ideas, or general feedback.
Scan web application components for accessibility violations against WCAG guidelines.
htmlFor/id or wrapping.aria-describedby.aria-required.Accessibility Scan: <scope>
Violations: <N> (A: <n>, AA: <n>, AAA: <n>)
WCAG A (must fix):
- <file>:<line> - <element> missing alt text (1.1.1)
- <file>:<line> - <element> not keyboard accessible (2.1.1)
WCAG AA (should fix):
- <file>:<line> - contrast ratio 3.2:1, needs 4.5:1 (1.4.3)
Passing:
- Heading hierarchy is correct
- Language attribute is set