
Qe A11y Ally
Comprehensive WCAG accessibility auditing with multi-tool testing (axe-core + pa11y +...
Install
npx skills add proffesor-for-testing/agentic-qe --skill qe-a11y-ally -g -a claude-code -y- Repository
- proffesor-for-testing/agentic-qe521
- Category
- Design
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Comprehensive WCAG accessibility auditing with multi-tool testing (axe-core + pa11y + Lighthouse), TRUE PARALLEL execution with Promise.allSettled, graceful degradation, retry with backoff, context-aware remediation, learning integration, and video accessibility. Uses 3-tier browser cascade: Vibium → agent-browser → Playwright+Stealth.
/a11y-ally - Comprehensive Accessibility Audit
<default_to_action> When this skill is invoked with a URL, Claude executes ALL steps automatically without waiting for user prompts between steps.
THIS IS AN LLM-POWERED SKILL
The value of this skill is Claude's intelligence, not just running automated tools:
| Automated Tools Do | Claude (This Skill) Does |
|---|---|
| Flag "button has no name" | Analyze context: icon class, parent element, nearby text → generate "Add to wishlist" |
| Flag "image missing alt" | Use Vision to see the image → describe actual content |
| Flag "video has no captions" | Download video, extract frames, analyze each frame with Vision → generate real captions |
| Output generic templates | Generate context-specific, copy-paste ready fixes |
IF YOU SKIP THE LLM ANALYSIS, THIS SKILL HAS NO VALUE.
EXECUTION MODEL
CLAUDE EXECUTES ALL STEPS WITHOUT STOPPING.
Do NOT wait for user prompts between steps. Execute the full pipeline:
- Data Collection: Run multi-tool scan (axe-core, pa11y, Lighthouse) via Bash
- LLM Analysis: Read results and analyze context for each violation
- Vision Pipeline: If videos detected → download → extract frames → Read each frame → describe
- Intelligent Remediation: Generate context-specific fixes using your reasoning
- Generate Reports: Write all output files to
docs/accessibility-scans/{page-slug}/
WRONG:
Claude: "I found 5 violations. Should I analyze them?"
User: "Yes"
Claude: "I see a video. Should I run the video pipeline?"
User: "Yes"
RIGHT:
Claude: [Runs scan] → [Analyzes violations] → [Downloads video] → [Extracts frames] →
[Reads each frame with Vision] → [Generates captions] → [Writes all files]
"Audit complete. Generated 4 files in docs/accessibility-scans/example/"


