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

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

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

A tight, actionable accessibility reference that assumes Claude's competence and covers keyboard, forms, contrast, and validation concretely. Its main weaknesses are the dangling REFERENCE.md pointer and mostly attribute-level (rather than full copy-paste) examples.

Suggestions

Create the referenced REFERENCE.md (with roving tabindex / aria-activedescendant patterns) or remove the dangling reference so navigation is not broken.

Add one or two complete copy-paste-ready snippets (e.g., a labeled form field with aria-invalid + aria-describedby, or a roving tabindex nav example) to lift actionability toward fully executable.

Make the Validation workflow a short numbered sequence (run axe → fix → re-run → tab-through) so the feedback loop reads as an explicit ordered process rather than prose.

Dimension	Reasoning	Score
Conciseness	The body is lean: bullet points with exact thresholds ("Body text ≥4.5:1; large text (18.5px bold / 24px) ≥3:1") and a dense copy-paste skip-link CSS block, with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Concrete, specific guidance throughout—named tools (axe-core, axe-playwright, pa11y), exact ARIA attributes (aria-expanded, aria-required, aria-invalid, aria-describedby), and exact ratios—but most guidance is attribute/threshold-level rather than complete copy-paste snippets, with only one full code block.	4 / 5
Workflow Clarity	The Validation section provides an explicit feedback loop ("fix all high/critical findings and re-run until clean") plus a manual tab-through checkpoint, but the skill is a topical reference rather than a clearly sequenced multi-step workflow, so it sits just below a full explicit-workflow score.	4 / 5
Progressive Disclosure	Well under 50 lines and organized into clear sections (Contrast, Keyboard, Forms, Tables, etc.), but the single "Composite widget patterns ... in REFERENCE.md" reference points to a file that does not exist on disk, a minor navigation gap.	4 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

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

A strong, explicit description that clearly answers both what the skill does and when to use it, with concrete trigger surfaces and a distinct niche. It could be sharpened by adding action verbs and common accessibility synonyms (a11y, ARIA, alt text).

Dimension	Reasoning	Score
Specificity	Names the domain ("WCAG 2.2 Level AA accessibility patterns for React/HTML/CSS") and enumerates many concrete coverage areas (keyboard navigation, screen reader semantics, low vision contrast, voice access, inclusive language), but frames them as "patterns"/"Covers" topics rather than a punchy list of concrete verbs, sitting just below comprehensive-action level.	4 / 5
Completeness	Clearly states the "what" (WCAG 2.2 AA accessibility patterns for React/HTML/CSS) and an explicit "Use when..." clause with concrete enumerated trigger surfaces, matching the anchor that answers both what and when with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural trigger coverage ("creating or modifying UI components, forms, navigation, tables, images," plus keyboard/screen reader/contrast/voice terms), but missing common synonyms a user might say such as "a11y," "ARIA," "alt text," or "tab order."	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (WCAG 2.2 AA accessibility compliance) with distinct, specific triggers (UI components, forms, navigation, tables, images) and minimal overlap risk with general coding skills.	5 / 5
	Total	18 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: monkilabs/opencastle
Path: src/orchestrator/skills/accessibility-standards/SKILL.md
Commit: fa0c341

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