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.

76

Quality

95%

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

87%

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

A dense, highly actionable ARIA-pattern reference with concrete code and per-pattern ARIA/keyboard tables, lean prose, and clean section-based navigation. Its main gap is the absence of an explicit sequenced authoring/review workflow with a verification checkpoint.

Suggestions

Add an explicit authoring workflow — e.g., 1) identify the matching APG pattern, 2) apply required roles/states, 3) implement the keyboard-interaction model, 4) validate with axe-a11y/pa11y-a11y — so the path from design to verified widget is sequenced.

Include a concrete verification checkpoint (run an axe/pa11y scan against the widget and cross-check against the APG example page) to close the loop between authoring and review.

For the review use case, add a short checklist (required roles present, keyboard model complete, none of the 'Common ARIA failures' violations) so reviewing is as sequenced as authoring.

DimensionReasoningScore

Conciseness

Lean, dense reference material — compact tables and brief orienting prose with no padding or explanation of basic concepts Claude already knows; every section earns its place across the 31 patterns.

3 / 3

Actionability

Provides copy-paste-ready HTML for Combobox, Tabs, Disclosure, and Tooltip, plus concrete required-ARIA and keyboard-interaction tables per pattern — fully executable guidance rather than vague direction.

3 / 3

Workflow Clarity

Content is well organized into clear sections, but there is no explicit multi-step authoring/review workflow with validation checkpoints; the simple-skill exemption does not apply to a 240-line multi-pattern reference.

2 / 3

Progressive Disclosure

Clear overview (Overview / When to use) with well-signaled one-level-deep references (W3C APG URL, sibling wcag-* and axe/pa11y skills) and no nested bundle files; sections provide easy in-file navigation.

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 reference covers and gives explicit 'Use when' triggers for both authoring and review. It is concise, uses third person, and is highly distinguishable from neighboring accessibility skills.

DimensionReasoningScore

Specificity

Enumerates multiple concrete specifics — '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' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what it covers and when to use it via the 'Use when authoring a custom interactive widget... or when reviewing one for ARIA correctness' clause.

3 / 3

Trigger Term Quality

Good coverage of natural terms a user would say ('ARIA', 'custom interactive widget', 'native HTML equivalent', and named patterns like Combobox/Tabs/Tree) alongside the review framing.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (W3C APG widget patterns for custom widgets without native equivalents) with triggers unlikely to fire for unrelated skills.

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