CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/wcag-keyboard-navigation

Reference catalog for WCAG 2.2 keyboard-navigation conformance - covers SC 2.1.1 (Keyboard), 2.1.2 (No Keyboard Trap), 2.1.4 (Character Key Shortcuts), 2.4.3 (Focus Order), 2.4.7 (Focus Visible), 2.4.11/2.4.12 (Focus Not Obscured) - with conformance levels (A/AA), test scripts, and per-criterion failure patterns. Use when authoring or reviewing keyboard-only interaction support.

75

Quality

94%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

A well-structured, actionable reference catalog with clear per-component workflows and concrete fixes. Its main weakness is mild verbosity from explanatory context (WCAG principles overview, spec quotes, rationale) that Claude already knows.

Suggestions

Trim the four-principles overview and quoted WCAG spec passages; Claude already knows WCAG's POUR structure and normative language - link the spec instead.

Remove or compress rationale sentences like 'This SC exists because users with speech-input software produce spurious key presses' to keep the catalog token-lean.

Replace the 'await expect(...)' placeholder in the SC 2.1.1 Playwright example with a concrete locator assertion so the test is fully copy-paste-ready.

DimensionReasoningScore

Conciseness

Mostly efficient tables/scripts, but includes unnecessary explanation Claude already knows - the four-principles overview ('Perceivable / Operable / Understandable / Robust'), quoted WCAG spec passages, and rationale sentences ('This SC exists because users with speech-input software...') could be trimmed.

2 / 3

Actionability

Provides concrete, copy-paste-ready guidance - a Playwright test script and specific fixes like ':focus-visible { outline: 2px solid var(--focus-ring); }' and 'scroll-margin-top'; one 'await expect(...)' placeholder is incomplete but the bulk is executable.

3 / 3

Workflow Clarity

Per-component test patterns are clearly sequenced (Form 1-5, Modal 1-4, Menu 1-5, Tabs 1-4) with embedded verification checkpoints ('verify focus order', 'verify each interactive element has a visible focus ring').

3 / 3

Progressive Disclosure

Well-organized into clear sections (Overview, When to use, Success Criteria, Per-component patterns, Anti-patterns, References) with one-level references to sibling skills and external specs, no nested reference chains.

3 / 3

Total

11

/

12

Passed

Description

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.

A strong, specific description that clearly states what the skill provides and when to use it, with natural trigger terms and a distinct niche. It is slightly verbose due to the inline SC-number enumeration but earns high marks across all dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions - 'covers SC 2.1.1...2.4.12', 'conformance levels (A/AA), test scripts, and per-criterion failure patterns' - rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Reference catalog for WCAG 2.2 keyboard-navigation conformance - covers...') and when ('Use when authoring or reviewing keyboard-only interaction support').

3 / 3

Trigger Term Quality

Natural terms a user would say are present ('keyboard-navigation conformance', 'keyboard-only interaction support', 'WCAG 2.2'), though the SC-number enumeration is somewhat jargon-heavy.

3 / 3

Distinctiveness Conflict Risk

Clear niche (WCAG 2.2 keyboard-navigation criteria) with distinct triggers, unlikely to fire for the paired runner skills (axe-a11y, pa11y-a11y).

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents