web-accessibility-audit

Audit web applications for WCAG accessibility compliance. Use when asked to run accessibility checks, identify common violations, and provide remediation guidance.

Quality

70%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/web-accessibility-audit/SKILL.md

Quality

Discovery

89%

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 solid description that clearly communicates its purpose and when to use it. The WCAG/accessibility domain is well-defined and distinctive. The main weakness is that the specific capabilities could be more granular—listing concrete checks like color contrast, alt text, ARIA attributes, or keyboard navigation would strengthen the specificity.

Suggestions

Add specific concrete actions such as 'check color contrast ratios, validate alt text, audit ARIA attributes, verify keyboard navigation' to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (web accessibility/WCAG) and some actions (audit, identify violations, provide remediation guidance), but doesn't list specific concrete actions like checking alt text, color contrast, ARIA labels, keyboard navigation, etc.	2 / 3
Completeness	Clearly answers both what ('Audit web applications for WCAG accessibility compliance') and when ('Use when asked to run accessibility checks, identify common violations, and provide remediation guidance') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms: 'accessibility', 'WCAG', 'accessibility checks', 'violations', 'remediation'. These are terms users would naturally use when seeking accessibility auditing help.	3 / 3
Distinctiveness Conflict Risk	WCAG accessibility auditing is a clear niche with distinct triggers like 'WCAG', 'accessibility compliance', and 'remediation guidance' that are unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

50%

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

This skill is comprehensive and highly actionable with excellent code examples covering all WCAG principles, but it suffers significantly from verbosity—it tries to be both a quick-reference skill and a complete WCAG tutorial. Much of the content (violation statistics, POUR principles, conformance levels, extensive pattern examples) should be moved to the referenced files, leaving the skill body as a lean audit workflow. The workflow is well-structured but lacks explicit validation checkpoints between phases.

Suggestions

Move the '12 Most Common WCAG Violations' list, POUR principles table, conformance levels table, and detailed WCAG pattern examples into reference files (e.g., references/common-violations.md, references/pattern-examples.md), keeping only the audit workflow and output format in the skill body.

Remove explanatory content Claude already knows (what WCAG principles mean, what conformance levels are, WebAIM statistics) to reduce token usage by ~60%.

Add explicit validation checkpoints between audit phases, e.g., 'Review automated results for false positives before proceeding to manual inspection' and 'Verify all critical issues are reproducible before including in report'.

Consolidate the 'Important Notes' and 'Common Pitfalls' sections into the workflow itself as inline warnings where they're most relevant, rather than as separate end-of-file lists.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines. Includes extensive WCAG principle explanations, conformance level tables, and statistics that Claude already knows. The '12 Most Common WCAG Violations' section with WebAIM percentages, the POUR principles table, and conformance levels are all well-known reference material that doesn't need to be in the skill body. Much of this belongs in reference files.	1 / 3
Actionability	Provides fully executable code examples across HTML, CSS, JavaScript, and bash commands. The audit process includes concrete commands (ESLint, Lighthouse, grep patterns), and every WCAG pattern example shows before/after with copy-paste ready code.	3 / 3
Workflow Clarity	The 4-phase audit process is clearly sequenced and the severity prioritization is well-defined. However, there are no explicit validation checkpoints or feedback loops between phases—no 'verify automated results before proceeding to manual inspection' or error recovery steps if tools fail.	2 / 3
Progressive Disclosure	References to external files exist (references/grep-patterns.md, references/screen-reader-guide.md, etc.) which is good, but the main file contains massive amounts of inline content that should be in those reference files instead. The WCAG pattern examples section alone could be a separate reference document, keeping the skill body as a concise overview.	2 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: warpdotdev/oz-skills
Commit: 6c08c49

Reviewed: 14 days 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.