CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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-organized, lean overview that delegates detail to a verified one-level reference and gives concrete actionable guidance. The only weakness is a mildly redundant "Explain" section that overlaps the opening justification.

Suggestions

Remove or merge the "Explain" section, since its content restates the ghost-focus rationale already given in the opening sentence, saving tokens without losing information.

Consider adding one short inline HTML snippet showing the incorrect vs. correct (tabindex="-1" / inert) markup so the "Fix" is copy-paste ready without requiring a jump to the reference.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the "Explain" section ("Explain why focusable elements inside aria-hidden containers cause confusion...") is a meta-instruction that overlaps with the opening justification sentence and could be tightened or removed.

2 / 3

Actionability

Gives concrete, executable guidance with exact attribute values ("tabindex=\"-1\"" or "inert") and specific elements to scan (links, buttons, inputs); as an instruction-only skill the absence of inline code is not penalized because the guidance is actionable.

3 / 3

Workflow Clarity

A clear Check → Fix → Code Review sequence is present, with an explicit verification note ("verify the fix with browser accessibility tooling or assistive tech"); for a simple single-purpose review skill this is unambiguous.

3 / 3

Progressive Disclosure

The body is a concise overview that cleanly signals a single one-level-deep reference ("see references/rule.md"), which exists and holds the detailed implementation and code examples.

3 / 3

Total

11

/

12

Passed

Description

100%

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 well-crafted: it pairs an explicit 'Use when' trigger with concrete, specific review actions and occupies a clearly distinct accessibility niche. It scores at the top of the scale across all dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete review actions such as "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output," matching the anchor for listing several specific actions.

3 / 3

Completeness

Explicitly answers both parts: an explicit "Use when reviewing rendered HTML, interactive components, or design-system patterns..." trigger for when, and concrete inspection actions for what.

3 / 3

Trigger Term Quality

Contains natural terms an accessibility reviewer would say ("aria-hidden," "focusable elements," "keyboard behavior," "screen-reader output," "rendered HTML"), giving good coverage of likely user phrasing.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (focusable elements inside aria-hidden containers) with distinct accessibility triggers, making overlap with other skills unlikely.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.