scan-accessibility

Scan TSX files for WCAG 2.2 AA accessibility issues statically detectable in codebases.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/sncollective/snc-platform --skill scan-accessibility
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scan-accessibility
Source: https://github.com/sncollective/snc-platform/tree/main/.claude/skills/scan-accessibility
Command: npx skills add https://github.com/sncollective/snc-platform --skill scan-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The scan-accessibility skill identifies accessibility regressions and missing accessibility affordances that can be detected through static code analysis, reducing manual audits and helping teams prioritize WCAG 2.2 Level AA remediation work across a codebase.

Core Features & Use Cases

  • Rule library: A curated set of rules for common static-detectable WCAG 2.2 Level AA issues, including image alt text, form labels, heading hierarchy, semantic interactive elements, keyboard interaction, media alternatives, and SPA route announcements.
  • Per-rule references: Each rule includes rationale, examples, exceptions, and scope guidance to support developer remediation and code review.
  • Integration use case: Load as a rule library into the refactor-scan pipeline to produce per-file findings for apps/web TSX components, enabling triage, tracking, and targeted fixes during refactors.

Quick Start

Load the scan-accessibility rules into your refactor-scan pipeline and run it against apps/web/src to generate per-file WCAG 2.2 Level AA findings.

Frequently Asked Questions about scan-accessibility

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

FAQPage Schema
How do I scan React TSX components for WCAG 2.2 AA accessibility issues?

To scan React TSX components for WCAG 2.2 AA accessibility issues, load the scan-accessibility rules into a refactor-scan pipeline and run it against your apps/web/src directory to generate per-file findings for tracked remediation.

What static analysis checks are available for WCAG 2.2 Level AA compliance?

Static analysis checks for WCAG 2.2 Level AA compliance include detecting missing image alt text, form labels, heading hierarchy violations, semantic interactive patterns, keyboard interaction gaps, missing media captions, and SPA route announcement deficiencies.

Can I use static code analysis to find missing alt text and form labels in a monorepo?

Yes, you can use static code analysis to find missing alt text and form labels in a monorepo by applying file-scoped TSX analysis rules to route layouts and media components, flagging these specific WCAG 2.2 issues for remediation.

How do I integrate accessibility rule libraries into an existing code refactor pipeline?

Integrate accessibility rule libraries into a code refactor pipeline by loading them as a rule set that emits per-file findings, enabling triage and targeted fixes during monorepo refactoring workflows.

Does static accessibility scanning detect keyboard interaction gaps and SPA route announcements?

Static accessibility scanning detects keyboard interaction gaps and SPA route announcement deficiencies by analyzing code patterns, applying per-rule reference documentation to flag semantic interactive element issues.

What is the best way to triage WCAG 2.2 accessibility regressions during codebase refactoring?

The best way to triage WCAG 2.2 accessibility regressions during codebase refactoring is to generate per-file findings from static analysis, prioritizing tracked remediation for missing affordances like heading hierarchy and form labels.