accessibility-a11y

Implement web accessibility (a11y) best practices following WCAG guidelines to create inclusive, accessible user interfaces.

Quality

41%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./accessibility-a11y/SKILL.md

Quality

Discovery

32%

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 identifies a clear domain (web accessibility/WCAG) but lacks the specificity and completeness needed for reliable skill selection. It fails to include explicit trigger guidance and misses concrete actions that would help Claude understand when to apply this skill versus general web development skills.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions accessibility, a11y, WCAG, screen readers, ADA compliance, or asks about making UI accessible'

List specific concrete actions such as 'add ARIA labels, fix color contrast issues, implement keyboard navigation, write alt text for images'

Include more natural trigger terms users might say: 'screen reader support', 'ADA', 'color contrast', 'alt text', 'focus states', 'semantic HTML'

Dimension	Reasoning	Score
Specificity	Names the domain (web accessibility, WCAG) and general goal (create inclusive, accessible user interfaces), but lacks specific concrete actions like 'add ARIA labels', 'fix color contrast', 'implement keyboard navigation'.	2 / 3
Completeness	Describes what it does (implement accessibility best practices) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes good terms like 'a11y', 'WCAG', 'accessibility', and 'accessible', but misses common variations users might say like 'screen reader', 'ADA compliance', 'keyboard navigation', 'color contrast', or 'alt text'.	2 / 3
Distinctiveness Conflict Risk	The 'a11y' and 'WCAG' terms provide some distinctiveness, but 'user interfaces' and 'best practices' are generic enough to potentially overlap with general UI/UX or web development skills.	2 / 3
	Total	7 / 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 provides comprehensive accessibility guidelines with good topical coverage and clear organization. However, it reads more like a reference document than an actionable skill - it lacks executable code examples, concrete implementation patterns, and clear validation workflows. The content would benefit from being more concise and including copy-paste ready code snippets.

Suggestions

Add executable code examples for key patterns (e.g., accessible form markup, ARIA live region implementation, focus trap handling)

Include a quick-start checklist with the most critical accessibility checks to run before shipping

Add explicit validation workflow: 'Run axe-core -> fix critical issues -> re-run -> verify with keyboard navigation -> test with screen reader'

Split detailed content (ARIA patterns, testing procedures) into separate reference files and link from main skill

Dimension	Reasoning	Score
Conciseness	The content is reasonably organized but includes some explanatory text Claude already knows (e.g., 'Design for all users including those with visual, auditory, motor, and cognitive disabilities'). Some sections could be tightened into more direct instructions.	2 / 3
Actionability	Provides specific guidance and mentions concrete tools/attributes, but lacks executable code examples. Instructions like 'Use semantic elements' and 'Ensure sufficient color contrast' are directive but not copy-paste ready with actual implementation code.	2 / 3
Workflow Clarity	Testing section provides a reasonable sequence (automated then manual), but lacks explicit validation checkpoints or feedback loops. No clear 'if X fails, do Y' recovery steps for accessibility remediation workflows.	2 / 3
Progressive Disclosure	Content is well-organized with clear section headers, but it's a monolithic document with no references to external files for detailed topics like ARIA patterns or testing procedures. Complex topics like screen reader testing could benefit from separate detailed guides.	2 / 3
	Total	8 / 12 Passed

Validation

62%

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

Validation for skill structure

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning
body_examples	No examples detected (no code fences and no 'Example' wording)	Warning
body_output_format	No obvious output/return/format terms detected; consider specifying expected outputs	Warning
body_steps	No step-by-step structure detected (no ordered list); consider adding a simple workflow	Warning

	Total	10 / 16 Passed

Repository: mindrally/skills
Commit: 47f47c1

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