feat: add /a11y WCAG 2.1 AA accessibility audit skill#756
Open
Gonzih wants to merge 1 commit intogarrytan:mainfrom
Open
feat: add /a11y WCAG 2.1 AA accessibility audit skill#756Gonzih wants to merge 1 commit intogarrytan:mainfrom
Gonzih wants to merge 1 commit intogarrytan:mainfrom
Conversation
Adds a new /a11y skill for WCAG 2.1 AA compliance auditing using real browser testing plus static source analysis. Covers the 6 most common accessibility failure categories: - Tab order and keyboard navigation (focus traps, zero-size elements) - Images and non-text content (missing alt, decorative vs meaningful) - Form labels and error handling (unlabeled inputs, missing aria-describedby) - Heading hierarchy and landmark structure (h1→h3 skips, missing <main>) - Color contrast sampling (4.5:1 for normal text, 3:1 for large/UI) - ARIA usage (buttons/links without accessible names, invalid roles) Reports findings by WCAG criterion code and severity (CRITICAL/HIGH/ MEDIUM/LOW/PASS). With --fix, applies minimal fixes for each confirmed issue and re-verifies. With --code, runs static grep analysis only. This fills the gap between /cso (security audit) and /qa (functional testing): neither covers accessibility systematically. /a11y completes the quality-assurance triangle. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new
/a11yskill for WCAG 2.1 AA accessibility compliance auditing using real browser testing (via the browse daemon) plus static source analysis.6 check categories:
aria-describedbyon errors<main>, duplicate navsSeverity tiers: CRITICAL (blocks users) / HIGH (significantly degrades) / MEDIUM (reduces quality) / LOW (minor)
Modes:
/a11y <url>— full browser audit/a11y <url> --fix— audit + apply minimal fixes per finding with re-verification/a11y --code— static grep analysis only (no browser required)Why
gstack already has
/cso(security audit) and/qa(functional QA). Neither covers accessibility systematically. This fills the third leg of the quality triangle.Legal context: WCAG 2.1 AA is now required by ADA, EAA (EU), and referenced in CVAA. Teams that skip accessibility until launch pay 10× more to fix it post-launch.
Design notes
/qaand/canaryTest plan
bun run gen:skill-docsgeneratesa11y/SKILL.mdwithout errors/a11y https://example.comto verify Phase 2 browser checks work end-to-end/a11y --codeon a project with known missing alt tags to verify static grep🤖 Generated with Claude Code