CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aria-required-attr

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Include required ARIA attributes for roles. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/aria-required-attr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 lean, well-structured overview body that delegates detail appropriately to a real one-level-deep reference file. The main gaps are in-body actionability — no roles-to-required-attributes mapping, code snippet, or named verification tool — and mild redundancy/padding (background intro, Explain section, Quick Reference overlap).

Suggestions

Cut the background intro sentence and the Explain section (they restate ARIA knowledge Claude already has) and merge the Quick Reference bullets into Check/Fix to remove redundancy.

Inline the minimal executable core in the body: a short table or list mapping common roles to their required attributes (slider → aria-valuenow/min/max, scrollbar → aria-controls/valuenow, checkbox → aria-checked) with one small HTML snippet, instead of deferring all specifics to references/rule.md.

Make the verification checkpoint concrete by naming the tooling (e.g., "run axe or Lighthouse" and "inspect the accessibility tree") rather than "browser accessibility tooling or assistive tech".

DimensionReasoningScore

Conciseness

The body is short but includes unnecessary explanation Claude already knows — "Certain ARIA roles are incomplete without their required attributes, preventing assistive technologies from correctly communicating the element's state or value" and an Explain section restating why screen readers need ARIA — and the Quick Reference bullets largely repeat the Check and Fix sections. It fits the 'mostly efficient but could be tightened' anchor rather than the 'minor trims' anchor above.

3 / 5

Actionability

Only one concrete detail appears in the body — "aria-valuenow for role=\"slider\"" — while the core knowledge needed to execute (which roles require which attributes, any code example, any concrete tool command) is entirely deferred to references/rule.md. This is 'some concrete guidance but incomplete; missing key details' rather than the mostly-executable anchor above.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections imply a clear sequence for this single-task skill, and the Code Review section mentions verification ("note how to verify the fix with browser accessibility tooling or assistive tech"), but the verification step is only vaguely specified in the body rather than being a concrete checkpoint — matching 'clear sequence with most checkpoints; minor validation gaps'.

4 / 5

Progressive Disclosure

The body is a concise overview with a clearly signaled, verified one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and the referenced file exists and carries the bulk content (examples, exceptions, standards, verification), matching the clear-overview anchor.

5 / 5

Total

15

/

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 covers both when to trigger (rendered HTML, interactive components, design-system patterns) and what to do (check native semantics, inspect keyboard/focus/accessible-name/screen-reader behavior). Its main weaknesses are a grammatically mangled embedded rule title and the absence of the word "accessibility" itself as a trigger term.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — but stops short of comprehensive coverage: it never states the rule's actual outcome (flagging/adding missing required attributes), and the garbled phrase "related to Include required ARIA attributes for roles" muddles the core action.

4 / 5

Completeness

Both what and when are explicitly answered with concrete trigger phrases: "Use when reviewing rendered HTML, interactive components, or design-system patterns related to..." gives the when, and "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" gives the what.

5 / 5

Trigger Term Quality

Good natural keyword coverage — "rendered HTML", "interactive components", "ARIA attributes", "roles", "keyboard behavior", "screen-reader output" — but common variations like "accessibility", "a11y", or "WCAG" are missing, keeping it below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The ARIA-required-attributes trigger is a clear niche distinct from most skills, but the generic "reviewing rendered HTML, interactive components, or design-system patterns" framing would also match sibling frontendchecklist accessibility rules, giving minor overlap risk with closely related skills.

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/aria-required-attr/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.