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:Dicklesworthstone/pi_agent_rust --skill wcag-audit-patterns85
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/skillValidation 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 excels across all dimensions. It provides specific capabilities (automated testing, manual verification, remediation guidance), includes natural trigger terms users would actually say, explicitly states both what the skill does and when to use it, and occupies a clear niche that distinguishes it from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'automated testing', 'manual verification', and 'remediation guidance'. Also mentions specific outcomes like 'fixing WCAG violations' and 'implementing accessible design patterns'. | 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 audits', 'WCAG', 'WCAG violations', 'accessible design patterns', 'auditing websites for accessibility'. These are terms accessibility professionals and developers commonly use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on WCAG 2.2 accessibility auditing with distinct triggers like 'WCAG', 'accessibility audits', and 'WCAG violations'. Unlikely to conflict with general web development or testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%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 excessively verbose for a skill file, explaining WCAG fundamentals Claude already knows, and lacks a clear audit workflow with validation checkpoints. The content would benefit from significant condensation and splitting detailed checklists into referenced 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 validate
Move detailed WCAG criterion checklists (Perceivable, Operable, etc.) to separate reference files and keep only a summary in SKILL.md
Remove explanatory content about WCAG levels and POUR principles - Claude knows these; focus on the actionable patterns
Add a validation checkpoint after remediation: 'After applying fixes, re-run axe-core and verify violation count decreased'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but overly verbose for Claude's context window. 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 a monolithic 400+ line document. The detailed checklists for each WCAG criterion could be split into separate reference files, with SKILL.md providing a concise overview and links to detailed criteria. | 2 / 3 |
Total | 9 / 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 (556 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 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.