CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aria-labels

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

Quality

70%

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-labels/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 a well-structured, appropriately short overview that correctly delegates code examples and verification detail to a real one-level-deep reference file, giving excellent progressive disclosure and a clear check/fix/review sequence. Weaknesses are concentrated in the body itself: motivational filler, a vague 'Explain' section, an awkwardly repeated rule title, and no directly executable inline guidance (no code, no named tools).

Suggestions

Cut the motivational intro sentence and the vague 'Explain' section ('Explain how clear labels... improve accessibility and general usability') — Claude already knows why labels matter; keep only operational guidance.

Add minimal executable substance to the body: a short good/bad button-labeling snippet or the concrete commands ('run axe or Lighthouse', 'inspect the accessibility tree') instead of the bare directive 'Audit all interactive elements'.

Fix the broken phrasing in the Code Review section, which repeats the rule title verbatim mid-sentence ('interactive states that affect Provide accessible names for all interactive elements').

DimensionReasoningScore

Conciseness

Mostly efficient short body, but includes unnecessary explanation: the motivational intro ('Interactive elements are the core of web navigation; without names, they become "mystery meat"...'), the vague filler 'Explain' section, and the awkward verbatim repetition of the rule title in Code Review ('interactive states that affect Provide accessible names for all interactive elements'). Matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trimming of level 4.

3 / 5

Actionability

Some concrete guidance exists — 'Add descriptive text content or `aria-label` attributes', and Quick Reference names generic labels to avoid ('Click Here', 'More') — but it is incomplete: no inline code example, no named tools (axe/Lighthouse live only in the reference file), and the Check step ('Audit all interactive elements... for missing or unhelpful accessible names') is high-level direction without specific steps. Not 2 because concrete specifics like aria-label and example bad names are present; not 4 because nothing in the body is directly executable.

3 / 5

Workflow Clarity

A clear Check → Fix → Explain → Code Review sequence with checkpoints implied ('note how to verify the fix with browser accessibility tooling or assistive tech'). Not 5 because verification/validation is only mentioned and deferred to the reference file rather than stated as explicit inline steps; not 3 because the sequence is clear, organized, and verification is at least signaled (this is a review skill, so the destructive/batch cap does not apply).

4 / 5

Progressive Disclosure

The body is a concise overview with well-organized sections, and details are split into a single, clearly signaled, one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`' — which exists in the bundle and contains the code examples and verification steps. Matches 'clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'.

5 / 5

Total

15

/

20

Passed

Description

63%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 has a clear 'Use when...' trigger and a list of concrete inspection actions, but the grammatically broken embedding of the rule title ('related to Provide accessible names for all interactive elements') degrades both the 'what' and the trigger phrasing. Key domain synonyms (accessibility, a11y, aria-label, WCAG) are absent, and the broad inspection scope raises conflict risk with sibling accessibility skills.

Suggestions

Add the natural trigger synonyms users actually say — 'accessibility', 'a11y', 'aria-label', 'WCAG' — since none of these currently appear in the description.

Rewrite the embedded rule title into a grammatical clause (e.g., 'Use when reviewing rendered HTML for accessible names of interactive elements') instead of 'related to Provide accessible names for all interactive elements'.

Narrow the scope to naming to reduce overlap: 'keyboard behavior' and 'focus flow' belong to sibling accessibility rules and would cause this skill to trigger for the wrong rule.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output' — plus the reviewing action. Not 5 because coverage is one-sided (inspection only, no fix actions) and the embedded rule title 'related to Provide accessible names for all interactive elements' breaks the action phrasing; not 3 because it clearly exceeds 1-2 concrete actions.

4 / 5

Completeness

Has both an explicit 'when' ('Use when reviewing rendered HTML, interactive components, or design-system patterns') and a 'what' (check native semantics, inspect keyboard behavior, focus flow, accessible names, screen-reader output). Not 5 because the core 'what' — giving interactive elements accessible names — is only conveyed via the awkwardly embedded rule title, and the trigger phrasing is muddied by that broken sentence; the level-4 anchor ('when' could be more explicit or specific) fits better.

4 / 5

Trigger Term Quality

Contains relevant keywords ('rendered HTML', 'interactive components', 'accessible names', 'keyboard behavior', 'focus flow', 'screen-reader') but misses the most natural variations users actually say: 'accessibility', 'a11y', 'aria-label', 'aria', and 'WCAG' — the word 'accessibility' itself never appears. Matches 'some relevant keywords but missing common variations or synonyms' rather than the 'a few natural terms missing' of level 4.

3 / 5

Distinctiveness Conflict Risk

The naming focus ('accessible names') is somewhat specific, but 'inspect keyboard behavior, focus flow, and screen-reader output' overlaps heavily with sibling accessibility rules (keyboard navigation, focus order), so sibling skills in the same bundle would trigger on the same phrases. Matches 'somewhat specific but could still overlap with similar skills' — not 4, since the overlap is with closely related skills on multiple listed dimensions, not a minor risk.

3 / 5

Total

14

/

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