Slash Command

/a11y-scan

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.

Html

Css

Javascript

accessibility

frontend

npx claudepluginhub rohitg00/awesome-claude-code-toolkit --plugin accessibility-checker

Popularity

Parent stars

1,716

Parent forks

535

Invocation

How this command is triggered — by the user, by Claude, or both

Slash command

/accessibility-checker:a11y-scan

Model invocable

No pre-commands

Context Preview

The 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:
  ...

Command Content

49 lines · ~465 tokens

Other plugins with /a11y-scan

/a11y-scan

2.2k

Scans 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.

accessibility-test-scanner

/run-audit

1.7k

Runs 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-audit

/a11y-audit

Audits accessibility for live URLs, UI components, or screenshots against WCAG A/AA/AAA standards, generating a markdown report with tiered issues and fixes.

design-ops

/accessibility-audit

35.7k

Audits 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.

ui-design

/a11y

Audits 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.

godmode

Stats

LanguageJavaScript

Parent stars1,716

Parent forks535

MaintenanceFair

Last CommitFeb 4, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

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: ...

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

Scan web application components for accessibility violations against WCAG guidelines.

Steps

Identify the target: component file, page, or entire project.
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.
Check component-level issues:
- Interactive elements (buttons, links) without accessible names.
- Custom components missing ARIA roles and states.
- Dynamic content updates without live region announcements.
- Modal dialogs without focus trapping.
Check form accessibility:
- Labels associated with inputs via htmlFor/id or wrapping.
- Error messages linked to inputs via aria-describedby.
- Required fields marked with aria-required.
Classify findings by WCAG level (A, AA, AAA) and severity.
Provide specific fix instructions for each violation.

Format

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

Rules

Prioritize WCAG A violations (legal compliance baseline).
Provide the specific WCAG criterion number for each violation.
Include fix code snippets, not just descriptions.
Check both static HTML/JSX and dynamically generated content.
Test with screen reader considerations (not just automated rules).

/a11y-scan

Popularity

Invocation

Context Preview

Command Content

Other plugins with /a11y-scan

Help us improve

Help us improve

Find plugins for your project

/a11y-scan

Popularity

Invocation

Context Preview

Command Content

Steps

Format

Rules

Other plugins with /a11y-scan

Help us improve

Steps

Format

Rules