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, and inclusive language.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 an excellent skill description that clearly defines its scope (WCAG 2.2 AA accessibility patterns), specifies the technology context (React/HTML/CSS), includes an explicit 'Use when' clause with concrete trigger scenarios, and covers the breadth of accessibility concerns. It uses proper third-person voice and is concise yet comprehensive.
| 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, and 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', 'UI components'. 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 with specific standards (WCAG 2.2 Level AA) makes it clearly distinguishable from general UI or React skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently covers WCAG 2.2 Level AA accessibility patterns with concrete, actionable guidance. It excels at conciseness by using tables for rules, providing executable code examples, and deferring complex patterns to a reference file. The validation workflow with explicit feedback loops ensures safe implementation of accessibility requirements.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It assumes Claude's competence with HTML/CSS/ARIA concepts, avoids explaining what WCAG is or how screen readers work, and every section delivers actionable rules or patterns without padding. | 3 / 3 |
Actionability | Provides concrete, copy-paste-ready code examples (skip link HTML/CSS, navigation markup), specific contrast ratios, exact tool commands (`npx axe-core`), and clear patterns in table format. The guidance is specific and executable rather than abstract. | 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), and the validation section explicitly includes error recovery ('Fix, re-run audits, and repeat until no high/critical a11y issues remain'). | 3 / 3 |
Progressive Disclosure | Content is well-organized into clearly labeled sections by concern (Keyboard, Low Vision, Screen Reader, Forms, etc.). Complex composite patterns are explicitly deferred to REFERENCE.md with clear signaling. The skill stays focused as an overview without becoming monolithic. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%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
f5c8508
- Reviewed
Table of Contents
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.