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.
Install with Tessl CLI
npx tessl i github:wshobson/agents --skill wcag-audit-patternsOverall
score
81%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 96%
↑ 1.05xAgent success when using this skill
Validation for skill structure
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 well-crafted skill description that follows best practices. It uses third person voice, lists specific capabilities, includes an explicit 'Use when...' clause with natural trigger terms, and carves out a distinct niche around accessibility auditing. The description provides sufficient detail for Claude to confidently select this skill when users mention accessibility, WCAG, or related concepts.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'WCAG 2.2 accessibility audits', 'automated testing', 'manual verification', and 'remediation guidance'. These are distinct, actionable 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'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'accessibility', 'WCAG', 'auditing websites', 'WCAG violations', 'accessible design patterns'. Covers both technical terms (WCAG 2.2) and common language (accessibility). | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on WCAG/accessibility auditing with specific triggers like 'WCAG violations' and 'accessible design patterns'. Unlikely to conflict with general web development or testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable remediation patterns and executable code examples, making it practically useful for fixing accessibility issues. However, it's overly verbose, explaining WCAG fundamentals Claude already knows, and lacks a clear audit workflow with validation checkpoints. The monolithic structure would benefit from splitting detailed checklists into separate reference files.
Suggestions
Add an explicit audit workflow section with numbered steps: 1) Run automated scan, 2) Review violations, 3) Manual testing checklist, 4) Apply fixes, 5) Re-run scan to verify - with validation at each step.
Remove explanatory content Claude already knows (POUR principles definitions, conformance level descriptions) and replace with just the actionable checklist items.
Split the detailed per-criterion checklists into separate files (e.g., PERCEIVABLE.md, OPERABLE.md) and keep SKILL.md as a concise overview with quick-reference patterns and links.
Add a verification step after remediation patterns showing how to confirm the fix worked (e.g., 'Verify: Run axe-core on the element, expect no violations for rule X').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but overly verbose for Claude's needs. The POUR principles explanation, conformance level table, and extensive checklist items explain concepts Claude already knows. Could be significantly condensed while preserving actionability. | 2 / 3 |
Actionability | Excellent executable code examples throughout - HTML fixes, CSS contrast solutions, JavaScript keyboard handling, axe-core integration, and CLI commands. All examples are copy-paste ready with clear before/after patterns. | 3 / 3 |
Workflow Clarity | While the checklist structure is clear, there's no explicit audit workflow sequence (e.g., 'run automated tests first, then manual checks, then validate fixes'). Missing validation checkpoints between audit phases and no feedback loop for verifying remediation success. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's monolithic - over 400 lines in a single file. The detailed checklists for each WCAG criterion could be split into separate reference files, with SKILL.md providing a concise overview and links. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (556 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.