cc-a11y

Identify and remediate accessibility issues in TSX/JSX/HTML/CSS files.

1|Updated Feb 17, 2021
One-click install
npx skills add https://github.com/concord-consortium/dev-templates --skill cc-a11y
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-a11y
Source: https://github.com/concord-consortium/dev-templates/tree/main/claude/skills/cc-a11y
Command: npx skills add https://github.com/concord-consortium/dev-templates --skill cc-a11y

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Claude-a11y skill automates the identification and remediation of accessibility issues across Claude-driven codebases, reducing manual audits and accelerating compliant releases.

Core Features & Use Cases

  • Automatically analyzes TSX/JSX/HTML/CSS for WCAG-related accessibility issues.
  • Produces fixes suggestions and formal reports for single files, feature branches, or entire repositories.
  • Use cases include pre-merge branch audits and repository-wide accessibility summaries.

Quick Start

Run /cc-a11y review to start an automated accessibility audit on the target file or repository.

Frequently Asked Questions about cc-a11y

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an automated accessibility review on my TSX and JSX files?

You can automate accessibility reviews on TSX and JSX files by running an audit command that analyzes your codebase for WCAG issues and generates formal reports with suggested fixes. The tool works on single files, feature branches, or entire repositories.

What is automated WCAG issue remediation for HTML and CSS codebases?

Automated WCAG remediation identifies accessibility violations in HTML and CSS codebases and produces deterministic fixes. It applies branch safety checks and ignore rules to ensure safe, reproducible results without manual auditing.

Can I use this accessibility audit tool on a feature branch before merging?

Yes, you can use this accessibility audit tool on a feature branch before merging. It performs branch safety checks and generates issue reports and deterministic fixes for the files within that specific branch to accelerate compliant releases.

Does the accessibility review process generate suggested code fixes?

Yes, the accessibility review process generates suggested fixes for identified issues. It produces formal reports and applies deterministic fixes to ensure the remediation results are safe and reproducible across your codebase.

What are the limitations of automating accessibility fixes across a repository?

Automating accessibility fixes across a repository is limited by its deterministic nature, meaning it applies safe, reproducible fixes. It relies on ignore rules and branch safety checks, which may require manual review for complex WCAG compliance scenarios.