accessibility-standards

WCAG 2.2 Level AA accessibility patterns for React/HTML/CSS. Use when creating or modifying UI components, forms, navigation, tables, images, or any user-facing elements. Covers keyboard navigation, screen reader semantics, low vision contrast, voice access, inclusive language.

Quality

96%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Discovery

100%

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 strong, well-crafted skill description that clearly defines its scope (WCAG 2.2 AA accessibility), specifies the technology context (React/HTML/CSS), and provides explicit trigger guidance with a 'Use when' clause. It covers both the what and when comprehensively, uses natural developer terminology, and occupies a distinct niche that is unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and domains: 'UI components, forms, navigation, tables, images, user-facing elements' along with specific accessibility concerns like 'keyboard navigation, screen reader semantics, low vision contrast, voice access, inclusive language'.	3 / 3
Completeness	Clearly answers both what ('WCAG 2.2 Level AA accessibility patterns for React/HTML/CSS') and when ('Use when creating or modifying UI components, forms, navigation, tables, images, or any user-facing elements') with an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'accessibility', 'WCAG', 'keyboard navigation', 'screen reader', 'contrast', 'forms', 'navigation', 'React', 'HTML', 'CSS'. These are terms developers naturally use when seeking accessibility guidance.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive niche combining WCAG 2.2 AA compliance with specific frontend technologies (React/HTML/CSS). The accessibility focus clearly distinguishes it from general UI/component skills, and the specific standard (WCAG 2.2 Level AA) further narrows its scope.	3 / 3
	Total	12 / 12 Passed

Implementation

92%

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, well-structured accessibility skill that provides concrete, actionable patterns with good token efficiency. It covers the right breadth of WCAG 2.2 AA topics with specific code examples, contrast ratios, and tool recommendations. The main weakness is that REFERENCE.md is referenced but not provided in the bundle, and the skill is moderately long — some sections could potentially be offloaded to keep the overview leaner.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient throughout. It assumes Claude knows HTML, ARIA, and React fundamentals, providing only the specific patterns and rules needed. No unnecessary explanations of what accessibility is or how screen readers work in general.	3 / 3
Actionability	Provides concrete, copy-paste-ready HTML/CSS code examples (skip link, navigation, sr-only class), specific contrast ratios, exact tool commands (`npx axe-core`), and precise ARIA attribute patterns. The tables with rules and patterns are immediately actionable.	3 / 3
Workflow Clarity	The validation checkpoints section provides a clear run-fix-repeat feedback loop with specific tools and steps. The overall workflow is stated upfront (plan → generate → review → iterate). For a reference/standards skill, the validation section with explicit re-run instructions is well done.	3 / 3
Progressive Disclosure	References REFERENCE.md for composite component patterns, which is good progressive disclosure. However, REFERENCE.md is not provided in the bundle, so we can't verify the reference is accurate. The skill itself is well-organized with clear sections, but some sections (like Tables & Grids, Navigation) could potentially be moved to reference files to keep the main skill more focused.	2 / 3
	Total	11 / 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: monkilabs/opencastle
Commit: 7a69a05

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