Slash Command

A11y Scan

Scan for accessibility issues with WCAG 2.1/2.2 compliance and screen reader

Type: Slash Command
Repository: jeremylongshore/tons-of-skills-marketplace
GitHub stars: 2.8k
License: MIT
Repo last updated: Sep 27, 2026
Source file: plugins/testing/accessibility-test-scanner/commands/a11y-scan.md

What A11y Scan is

A11y Scan is a slash command published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

A11y Scan gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install A11y Scan

Claude Code

Download a11y-scan.md from the repository.
Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
Run it by typing / followed by its name.

Claude Cowork

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
In Customize → Skills, click +, then upload the ZIP.
Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/testing/accessibility-test-scanner/commands/a11y-scan.md, shared under the repository's MIT license. Read the full file on GitHub.

Comprehensive accessibility testing with WCAG 2.1/2.2 validation, ARIA compliance, keyboard navigation testing, and screen reader compatibility checks.

What You Do

WCAG Compliance Scanning

Check WCAG 2.1 Level A, AA, AAA compliance
Validate WCAG 2.2 new success criteria
Generate detailed compliance reports

ARIA Validation

Verify proper ARIA usage
Detect ARIA antipatterns
Validate landmark regions and roles

Keyboard Navigation

Test tab order and focus management
Verify keyboard shortcuts
Check focus indicators

Screen Reader Testing

Generate screen reader test scenarios
Validate semantic HTML
Check alt text and labels

Color Contrast

Validate color contrast ratios
Test for color blindness
Suggest accessible color palettes

Usage Pattern

When invoked, you should:

Identify pages/components to test
Run automated accessibility audits (axe-core, Pa11y, Lighthouse)
Analyze results against WCAG criteria
Prioritize issues by severity and impact
Generate fix recommendations with code examples
Create accessibility test suite

Output Format

## Accessibility Audit Report

### Compliance Level: [A / AA / AAA]
**Pages Scanned:** [N]
**Issues Found:** [Critical: N, Serious: N, Moderate: N, Minor: N]

### Critical Issues (WCAG Level A)

#### Issue: [Description]
**WCAG Criterion:** [X.X.X - Name]
**Impact:** [High/Medium/Low]
**Affected Elements:** [N]
**Location:** `[selector or file:line]`

**Problem:**
[Detailed explanation]

**Fix:**

[problematic code]

[corrected code]


**Testing:**

- [ ] Screen reader: [how to verify]
- [ ] Keyboard: [how to verify]

### ARIA Issues

- Missing labels: [N]
- Invalid roles: [N]
- Incorrect relationships: [N]

### Keyboard Navigation

 Tab order: Logical
 Focus indicators: Missing on [N] elements
 Keyboard traps: Found [N]
…

Testing Tools Integration

axe-core (automated testing)
Pa11y (command-line testing)
Lighthouse accessibility audit
WAVE browser extension
NVDA/JAWS screen reader scripts
jest-axe / cypress-axe for automated tests

Before you install

Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
Try it in a test project or a copy of your files before pointing it at real work.
Pin the version you tested, and review changes before updating.
Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is A11y Scan?

A11y Scan is a slash command for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Scan for accessibility issues with WCAG 2.1/2.2 compliance and screen reader

How do I install A11y Scan in Claude Code?

Download a11y-scan.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use A11y Scan in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is A11y Scan safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.