Menu
Deep WCAG 2.1 criterion-by-criterion accessibility evaluation
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Creates well-structured Claude Skills with proper YAML frontmatter, clear instructions, and supporting files. Activates when the user wants to create a new skill, add capabilities to their AI assistant, encode team preferences, or structure any reusable instruction set. Covers the full lifecycle from intent capture through writing, testing, and refinement.
Shows all available skills, platform support, common workflows, and troubleshooting for the @terrazul/assistant-creator package. Activates when the user asks for help, wants to know what's available, or needs guidance on using the package.
Interactive wizard to set up MCP server credentials in your shell environment (~/.zshenv, ~/.bashrc, etc.). Activates when the user needs to configure API keys, tokens, or environment variables for MCP servers, or after adding new MCP integrations that require authentication.
Searches mcp.so marketplace for MCP servers and configures them for Claude, Codex, or Gemini. Use when user wants to add external tool integrations, find MCP servers, or configure model context protocol.
Converts Claude SKILL.md files to Gemini-compatible format. Use when user wants to use a Claude skill with Gemini CLI, or needs to make skills cross-platform compatible.
Create well-formed Claude agents with proper YAML frontmatter, system prompts, and examples. Use when user wants to create a new agent, customize Claude behavior, or needs help structuring an agent definition.
| name | wcag-compliance |
| description | Deep WCAG 2.1 criterion-by-criterion accessibility evaluation |
Perform thorough WCAG 2.1 accessibility evaluation with criterion-by-criterion testing, compliance documentation, and remediation guidance.
25 criteria - Essential accessibility, basic barrier removal.
13 additional criteria - Recommended target for most websites.
23 additional criteria - Maximum accessibility, not always achievable.
Clarify:
Use Puppeteer to check:
Perform hands-on testing:
For each WCAG criterion, document:
### [X.X.X Criterion Name] - Level [A/AA/AAA]
**Status**: Pass / Fail / Not Applicable
**Conformance Requirement**: [Official WCAG text]
**Testing Method**: [How tested]
**Evidence**:
- [Screenshot/observation]
**Issues Found** (if any):
1. [Location]: [Issue description]
- Impact: [Who affected]
- Fix: [Code example]
**Notes**: [Additional context]
Generate formal compliance documentation.
# WCAG 2.1 Compliance Report
**Organization**: [Name]
**Website**: [URL]
**Conformance Target**: Level [A/AA/AAA]
**Report Date**: [Date]
**Review Period**: [Date range]
## Conformance Statement
[Organization] is committed to ensuring digital accessibility for people with disabilities. We have assessed [website] against WCAG 2.1 Level [AA] criteria.
### Conformance Status
| Level | Criteria | Passed | Failed | N/A |
|-------|----------|--------|--------|-----|
| A | 25 | X | X | X |
| AA | 13 | X | X | X |
| AAA | 23 | X | X | X |
**Overall Conformance**: [Fully Conformant / Partially Conformant / Non-Conformant]
## Executive Summary
### Strengths
- [What works well]
### Areas for Improvement
- [What needs work]
### Critical Issues
1. [Critical issue 1]
2. [Critical issue 2]
## Detailed Criteria Assessment
### Principle 1: Perceivable
#### 1.1 Text Alternatives
##### 1.1.1 Non-text Content (A)
**Status**: [Pass/Fail/N/A]
[Details...]
[Continue for each criterion...]
### Principle 2: Operable
[Criteria...]
### Principle 3: Understandable
[Criteria...]
### Principle 4: Robust
[Criteria...]
## Issues Summary
### By Severity
| Severity | Count | Impact |
|----------|-------|--------|
| Critical | X | Blocks access |
| Serious | X | Major barrier |
| Moderate | X | Inconvenience |
| Minor | X | Enhancement |
### By Principle
| Principle | Issues |
|-----------|--------|
| Perceivable | X |
| Operable | X |
| Understandable | X |
| Robust | X |
## Remediation Plan
### Immediate (1-2 weeks)
| Issue | Criterion | Priority | Effort |
|-------|-----------|----------|--------|
| [Issue] | [X.X.X] | Critical | Low |
### Short-term (1 month)
[Table...]
### Long-term (3+ months)
[Table...]
## Testing Methodology
### Tools Used
- Puppeteer for automated testing
- Manual keyboard testing
- Color contrast analysis
- ARIA validation
### Pages Tested
1. [URL 1]
2. [URL 2]
### Testing Environment
- Browser: [Browser/version]
- Screen size: [Dimensions]
- Assistive technology: [If used]
## Certification
This accessibility audit was conducted by [Name/Organization] on [Date].
**Auditor**: [Name]
**Credentials**: [If applicable]
**Contact**: [Email]
---
*This report represents the accessibility status at the time of testing. Website updates may affect conformance.*
Use the wcag-compliance skill to audit [URL] at Level AA.
Document all criteria for compliance reporting.
Focus on forms and navigation components.