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.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/accessibility-compliance/skills/wcag-audit-patterns/SKILL.md

Quality

Content

40%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tidy overview that points correctly to a details reference, but it explains WCAG basics Claude already knows and lacks an executable, sequenced audit workflow with specific tools and verification steps. As an audit skill it reads more as a primer than an actionable procedure.

Suggestions

Add a concrete, numbered audit workflow with verification checkpoints (e.g., 1. Run automated scan with axe-core; 2. Keyboard-only navigation pass; 3. Screen-reader spot check; 4. Verify each finding against a WCAG 2.2 success criterion; 5. Document remediation).

Replace generic do's/don'ts with actionable specifics: name tools and commands (axe-cli, Lighthouse, WAVE), cite exact SC numbers (e.g., 1.4.3 Contrast), and give copy-paste test snippets.

Move the POUR principles and A/AA/AA conformance fundamentals into references/details.md since they are baseline knowledge, keeping SKILL.md lean and focused on how to execute an audit.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and well-structured, but the POUR principles block and A/AA/AAA conformance table re-explain WCAG fundamentals Claude already knows; tightening these would move it toward a 4.	3 / 5
Actionability	Provides high-level hints ('Use semantic HTML', '30-50% issues detectable', 'Don't rely only on automated testing') and lists of violations, but no concrete executable guidance — no tool names (axe, Lighthouse, WAVE), commands, specific success-criterion numbers, or test procedures, fitting the 2 anchor more than 3.	2 / 5
Workflow Clarity	Content is organized topically (When to Use, Core Concepts, Best Practices) rather than as a sequenced audit workflow; there is no step-by-step audit process and no validation/verification checkpoints, matching the 2 anchor's rough-or-absent sequence.	2 / 5
Progressive Disclosure	Good structure with clear sections and one well-signaled, one-level-deep reference to references/details.md (a real file). It stops short of 5 because some inline material (POUR, violations tree) could live in the reference and only a single reference path is exposed.	4 / 5
	Total	11 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description that clearly states capabilities and trigger conditions in third person with concrete actions. It narrowly misses top marks on specificity and trigger coverage by omitting a few common synonyms and adjacent compliance terms.

Dimension	Reasoning	Score
Specificity	Names several concrete actions — 'automated testing, manual verification, and remediation guidance' — but does not enumerate the full audit surface (e.g., reporting, VPAT generation), leaving minor coverage gaps consistent with a 4 rather than a comprehensive 5.	4 / 5
Completeness	Explicitly 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...') with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('auditing websites for accessibility', 'fixing WCAG violations', 'accessible design patterns') but omits common synonyms/extensions like 'a11y', 'ADA', 'Section 508', or 'VPAT', so it stops short of comprehensive 5-level coverage.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (WCAG 2.2 accessibility auditing) with distinct, specific triggers and minimal overlap risk with other skills, matching the 5 anchor.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: wshobson/agents
Path: plugins/accessibility-compliance/skills/wcag-audit-patterns/SKILL.md
Commit: d6837ae

Reviewed: about 12 hours ago

Table of Contents

Discovery Implementation Validation

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.