CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/04-develop/01-ui-skills-dot-com/wcag-audit-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 skill delivers genuinely valuable, executable material in its automated-testing and remediation-pattern sections, but buries it in a ~550-line monolith that re-enumerates the entire WCAG 2.2 checklist and explains concepts Claude already knows. Restructuring into an overview plus a references file, and adding an explicit audit workflow, would substantially improve it.

Suggestions

Move the per-principle WCAG checklists (Principles 1-4) into a references/ file (e.g. references/wcag-checklist.md) and keep only the high-impact 'Common Violations by Impact' summary and links in SKILL.md.

Delete or drastically shrink the 'Core Concepts' section (conformance levels, POUR definitions) — this is background knowledge Claude already has and costs tokens without adding capability.

Add an explicit sequenced audit workflow, e.g. 1. Scope the audit (target level A/AA), 2. Run automated scan (axe CLI), 3. Manual keyboard/screen-reader checks per checklist, 4. Triage findings by impact, 5. Apply remediation patterns and re-run the scan to verify fixes.

DimensionReasoningScore

Conciseness

The body spans ~550 lines, of which the 'Core Concepts' section (POUR principles, conformance levels, 'Perceivable: Can users perceive the content?') and the ~350-line enumeration of every WCAG success criterion ('1.4.3 Contrast (Minimum)', '2.4.11 Focus Not Obscured', etc.) restate reference knowledge Claude already has. Several padded sections duplicate the WCAG spec rather than adding what Claude doesn't know.

2 / 5

Actionability

Mostly executable, copy-paste-ready guidance: the axe-core integration ('await page.addScriptTag({ path: require.resolve(\'axe-core\') })'), CLI commands ('npx @axe-core/cli https://example.com', 'npx pa11y'), and before/after remediation patterns for labels, contrast, and keyboard access. Minor gaps keep it below 5: the AccessibleDropdown example calls undefined methods (this.toggle(), this.focusNext()) and the Playwright snippet omits its imports/setup.

4 / 5

Workflow Clarity

The checklist is systematically organized by principle and the layout implies a rough order (checklist -> automated testing -> remediation), but there is no explicit end-to-end audit sequence tying together scoping, automated scan, manual verification, and reporting. Checkpoints are implicit (e.g., no step for triaging 'Critical (Blockers)' vs 'Serious' findings or verifying fixes after remediation), matching the 'steps present but checkpoints missing or implicit' anchor.

3 / 5

Progressive Disclosure

Section headers are clear ('## Audit Checklist', '## Automated Testing', '## Remediation Patterns'), but the skill is a single monolithic file with no bundle: the per-principle checklists (hundreds of lines, e.g. the full Perceivable/Operable/Understandable/Robust sections) are exactly the content that should live in a separate references file. This matches 'some structure but content that should be separate is inline'.

3 / 5

Total

12

/

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 description: it states concrete capabilities in third person and provides an explicit 'Use when...' clause with multiple natural trigger phrases. The only room for improvement is broader synonym coverage in the triggers (a11y, ADA, Section 508) to catch more user phrasings.

DimensionReasoningScore

Specificity

'Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance' names the domain and several concrete actions. Below the 5 anchor because the actions are bundled around a single audit activity and 'remediation guidance' is a deliverable rather than a distinct action; coverage also omits reporting/VPAT work the body actually covers.

4 / 5

Completeness

Both questions answered explicitly: what — 'Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance'; when — 'Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns', with three concrete trigger phrases mirroring the anchor-5 example structure.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'auditing websites for accessibility', 'fixing WCAG violations', 'implementing accessible design patterns', 'WCAG 2.2' — phrases users would plausibly say. Not 5 because common synonyms and related compliance terms are missing (e.g. 'a11y', 'ADA', 'Section 508', 'screen readers', 'VPAT').

4 / 5

Distinctiveness Conflict Risk

Clear niche (WCAG 2.2 accessibility auditing) with distinct triggers ('WCAG violations', 'accessibility audits') that would not naturally invoke another skill; overlap risk with generic web-testing skills is minimal.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (557 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

marchatton/agent-skills

Path

.agents/skills/04-develop/01-ui-skills-dot-com/wcag-audit-patterns/SKILL.md

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.