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, plus the modal focus-trap / focus-management pattern (focus-on-open, Tab-cycle, inert, Escape-closes, restore-to-trigger, native `<dialog>`) in references/. Use when authoring or reviewing keyboard-only interaction support, or a modal / drawer / popover's focus management.

69

Quality

87%

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

75%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 well-organized reference catalog with concrete test scripts, specific fixes, and a properly linked one-level-deep reference file. Minor conciseness padding and a placeholder in the inline test script keep it just short of the top anchors.

Suggestions

Replace the placeholder `await expect(...)` in the SC 2.1.1 Playwright snippet with a real assertion so the example is fully copy-paste executable.

Trim the rationale sentences (e.g. the speech-input explanation under SC 2.1.4) since Claude already knows why these SCs exist.

Move the per-component test-pattern checklists' more detailed variations into references/ and keep SKILL.md to the canonical step lists, tightening the body toward the lean anchor.

DimensionReasoningScore

Conciseness

Mostly lean — tables of patterns/failures and a compact Playwright snippet assume Claude's competence — but a few explanatory sentences (e.g. 'This SC exists because users with speech-input software...') and the full SC quotations add padding that could be trimmed.

4 / 5

Actionability

Concrete, copy-paste-ready Playwright test code and specific fixes (e.g. ':focus-visible { outline: 2px solid var(--focus-ring); }', scroll-margin-top) cover common cases; the embedded test uses a placeholder `await expect(...)` that keeps it just shy of fully executable.

4 / 5

Workflow Clarity

Per-component test patterns (Form, Modal, Menu, Tabs) are numbered and clearly sequenced with implicit validation via the test scripts; it lacks explicit 'validate, fix, re-run' checkpoints, but the skill is a reference catalog rather than a destructive workflow so the simple-skill guidance applies.

4 / 5

Progressive Disclosure

Good structure: SKILL.md is an overview with well-signaled one-level-deep references to references/focus-trap.md (a real file) and clearly named sibling skills; the modal pattern is appropriately pushed to the reference rather than fully inlined, though the body still carries a fair amount of detail that could live in references.

4 / 5

Total

16

/

20

Passed

Description

92%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 dense, specific description that crisply states both what the skill covers and when to use it, with a clear niche and low overlap risk. Trigger-term coverage is strong but could add lay synonyms for accessibility and tab order.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — conformance levels, test scripts, per-criterion failure patterns, and an enumerated modal focus-management pattern (focus-on-open, Tab-cycle, inert, Escape-closes, restore-to-trigger, native <dialog>) — giving comprehensive coverage of the skill's scope.

5 / 5

Completeness

Explicitly answers 'what' (reference catalog covering six named SCs plus the focus-trap pattern) and 'when' ('Use when authoring or reviewing keyboard-only interaction support, or a modal / drawer / popover's focus management') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural triggers like 'keyboard-only interaction support' and 'modal / drawer / popover's focus management' are present, but it leans on the technical SC numbering and lacks common synonyms a non-expert user might say (e.g. 'a11y', 'accessibility', 'tab order').

4 / 5

Distinctiveness Conflict Risk

The narrow WCAG keyboard-navigation niche, explicit SC enumeration, and pointer to the modal focus-trap pattern in references/ make it clearly distinguishable from sibling skills like wcag-color-contrast or axe-a11y with minimal conflict risk.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents