accessibility-compliance-accessibility-audit

You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

42%

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

The body is well-organized into clear sections with a sensible audit workflow, but it is held back by a broken reference to a non-existent playbook and by instruction-level guidance that stops short of naming specific tools or explicit validation gates. Conciseness is reasonable despite some duplication of the description.

Suggestions

Create the missing `resources/implementation-playbook.md` (or remove the reference) so the progressive-disclosure path resolves to a real file.

Name concrete automated scanning tools (e.g., axe-core, Lighthouse, WAVE) and give at least one remediation example rather than only directional guidance.

Add explicit validation checkpoints to the workflow (e.g., "Only proceed to remediation once baseline violations are mapped and severity triaged").

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with no concept explanations, but the opening "You are an accessibility expert..." line and the Context section restate content already in the description and instructions, so it could be tightened.	2 / 3
Actionability	Instructions give concrete guidance (specific manual checks like keyboard, screen reader, focus order, contrast; mapping to WCAG criteria), but "Run automated scans" names no specific tool and remediation stays directional rather than example-backed.	2 / 3
Workflow Clarity	A clear sequence is present (scope -> scans -> manual checks -> map findings -> remediate -> re-test) with a re-test loop, but validation checkpoints are implicit rather than explicit gates (e.g., it never says to halt until a check passes).	2 / 3
Progressive Disclosure	The body references `resources/implementation-playbook.md` in both the Instructions and Resources sections, but no `resources/` directory or playbook file exists in the bundle, so the one-level-deep navigation path is broken and leads nowhere.	1 / 3
	Total	7 / 12 Passed

Description

50%

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

The description names a clear domain and several concrete actions but is written in second person and lacks any explicit "Use when..." trigger, leaving it moderately rather than strongly specified. Trigger-term coverage is decent but omits common accessibility phrasings users would naturally say.

Suggestions

Add an explicit "Use when..." trigger clause (e.g., "Use when auditing interfaces for WCAG compliance, identifying accessibility barriers, or preparing remediation guidance").

Rewrite in third-person voice (e.g., "Conducts accessibility audits...") instead of "You are an accessibility expert...".

Broaden trigger terms to include natural user phrasings like "screen reader", "color contrast", "keyboard navigation", "a11y", and "ADA / Section 508".

Dimension	Reasoning	Score
Specificity	"Conduct audits, identify barriers, and provide remediation guidance" lists multiple concrete actions (a 3), but the description opens with second-person voice ("You are an accessibility expert..."), which the guidelines penalize by reducing specificity by 1.	2 / 3
Completeness	It clearly states what the skill does, but there is no "Use when..." clause or equivalent explicit trigger guidance, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	It includes relevant keywords ("WCAG compliance", "inclusive design", "assistive technology", "audits", "barriers", "remediation") but misses common variations users would actually say such as "screen reader", "color contrast", "keyboard navigation", "a11y", or "ADA/Section 508".	2 / 3
Distinctiveness Conflict Risk	The accessibility/WCAG niche is fairly specific, but without explicit triggers it could still overlap with general UI/UX or design-review skills, matching the "somewhat specific but could overlap" anchor.	2 / 3
	Total	8 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: boisenoise/skills-collections
Commit: f36337d

Reviewed: 2 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.