wcag-audit-patterns
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.
86
71%
Does it follow best practices?
Impact
97%
1.04xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/accessibility-compliance/skills/wcag-audit-patterns/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that follows best practices closely. It uses third person voice, lists specific concrete capabilities, includes an explicit 'Use when' clause with natural trigger terms, and occupies a clearly distinct niche around WCAG accessibility auditing. It closely mirrors the structure and quality of the good examples in the rubric.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'automated testing', 'manual verification', 'remediation guidance', 'auditing websites', 'fixing WCAG violations', 'implementing accessible design patterns'. These are distinct, concrete capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance) and 'when' (explicit 'Use when' clause covering auditing, fixing violations, and implementing accessible design patterns). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'WCAG 2.2', 'accessibility audits', 'WCAG violations', 'accessible design patterns', 'auditing websites for accessibility'. These cover the primary terms a user would naturally use when seeking accessibility help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused on WCAG 2.2 accessibility auditing. The specific mention of WCAG, accessibility audits, and accessible design patterns creates a clear, narrow domain unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a reformatted WCAG 2.2 specification with code examples bolted on. While the remediation patterns and automated testing code are genuinely actionable and useful, the bulk of the content is reference material Claude already knows (WCAG criteria, POUR principles, conformance levels). The massive size (~400+ lines) with no progressive disclosure makes it extremely token-inefficient, and the lack of an explicit end-to-end audit workflow with validation checkpoints weakens its practical utility as a skill.
Suggestions
Drastically reduce the inline WCAG checklist to only the most commonly missed or tricky criteria, and move the full checklist to a separate CHECKLIST.md file referenced from the main skill.
Remove the POUR principles explanation, conformance levels table, and common violations tree — Claude already knows WCAG fundamentals. Focus the main file on the audit workflow and remediation patterns.
Add an explicit end-to-end audit workflow with numbered steps and validation checkpoints: e.g., 1) Run automated scan → 2) Categorize violations by severity → 3) Manual keyboard/screen reader testing → 4) Generate report → 5) Apply fixes → 6) Re-scan to verify.
Split remediation patterns and automated testing setup into separate referenced files (e.g., REMEDIATION.md, AUTOMATED-TESTING.md) to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Reproduces the entire WCAG 2.2 specification as a checklist, which is reference material Claude already knows. The POUR principles explanation, conformance level table, and exhaustive criterion-by-criterion listing add massive token cost with minimal novel instructional value. Much of this is a reformatted copy of publicly available WCAG documentation. | 1 / 3 |
Actionability | Provides fully executable code examples throughout: axe-core integration with Playwright, CLI commands, concrete HTML before/after remediation patterns, CSS fixes with specific contrast values, and a complete keyboard-accessible custom element implementation. All examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | The audit checklist provides a clear sequence organized by POUR principles, and the automated testing section gives concrete steps. However, there's no explicit audit workflow with validation checkpoints (e.g., run automated scan → triage results → manual verification → remediation → re-test cycle). The process of conducting an actual audit end-to-end is implicit rather than explicitly sequenced with feedback loops. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. The entire WCAG checklist, all remediation patterns, automated testing code, and best practices are inlined in a single massive document. This content desperately needs splitting — the checklist, remediation patterns, and automated testing setup should each be separate referenced files. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (549 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- wshobson/agents
- Commit
112197c
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.