CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aria-hidden-focus

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Remove focusable elements from aria-hidden containers. 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-hidden-focus/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 an exemplary one-level reference split keeping SKILL.md lean, but redundancy (duplicated fix advice, a description-parroting Code Review section, an Explain meta-section) and a Check step lacking an executable scan method or in-body verification keep the guidance from being fully actionable.

Suggestions

Merge the Quick Reference and Fix bullets into one statement of the rule and fix, and delete the Code Review paragraph's verbatim restatement of the description.

Make the Check step executable: list the focusable selector (a[href], button, input, select, textarea, [tabindex]) or name the axe rule (aria-hidden-focus) instead of just "links, buttons, or inputs".

Add an explicit verify step in the body (re-run the checker or keyboard-tab the container after applying tabindex="-1"/inert) instead of leaving verification only in references/rule.md.

DimensionReasoningScore

Conciseness

The opening "When a keyboard user tabs into an aria-hidden element, the screen reader remains silent..." explains a concept Claude already knows, the tabindex="-1"/inert advice is duplicated between Quick Reference and Fix, the "Explain" section is a meta-instruction rather than content, and the Code Review paragraph restates the description nearly verbatim. Mostly efficient but with repeated unnecessary material — the 3 anchor, not 4 (only minor over-explanation).

3 / 5

Actionability

"Scan aria-hidden=\"true\" containers for focusable elements like links, buttons, or inputs" and "Add tabindex=\"-1\" ... or use the inert attribute" are concrete, but the body gives no executable scan method (a focusable-element selector or an axe rule id) and no code example, deferring all details to references/rule.md. Some concrete guidance but incomplete — the 3 anchor, not 4 (mostly executable guidance).

3 / 5

Workflow Clarity

The Check → Fix sequence is present and ordered, and "note how to verify the fix with browser accessibility tooling" gestures at verification, but no explicit verification checkpoint or feedback loop appears in the body — it lives only in references/rule.md and is not surfaced as a step. Steps listed with checkpoints missing — the 3 anchor, not 4. This is a review skill, not a destructive/batch operation, so no lower cap applies.

3 / 5

Progressive Disclosure

A ~44-line body with well-organized sections (Quick Reference, Check, Fix, Explain, Code Review) and a single, clearly signaled, one-level-deep pointer — "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — which exists and appropriately holds the code examples, exceptions, and verification detail. This matches the 5 anchor and the simple-skill scoring note.

5 / 5

Total

14

/

20

Passed

Description

71%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 provides an explicit third-person trigger clause and several concrete checking actions, so both what and when are answered. However, the garbled rule-name concatenation, a category-generic what, and a trigger template that would collide with sibling accessibility skills keep it a notch below excellent.

Suggestions

Rewrite the trigger to name the rule naturally, e.g. "Use when reviewing markup where aria-hidden containers, ghost focus, or hidden focusable elements come up", so it is distinct from sibling rule templates.

Include fix-side actions in the description (e.g. "flag focusable children and apply tabindex=\"-1\" or inert") so the what reflects the skill's full scope.

Add natural trigger synonyms such as "accessibility", "tab order", and "focusable" to broaden keyword coverage.

DimensionReasoningScore

Specificity

"Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" lists several concrete checking actions in the domain. It falls short of the 5 anchor because the template-concatenated phrase "related to Remove focusable elements from aria-hidden containers" is awkward and no fix-side actions (e.g. tabindex="-1", inert) are named, but it clearly exceeds the 3 anchor's 1-2 actions.

4 / 5

Completeness

Both parts are present and explicit: the when via "Use when reviewing rendered HTML, interactive components, or design-system patterns" and the what via "Check native semantics first, then inspect keyboard behavior, focus flow...". It sits between the 4 and 5 anchors — the when is strong, but the what is category-generic checking rather than this rule's specific action, and the awkward embedded rule name weakens the explicitness.

4 / 5

Trigger Term Quality

Natural terms like "reviewing rendered HTML", "interactive components", "design-system patterns", "keyboard behavior", "focus flow", and "screen-reader output" give good coverage, matching the 4 anchor. It is not a 5 because common variations users would say — "accessibility", "a11y", "tab order", "focusable" — are absent.

4 / 5

Distinctiveness Conflict Risk

"Use when reviewing rendered HTML, interactive components, or design-system patterns" is a shared template that sibling accessibility rules from the same source would repeat verbatim; only the embedded rule name distinguishes it. Somewhat specific (aria-hidden, keyboard behavior) but overlapping with similar accessibility skills — the 3 anchor, not 4 ("mostly distinct").

3 / 5

Total

15

/

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-hidden-focus/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.