CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/aria-authoring-patterns

Reference for the W3C ARIA Authoring Practices Guide (APG) - covers the 31 canonical interactive-widget patterns (Combobox, Dialog, Menu, Tabs, Tree, etc.), their required ARIA roles and states, the keyboard-interaction model per pattern, and the canonical-violations to watch for. Use when authoring a custom interactive widget that doesn't have a native HTML equivalent, or when reviewing one for ARIA correctness.

65

Quality

82%

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

68%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 dense, well-structured reference skill with concrete code examples and actionable failure/anti-pattern tables. Its main weakness is workflow clarity: there is no explicit authoring workflow with validation checkpoints or a feedback loop tying implementation to axe-a11y verification.

Suggestions

Add an explicit numbered authoring workflow ending in a validation checkpoint, e.g. 'identify the widget -> match an APG pattern -> implement required roles/states/keyboard -> verify with axe-a11y -> re-check against the Common ARIA failures table'.

Frame the existing axe-a11y reference as a concrete verification step (a validate-then-fix feedback loop) rather than only a 'When to use' scenario, to lift workflow clarity above 3.

Consider moving the per-pattern essentials for the remaining 27 patterns into a references/ file (one level deep) so the SKILL.md overview stays lean while keeping full actionability available on demand.

DimensionReasoningScore

Conciseness

Mostly lean and table/code-driven with little explanation of concepts Claude already knows, but the 'first rule of ARIA' blockquote and some editorial table commentary could be trimmed slightly.

4 / 5

Actionability

Copy-paste-ready HTML examples for Combobox, Tabs, Disclosure, and Tooltip plus concrete 'Fix' columns in failure tables, but only 4 of the 31 patterns receive full code examples.

4 / 5

Workflow Clarity

The document structure implies a sensible sequence (identify pattern, implement roles/states/keyboard, check failures) but there are no explicit validation checkpoints or a validate-fix-retry feedback loop, even though axe-a11y verification is mentioned only as a use case.

3 / 5

Progressive Disclosure

Well-organized into clear sections with one-level-deep, clearly signaled external references (APG URL, WAI-ARIA spec, sibling skills); no bundle files exist, and the single-file quick-reference layout is appropriate, though per-pattern details are all inlined rather than split into reference files.

4 / 5

Total

15

/

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, specific description that clearly states both what the skill covers and when to use it, with concrete pattern names as natural trigger terms. The main gap is missing common accessibility synonyms (a11y, screen reader) and minor overlap with sibling a11y skills.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'covers the 31 canonical interactive-widget patterns', 'required ARIA roles and states', 'the keyboard-interaction model per pattern', 'canonical-violations to watch for' — giving comprehensive coverage of what the reference provides.

5 / 5

Completeness

Explicitly answers both what ('Reference for the W3C ARIA APG - covers...') and when ('Use when authoring a custom interactive widget... or when reviewing one for ARIA correctness') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Strong natural trigger terms ('Combobox, Dialog, Menu, Tabs, Tree', 'custom interactive widget', 'ARIA correctness'), but misses common synonyms a user might say such as 'accessibility', 'a11y', or 'screen reader'.

4 / 5

Distinctiveness Conflict Risk

Clear niche scoped to the W3C ARIA Authoring Practices Guide with distinct triggers, but minor overlap risk with closely related sibling accessibility skills (wcag-*, axe-a11y) referenced in the body.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents