Web Accessibility
- 32 installs
- 4 repo stars
- Updated April 11, 2026
- 89jobrien/steve
web-accessibility is a Claude Code skill for WCAG compliance audits, screen reader testing, and inclusive-design remediation.
About
web-accessibility is a Claude Code skill for web accessibility analysis and remediation focused on WCAG compliance. It audits against WCAG 2.1/2.2 levels A, AA, and AAA, tests screen reader and keyboard support, and checks color contrast and form accessibility. Developers use it to audit a site's accessibility and fix issues. It provides concrete before-and-after remediation examples.
- Conducts WCAG 2.1/2.2 compliance audits at levels A, AA, and AAA
- Tests screen reader compatibility, keyboard navigation, and color contrast
- Validates form labels, alt text, and ARIA usage with remediation examples
Web Accessibility by the numbers
- 32 all-time installs (skills.sh)
- Ranked #1,443 of 2,245 Frontend Development skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
web-accessibility capabilities & compatibility
- Capabilities
- accessibility audit · wcag compliance · contrast analysis
- Use cases
- ui design · web design · code review
What web-accessibility says it does
This skill provides comprehensive web accessibility analysis and remediation, focusing on WCAG compliance, screen reader compatibility, and inclusive design.
Color contrast ratio 4.5:1 (text)
npx skills add https://github.com/89jobrien/steve --skill web-accessibilityAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 32 |
|---|---|
| repo stars | ★ 4 |
| Last updated | April 11, 2026 |
| Repository | 89jobrien/steve ↗ |
What it does
Audit a website for WCAG 2.1/2.2 compliance and remediate screen reader, keyboard, contrast, and form accessibility issues.
Who is it for?
Frontend developers auditing and remediating web accessibility against WCAG 2.1/2.2.
When should I use this skill?
Conducting WCAG audits, testing screen reader compatibility, validating keyboard navigation, or ensuring inclusive design.
What you get
A WCAG audit with severity-ranked issues and concrete remediation code.
- A WCAG accessibility audit
- Severity-ranked issues
- Remediation code examples
By the numbers
- WCAG 2.1/2.2 levels A, AA, AAA
- AA contrast ratio 4.5:1, AAA 7:1
Files
Web Accessibility
This skill provides comprehensive web accessibility analysis and remediation, focusing on WCAG compliance, screen reader compatibility, and inclusive design.
When to Use This Skill
- When conducting WCAG compliance audits
- When testing screen reader compatibility
- When validating keyboard navigation
- When analyzing color contrast
- When ensuring inclusive design
- When remediating accessibility issues
What This Skill Does
1. WCAG Compliance: Assesses compliance with WCAG 2.1/2.2 (A, AA, AAA) 2. Screen Reader Testing: Validates semantic HTML and ARIA usage 3. Keyboard Navigation: Tests keyboard accessibility and focus management 4. Color Contrast: Analyzes color contrast ratios 5. Alternative Text: Evaluates alt text and media accessibility 6. Form Accessibility: Validates form labels and error handling
How to Use
Audit Accessibility
Conduct a WCAG compliance audit of this websiteTest keyboard navigation and screen reader compatibilitySpecific Analysis
Check color contrast ratios and suggest improvementsWCAG Standards
Level A (Minimum)
- Text alternatives for images
- Captions for videos
- Keyboard accessible
- No seizure-inducing content
- Proper heading structure
Level AA (Recommended)
- Color contrast ratio 4.5:1 (text)
- Resizable text up to 200%
- Multiple navigation methods
- Consistent navigation
- Error identification
Level AAA (Enhanced)
- Color contrast ratio 7:1 (text)
- Sign language interpretation
- Extended audio descriptions
- No timing restrictions
- Context-sensitive help
Examples
Example 1: WCAG Audit
Input: Audit homepage for WCAG compliance
Output:
## Accessibility Audit: Homepage
### Critical Issues (Level A)
**1. Missing Alt Text**
- **Location**: Hero image (line 45)
- **Issue**: Image has no alt attribute
- **Fix**: Add descriptive alt text<!-- Before --> <img src="hero.jpg">
<!-- After --> <img src="hero.jpg" alt="Team collaborating on project management dashboard">
**2. Missing Form Labels**
- **Location**: Email input (line 78)
- **Issue**: Input has no associated label
- **Fix**: Add proper label
<!-- Before --> <input type="email" id="email">
<!-- After --> <label for="email">Email Address</label> <input type="email" id="email" aria-required="true">
### Warnings (Level AA)
**3. Color Contrast**
- **Location**: Button text (line 92)
- **Issue**: Contrast ratio 3.2:1 (needs 4.5:1)
- **Fix**: Darken text color
Best Practices
Accessibility Guidelines
1. Semantic HTML: Use proper HTML elements 2. ARIA When Needed: Use ARIA for complex interactions 3. Keyboard Access: Ensure all functionality is keyboard accessible 4. Color Contrast: Meet WCAG contrast requirements 5. Testing: Test with screen readers and keyboard only
Related Use Cases
- WCAG compliance audits
- Screen reader testing
- Keyboard navigation validation
- Color contrast analysis
- Inclusive design implementation
Related skills
Vercel React Best PracticesAutomatically apply Vercel’s official React and Next.js performance rules during code generation and review.587k29.6kVercel Composition PatternsGenerate and refactor React components that stay maintainable as complexity grows without boolean prop explosion.267k29.6k
ShadcnAdd, compose, search, fix, and style production-grade React components directly from source without leaving their editor.257k120k
Develop UserscriptsCorrectly write, debug, and package userscripts for Tampermonkey and ScriptCat with proper metadata, GM APIs, and runtime decisions.224k72
Minimalist UiGenerate clean, editorial-style web interfaces with warm monochrome palettes, typographic hierarchy, bento grids and flat components that feel premium and utilita212k69.4kImage To CodeConvert high-fidelity design images into production-ready, visually accurate frontend code that avoids generic AI design pitfalls.177k69.4kFAQ
Which WCAG versions does it cover?
WCAG 2.1/2.2 across levels A, AA, and AAA.
What contrast ratio is required at AA?
A color contrast ratio of 4.5:1 for text.