web-accessibility
npx machina-cli add skill aiskillstore/marketplace/web-accessibility --openclawWeb 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
- WCAG Compliance: Assesses compliance with WCAG 2.1/2.2 (A, AA, AAA)
- Screen Reader Testing: Validates semantic HTML and ARIA usage
- Keyboard Navigation: Tests keyboard accessibility and focus management
- Color Contrast: Analyzes color contrast ratios
- Alternative Text: Evaluates alt text and media accessibility
- Form Accessibility: Validates form labels and error handling
How to Use
Audit Accessibility
Conduct a WCAG compliance audit of this website
Test keyboard navigation and screen reader compatibility
Specific Analysis
Check color contrast ratios and suggest improvements
WCAG 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
```html
<!-- 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
Source
git clone https://github.com/aiskillstore/marketplace/blob/main/skills/89jobrien/web-accessibility/SKILL.mdView on GitHub Overview
Provides comprehensive web accessibility analysis and remediation, prioritizing WCAG 2.1/2.2 compliance, screen reader compatibility, and inclusive design. It evaluates semantic HTML, ARIA usage, color contrast, and form accessibility to help teams ship accessible sites.
How This Skill Works
The skill performs audits against WCAG 2.1/2.2 (A, AA, AAA) and tests key areas such as keyboard navigation, focus management, and screen reader output. It analyzes color contrast, alt text, and form labels, then generates concrete remediation recommendations and verification steps.
When to Use It
- Conducting WCAG compliance audits
- Testing screen reader compatibility
- Validating keyboard navigation and focus management
- Analyzing color contrast
- Remediating accessibility issues in existing sites
Quick Start
- Step 1: Run a WCAG compliance audit across the target site (WCAG 2.1/2.2, A/AA/AAA).
- Step 2: Validate semantic HTML, ARIA usage, keyboard navigation, and color contrast.
- Step 3: Implement fixes and re-run audits to verify accessibility improvements.
Best Practices
- Use semantic HTML and proper landmark roles
- Apply ARIA only where necessary
- Ensure complete keyboard accessibility and visible focus indicators
- Meet WCAG contrast ratios and scalable text
- Test with screen readers and keyboard-only navigation early and often
Example Use Cases
- WCAG Audit: assessing a homepage for Level A/AA issues and proposing fixes
- Missing Alt Text remediation for hero images and media
- Form accessibility improvements with proper labels and error handling
- Color contrast fixes on call-to-action buttons to reach 4.5:1 or higher
- Navigation focus management enhancements across multiple pages