accessibility-wcag

Web accessibility patterns for WCAG 2.2 compliance including ARIA, keyboard navigation, screen readers, and testing

1.06x

Quality

67%

Does it follow best practices?

Impact

95%

1.06x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/accessibility-wcag/SKILL.md

Quality

Discovery

54%

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 effectively identifies its accessibility niche with good trigger terms but fails to provide explicit guidance on when Claude should use it. The capabilities listed are more like topic areas than concrete actions, and the missing 'Use when...' clause significantly limits its effectiveness for skill selection.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about accessibility, WCAG compliance, screen reader support, or keyboard-only navigation'

Convert topic areas into concrete actions: 'Implements ARIA attributes, audits keyboard focus order, tests with screen readers, validates WCAG 2.2 compliance'

Dimension	Reasoning	Score
Specificity	Names the domain (web accessibility, WCAG 2.2) and lists some areas (ARIA, keyboard navigation, screen readers, testing), but these are categories rather than concrete actions like 'implement ARIA labels' or 'audit keyboard focus order'.	2 / 3
Completeness	Describes what the skill covers (accessibility patterns) 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 strong natural keywords users would say: 'accessibility', 'WCAG', 'ARIA', 'keyboard navigation', 'screen readers', and 'testing' - these cover common variations of how users discuss accessibility work.	3 / 3
Distinctiveness Conflict Risk	The combination of 'WCAG 2.2', 'ARIA', 'screen readers', and 'keyboard navigation' creates a clear niche that is unlikely to conflict with other skills - accessibility is a distinct domain.	3 / 3
	Total	9 / 12 Passed

Implementation

79%

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

This is a strong accessibility reference skill with excellent concrete code examples covering semantic HTML, ARIA patterns, keyboard navigation, and forms. The content is appropriately concise and highly actionable. However, it could benefit from explicit testing workflows (how to actually run screen reader tests, use contrast checkers) and references to external resources for comprehensive WCAG 2.2 coverage.

Suggestions

Add a testing workflow section with specific commands/steps for running accessibility audits (e.g., axe-core, Lighthouse, manual screen reader testing procedures)

Include references to external resources for deeper WCAG 2.2 criteria coverage (e.g., link to a WCAG_CRITERIA.md or official W3C resources)

Add validation feedback loop for the checklist items - how to verify each item passes and what to do when it fails

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, providing concrete code examples without explaining basic concepts Claude already knows. Every section delivers actionable patterns without padding.	3 / 3
Actionability	Fully executable HTML, TSX, and CSS code examples throughout. The Modal, Tabs, and Form components are copy-paste ready with proper ARIA attributes and keyboard handling.	3 / 3
Workflow Clarity	The checklist at the end provides a clear sequence for validation, but the skill lacks explicit testing workflows or feedback loops for verifying accessibility compliance. No step-by-step process for running screen reader tests or contrast checks.	2 / 3
Progressive Disclosure	Content is well-organized with clear section headers, but it's a monolithic file with no references to external resources for deeper topics like WCAG 2.2 specific criteria, testing tool documentation, or advanced ARIA patterns.	2 / 3
	Total	10 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: haniakrim21/everything-claude-code
Commit: ae2cadd

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