CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aria-valid-attr-value

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

Quality

80%

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-valid-attr-value/SKILL.md
SKILL.md
Quality
Evals
Security

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 lean, well-structured review skill: the Quick Reference bullets name the three concrete failure modes, the Check/Fix/Explain/Code Review sections form a coherent sequence, and full details are correctly pushed to a real one-level-deep reference file. Main weaknesses are minor — a slightly redundant intro sentence, no explicit post-fix validation step, and no inline markup example or named tool in the body itself.

Suggestions

Add one compact inline contrast example (e.g., `aria-expanded="yes"` → `aria-expanded="true"`) to the Check section so the body is self-sufficient without opening the reference.

Make verification an explicit step, e.g. 'After fixing, re-inspect the element in the browser accessibility tree or re-run axe/Lighthouse' — the tooling is currently only named in references/rule.md.

Drop or tighten the opening explanation of why invalid values break assistive technologies; Claude already knows this and it duplicates the reference's 'Why It Matters' section.

DimensionReasoningScore

Conciseness

The body is short and every section is terse (Check/Fix/Explain are 1-2 sentences), matching 'Efficient; minor instances of over-explanation that could be trimmed' — the opening sentence 'Invalid attribute values cause ARIA properties to be ignored or misinterpreted by assistive technologies' explains a concept Claude already knows, and Quick Reference partially duplicates the Check section. Not a 5 because of that mild redundancy; not a 3 because nothing is padded and the bulk of detail is correctly deferred.

4 / 5

Actionability

Quick Reference gives concrete, checkable guidance: 'Ensure ARIA attribute values (like `aria-expanded="true"`) are valid', 'Avoid using "yes/no" where "true/false" is required', 'Check that IDs referenced in `aria-labelledby` or `aria-owns` actually exist'. This fits 'Mostly executable guidance ... with minor gaps' — the gaps are that no inline invalid/valid markup example or named validation tool appears in the body (axe/Lighthouse live only in the reference). Not a 3: the key failure modes are all specifically stated, and per the rubric's instruction-skill note, absence of code is not penalized when guidance is actionable.

4 / 5

Workflow Clarity

A clear review sequence is present — Check, then Fix, then Explain, then Code Review — with verification mentioned ('note how to verify the fix with browser accessibility tooling or assistive tech'). This matches 'Clear sequence with most checkpoints present; minor validation gaps': verification is invoked but not as an explicit post-fix validation step with a command. Not a 5 because there is a multi-phase process yet no explicit checkpoint (e.g., re-run the accessibility check after fixing); not a 3 because the phases are unambiguous and this is a non-destructive review skill, so no cap applies.

4 / 5

Progressive Disclosure

The body is a concise overview and defers detail via a clearly signaled, one-level-deep pointer: 'For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`', and that file exists in the bundle with exactly that content (code examples, exceptions, standards, verification). Matches 'Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation' — no nested references, no content that belongs in a separate file inlined.

5 / 5

Total

17

/

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.

A solid description with an explicit 'Use when' trigger, concrete review actions, and strong domain keywords. Its main flaw is the mechanical embedding of the rule title ('related to Use valid values for ARIA attributes'), which obscures the core capability and makes the sentence read like template output rather than a natural capability statement.

Suggestions

Rewrite the embedded title as a direct capability statement, e.g. 'Validates that ARIA attribute values use the types required by the ARIA spec (booleans, integers, ID references)'.

Add the natural umbrella terms users actually say — 'accessibility' and 'a11y' — to the trigger clause.

Trim the generic tail ('keyboard behavior, focus flow, accessible names, and screen-reader output') to reduce overlap with sibling accessibility skills and sharpen the niche.

DimensionReasoningScore

Specificity

It lists several concrete actions — 'Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant' — within a concrete domain (ARIA attribute values in rendered HTML), fitting 'Lists several specific actions; minor gaps in coverage'. Not a 5 because the core action (validating ARIA attribute values against allowed types) is never stated directly, only implied via the awkwardly embedded rule title 'related to Use valid values for ARIA attributes'; not a 3 because far more than 1-2 actions are named.

4 / 5

Completeness

Both parts are explicit: the trigger 'Use when reviewing rendered HTML, interactive components, or design-system patterns related to...' answers 'when', and 'Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output' answers 'what'. Fits 'Has both what and when; when could be more explicit or specific' — the 'when' is strong but the 'what' is procedural and the embedded phrase 'Use valid values for ARIA attributes' muddles the actual capability, keeping it below the anchor-5 example's clarity.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'rendered HTML', 'interactive components', 'design-system patterns', 'ARIA attributes', 'keyboard behavior', 'focus flow', 'accessible names', 'screen-reader output' — terms a user would plausibly say. Not a 5 because common umbrella terms and synonyms like 'accessibility', 'a11y', or 'ARIA values' are missing; not a 3 because coverage goes well beyond a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

The ARIA attribute-validity niche is clear and distinct from most skills, matching 'Mostly distinct; minor overlap risk with closely related skills'. Not a 5 because the broad tail 'keyboard behavior, focus flow, accessible names, and screen-reader output' bleeds into general accessibility-review territory and could collide with sibling accessibility rules that share that boilerplate.

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-valid-attr-value/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.