This skill empowers Claude to conduct thorough accessibility testing of web applications. It leverages the accessibility-test-scanner plugin to pinpoint areas of non-compliance with accessibility standards and offers recommendations for remediation.
How It Works
Initiating the Scan: Claude invokes the a11y-scan command, triggering the accessibility-test-scanner plugin.
Performing the Audit: The plugin conducts a comprehensive audit, checking for WCAG 2.1/2.2 compliance, ARIA validation, keyboard navigation, and screen reader compatibility.
Generating a Report: The plugin generates a detailed report outlining accessibility issues found, along with recommendations for fixing them.
When to Use This Skill
This skill activates when you need to:
Evaluate a web application's compliance with WCAG 2.1 or WCAG 2.2 guidelines.
Identify ARIA antipatterns and ensure proper ARIA usage.
Test keyboard navigation and focus management.
Examples
Example 1: Checking WCAG Compliance
User request: "Run an accessibility scan on this webpage and tell me if it meets WCAG 2.1 AA standards."
The skill will:
Execute the a11y-scan command.
Provide a report detailing WCAG 2.1 AA compliance issues and recommendations.
Example 2: Validating ARIA Attributes
User request: "Check the ARIA attributes on this component for any errors or antipatterns."
The skill will:
Execute the a11y-scan command.
Provide a report highlighting ARIA validation issues and recommended fixes.
Best Practices
Specificity: Be specific in your requests (e.g., "WCAG 2.2 Level AA compliance" instead of just "accessibility").
Context: Provide the specific webpage or component to be scanned for accurate results.
Iteration: Use the scan results to iteratively improve accessibility and re-scan to verify fixes.
Integration
This skill can be used in conjunction with other tools for code editing and testing. For example, after identifying accessibility issues, Claude can use its coding skills to implement the recommended fixes.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: jeremylongshore-claude-code-plugins-plus-skills-accessib-23description: Overview4---56## Overview78This skill empowers Claude to conduct thorough accessibility testing of web applications. It leverages the `accessibility-test-scanner` plugin to pinpoint areas of non-compliance with accessibility standards and offers recommendations for remediation.910## How It Works11121. **Initiating the Scan**: Claude invokes the `a11y-scan` command, triggering the accessibility-test-scanner plugin.132. **Performing the Audit**: The plugin conducts a comprehensive audit, checking for WCAG 2.1/2.2 compliance, ARIA validation, keyboard navigation, and screen reader compatibility.143. **Generating a Report**: The plugin generates a detailed report outlining accessibility issues found, along with recommendations for fixing them.1516## When to Use This Skill1718This skill activates when you need to:19- Evaluate a web application's compliance with WCAG 2.1 or WCAG 2.2 guidelines.20- Identify ARIA antipatterns and ensure proper ARIA usage.21- Test keyboard navigation and focus management.2223## Examples2425### Example 1: Checking WCAG Compliance2627User request: "Run an accessibility scan on this webpage and tell me if it meets WCAG 2.1 AA standards."2829The skill will:301. Execute the `a11y-scan` command.312. Provide a report detailing WCAG 2.1 AA compliance issues and recommendations.3233### Example 2: Validating ARIA Attributes3435User request: "Check the ARIA attributes on this component for any errors or antipatterns."3637The skill will:381. Execute the `a11y-scan` command.392. Provide a report highlighting ARIA validation issues and recommended fixes.4041## Best Practices4243- **Specificity**: Be specific in your requests (e.g., "WCAG 2.2 Level AA compliance" instead of just "accessibility").44- **Context**: Provide the specific webpage or component to be scanned for accurate results.45- **Iteration**: Use the scan results to iteratively improve accessibility and re-scan to verify fixes.4647## Integration4849This skill can be used in conjunction with other tools for code editing and testing. For example, after identifying accessibility issues, Claude can use its coding skills to implement the recommended fixes.5051---52> Converted and distributed by [TomeVault](https://tomevault.io/claim/jeremylongshore) — claim your Tome and manage your conversions.53<!-- tomevault:4.0:skill_md:2026-04-11 -->
Run npx skillmds@latest add tomevault-io/jeremylongshore-claude-code-plugins-plus-skills-accessib-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Overview It is listed under Web & Frontend on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.