CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/aria-authoring-patterns

Use when building or reviewing a custom interactive widget with no native HTML equivalent (combobox, dialog, menu, tabs, tree and more). Gives the W3C ARIA Authoring Practices pattern: required roles and states, keyboard interaction and common violations.

Quality

84%

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

78%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 highly actionable, well-organized reference with copy-paste HTML, precise ARIA tables, and cited edge-case rules (toggle labels, live regions, menu vs disclosure). Its main weaknesses are inline density — per-pattern detail that belongs in reference files — and minor duplication/over-explanation in the pattern catalog and failure tables.

Suggestions

Move the 'Per-pattern essentials' deep dives (combobox, tabs, tooltip, disclosure nav, toggle buttons, live regions) into one-level-deep files under references/ (e.g. references/combobox.md) and keep SKILL.md as an overview with the pattern catalog and a short pointer per pattern.

Merge the overlapping 'Common ARIA failures' and 'Anti-patterns' tables into a single table to remove duplicated entries (toggle label changes, aria-label on visible-text elements).

Drop or compress the 'When to use' column for well-known widgets (Button, Link, Table) and keep only the load-bearing 'Native fallback' column, and add a brief per-pattern test sequence like the disclosure-navigation one to the other pattern sections.

DimensionReasoningScore

Conciseness

Almost entirely dense tables and complete code with no prose padding, but the 31-pattern catalog explains well-known concepts ('Button — Trigger an action', 'Link — Navigation to a different resource') and the 'Common ARIA failures' and 'Anti-patterns' tables partially duplicate each other (toggle labels, aria-label misuse).

4 / 5

Actionability

Copy-paste-ready, complete HTML for combobox, tabs, disclosure, tooltip, and navigation patterns, concrete per-attribute 'why' tables, and executable verification guidance such as the Playwright assertion and the keyboard test sequence ('press Enter on the button, expect aria-expanded="true"').

5 / 5

Workflow Clarity

Decision guidance is unambiguous (native-preferred table, 'follow the matching APG pattern exactly', disclosure-not-menu for site nav), but there is no explicit end-to-end authoring/test sequence and step-by-step test procedures appear for only one pattern (disclosure navigation).

4 / 5

Progressive Disclosure

Sections are clearly organized, but the ~335-line body inlines ~150 lines of per-pattern deep dives ('Per-pattern essentials') and full pattern catalog tables that belong in one-level-deep reference files; no bundle files exist, so SKILL.md carries all detail itself.

3 / 5

Total

16

/

20

Passed

Description

83%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 that explicitly states both what the skill provides and when to use it, with concrete widget-name triggers. Keyword coverage is good but omits common accessibility phrasings, and the niche slightly overlaps sibling accessibility skills.

DimensionReasoningScore

Specificity

Names the domain and several concrete deliverables — 'required roles and states, keyboard interaction and common violations' — but the user-facing action ('building or reviewing') is generic, leaving minor gaps versus the comprehensive multi-action coverage of the top anchor.

4 / 5

Completeness

Explicitly answers both: 'Gives the W3C ARIA Authoring Practices pattern: required roles and states, keyboard interaction and common violations' (what) and 'Use when building or reviewing a custom interactive widget with no native HTML equivalent (combobox, dialog, menu, tabs, tree and more)' (when, with concrete trigger phrases).

5 / 5

Trigger Term Quality

Good natural keyword coverage ('combobox, dialog, menu, tabs, tree', 'custom interactive widget', 'W3C ARIA Authoring Practices'), but common phrasings a user would naturally say such as 'accessibility', 'a11y', or 'screen reader' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche — custom widgets with no native HTML equivalent — with distinct widget-name triggers, but 'keyboard interaction' overlaps with closely related accessibility skills (e.g. a keyboard-navigation or general WCAG skill), creating minor overlap risk.

4 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 possibly missing (references/focus-trap.md)

Warning

Total

15

/

16

Passed

Reviewed

On this page