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 an excellent 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' (Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns) with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'accessibility', 'WCAG', 'audits', 'WCAG violations', 'accessible design patterns', 'auditing websites'. Covers both the standard name (WCAG 2.2) and common terms like 'accessibility'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around WCAG 2.2 accessibility auditing. The specific mention of WCAG 2.2, accessibility audits, and violations makes it unlikely to conflict with general web development or design 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 comprehensive WCAG 2.2 reference document rather than a focused skill for Claude. While it excels at providing concrete, executable code examples and remediation patterns, it is far too verbose—reproducing standard WCAG criteria that Claude already knows—and lacks a clear audit workflow with validation checkpoints. The content desperately needs restructuring with progressive disclosure to separate the overview from detailed checklists and remediation guides.
Suggestions
Drastically reduce the inline content by moving the full WCAG checklists (Perceivable, Operable, Understandable, Robust) into a separate CHECKLIST.md file and the remediation patterns into REMEDIATION.md, keeping only a concise overview and workflow in the main skill.
Add an explicit audit workflow with numbered steps and validation checkpoints, e.g.: 1) Run automated scan → 2) Triage violations by severity → 3) Manual keyboard/screen reader testing → 4) Apply remediations → 5) Re-run automated scan to verify fixes → 6) Document remaining manual-only issues.
Remove the Core Concepts section (conformance levels, POUR principles, common violations taxonomy)—Claude already knows WCAG fundamentals. Focus the skill on the specific process and tooling for conducting audits.
Cut the Do's/Don'ts best practices section, which contains general accessibility advice Claude already knows, and replace with project-specific configuration guidance (e.g., how to configure axe-core rule sets for different conformance targets).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Includes extensive WCAG reference material Claude already knows (POUR principles, conformance levels, full criterion listings). This is essentially a WCAG reference document, not a skill teaching Claude something new. The core concepts section and full checklist reproduce publicly available standards. | 1 / 3 |
Actionability | Provides fully executable code examples throughout: axe-core integration, Playwright tests, CLI commands, concrete HTML before/after remediation patterns, CSS fixes, and JavaScript keyboard navigation implementations. All code is copy-paste ready. | 3 / 3 |
Workflow Clarity | The checklist structure provides a clear sequence for auditing, 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 overall process of conducting an audit is implicit rather than explicitly sequenced. | 2 / 3 |
Progressive Disclosure | Monolithic wall of content with no references to external files. The full WCAG checklist for all four principles, automated testing code, remediation patterns, and best practices are all inline. This would benefit enormously from splitting the detailed checklists and remediation patterns into 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
70444e5
- 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.