CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

accessibility-standards

WCAG 2.2 AA rules for HTML, CSS and React: contrast, keyboard, screen-reader semantics, voice access, forms and tables. Use when building or changing UI components, forms, navigation or any user-facing element.

71

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

The body is an exemplary lean rulebook: exact thresholds, concrete ARIA patterns, and a validation loop with re-run-until-clean semantics. Its one real defect is the dangling REFERENCE.md pointer — the composite-widget guidance it promises (roving tabindex, aria-activedescendant) is nowhere in the bundle, which hurts both actionability and navigation.

Suggestions

Either add the promised REFERENCE.md with the composite widget patterns (roving tabindex, aria-activedescendant) or inline the essential pattern code for menus/comboboxes/grids directly in the body.

If REFERENCE.md is not intended to exist, remove the reference and state the composite-widget rules inline so no guidance is silently missing.

Consider listing the validation tools in one place (e.g., a short Validation section note) with the exact CI invocation for axe-playwright or pa11y to make the check copy-paste ready.

DimensionReasoningScore

Conciseness

Every line is a rule or command with exact values ("≥4.5:1", "18.5px bold / 24px") and a copy-paste CSS block for the skip link. No conceptual padding, no explaining what WCAG or screen readers are — lean and it fully assumes Claude's competence.

5 / 5

Actionability

Highly concrete: exact contrast ratios, complete skip-link CSS, specific ARIA attributes (aria-required, aria-invalid, aria-describedby, aria-expanded), a page-title format string, and named validation tools (axe-core, axe-playwright, pa11y). The gap: composite widget patterns ("roving tabindex, aria-activedescendant") are deferred to REFERENCE.md, which does not exist in the bundle, leaving that common case without executable guidance.

4 / 5

Workflow Clarity

For a single-purpose standards skill, the action is unambiguous, and the Validation section provides an explicit feedback loop: "Run axe-core ... fix all high/critical findings and re-run until clean. Tab through the page to confirm order and visible focus." Not a destructive or batch operation, so no cap applies.

5 / 5

Progressive Disclosure

Sections are well-organized and compact (44 lines), and the one external pointer is clearly signaled and one level deep — but "Composite widget patterns (roving tabindex, aria-activedescendant) in REFERENCE.md" references a file that is absent from the bundle. A dangling reference means the promised content is unreachable, so navigation fails despite good structure.

3 / 5

Total

17

/

20

Passed

Description

88%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 description: it names the standard, technology targets, and concrete capability areas, and closes with an explicit 'Use when...' trigger clause. Its only weakness is missing the natural vocabulary users most often use ('accessibility', 'a11y', 'ARIA'), which slightly limits trigger recall.

Suggestions

Add the natural terms 'accessibility', 'a11y', and 'ARIA' to the description so it triggers on the phrasing users most commonly use when requesting this skill.

Consider tightening the trigger scope of 'any user-facing element' or pairing it with the accessibility framing to reduce overlap with general frontend/UI skills.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capability areas — "contrast, keyboard, screen-reader semantics, voice access, forms and tables" — grounded in a named standard ("WCAG 2.2 AA rules for HTML, CSS and React"), giving comprehensive coverage of the domain with no vague filler.

5 / 5

Completeness

Explicitly answers both: what — "WCAG 2.2 AA rules for HTML, CSS and React: contrast, keyboard, screen-reader semantics, voice access, forms and tables" — and when — "Use when building or changing UI components, forms, navigation or any user-facing element", with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage ("contrast", "keyboard", "screen-reader", "forms", "tables", "UI components", "navigation", "WCAG"), but it omits the most common user phrasings "accessibility"/"a11y" and "ARIA". It is above anchor 3 (which expects missing common synonyms) but lacks the exhaustive synonym/extension coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The WCAG 2.2 AA framing carves a clear niche, but the trigger "or any user-facing element" is broad and could overlap with general frontend/UI or design-system skills. Mostly distinct with minor overlap risk — anchor 4 rather than 5.

4 / 5

Total

18

/

20

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

Validation for skill structure

No warnings or errors.

Repository

monkilabs/opencastle

Path

src/orchestrator/skills/accessibility-standards/SKILL.md

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.