CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aria-roles

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

Quality

74%

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-roles/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.

The body is well-structured with a clear review workflow and exemplary progressive disclosure to a single real reference file. It is held back by a concept-explanation intro Claude does not need, some duplicated guidance between Quick Reference and Fix, and a Check step that lacks an executable detection technique.

Suggestions

Delete or compress the opening paragraph explaining what invalid ARIA roles do; Claude already knows this.

Make the Check section executable, e.g. a grep pattern for role attributes or a named tool (axe DevTools, accessibility inspector) to detect invalid values.

De-duplicate the native-controls guidance between Quick Reference and Fix so it appears once.

DimensionReasoningScore

Conciseness

The intro sentence "Invalid or misspelled ARIA roles are ignored by browsers and assistive technologies, rendering the intended accessibility features useless..." explains a concept Claude already knows, and "Prefer native HTML controls over custom ARIA widgets" in Quick Reference restates the Fix section's advice. Mostly efficient but could be tightened.

3 / 5

Actionability

Concrete specifics exist ("use `checkbox`, not `check-box`"; "native `<button>`, `<input>`, `<select>`"), but the Check step ("Search for any role attributes that use non-standard or misspelled ARIA role values") provides no executable technique (grep pattern, axe, DevTools inspection), and all code examples are deferred to the reference file rather than included inline.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a clearly labeled, coherent sequence appropriate to this single-purpose review skill. Verification is mentioned ("note how to verify the fix with browser accessibility tooling") but only in passing within Code Review rather than as an explicit checkpoint step, so it falls just short of a 5.

4 / 5

Progressive Disclosure

"For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" is a well-signaled, one-level-deep reference to a real file that verifiably contains the code examples and details promised. The body is a concise overview with the bulk appropriately split out, making navigation easy.

5 / 5

Total

15

/

20

Passed

Description

75%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.

The description is explicit about both what to do and when to trigger, with concrete domain-specific actions and keywords. Its main weaknesses are the grammatically garbled embedded rule title in the trigger clause and missing common accessibility synonyms.

Suggestions

Rewrite the trigger clause so the rule name reads naturally, e.g. "Use when reviewing rendered HTML, interactive components, or design-system patterns for valid ARIA role values."

Add common natural trigger terms such as "accessibility", "a11y", or "WCAG" to broaden keyword coverage.

State the core capability explicitly (identify and fix invalid or misspelled ARIA roles) rather than implying it through the rule title.

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 the core action for the rule itself is only implied via the awkward phrase "related to Use valid ARIA role values", leaving minor gaps in coverage.

4 / 5

Completeness

Both the what ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") and the when ("Use when reviewing rendered HTML, interactive components, or design-system patterns...") are explicitly present. Not a 5 because the when-clause embeds the rule title mid-sentence ("patterns related to Use valid ARIA role values"), reading mechanically rather than as a natural concrete trigger phrase.

4 / 5

Trigger Term Quality

Natural terms like "rendered HTML", "interactive components", "ARIA role values", and "screen-reader output" are present, but common variations users say in this domain ("accessibility", "a11y", "WCAG") are missing.

4 / 5

Distinctiveness Conflict Risk

"ARIA role values" carves out a clear niche with distinct triggers, but the broad review contexts ("rendered HTML, interactive components, or design-system patterns") create minor overlap risk with closely related accessibility-review skills.

4 / 5

Total

16

/

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-roles/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.