CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aria-hidden-body

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Do not use aria-hidden on the document body. 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-hidden-body/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.

A compact, well-structured overview that appropriately delegates detail to a real one-level-deep reference file. Weaknesses are redundancy between the intro, Quick Reference, and 'Explain' sections, and a Check step that says what to look for but not how to detect it.

Suggestions

Add a concrete detection method to the Check section (e.g., inspect document.body.getAttribute('aria-hidden') in the rendered DOM or the browser accessibility tree, or run axe/Lighthouse) instead of the unactionable 'at any point in the lifecycle'.

Remove the 'Explain' section and the Quick Reference bullet that duplicate the opening paragraph's point about silencing the page for screen readers.

Merge the overlapping Check, Explain, and Code Review sections into one review sequence that ends with a verification step in the body.

DimensionReasoningScore

Conciseness

The body is short, but the Quick Reference bullet 'Hiding the body makes the entire page invisible to assistive technologies' duplicates the opening paragraph, and the 'Explain' section ('Explain the catastrophic impact...') restates it a third time without adding guidance. This is more than minor trimmable padding, so anchor 3 rather than 4.

3 / 5

Actionability

The Fix is concrete ('Remove aria-hidden="true" from the <body> and use it only on specific background containers when modals are open'), but the Check gives no detection method for 'at any point in the lifecycle' (no command, snippet, or tooling pointer in the body), and 'Explain'/'Code Review' describe rather than instruct. Missing key details, so anchor 3 rather than 4.

3 / 5

Workflow Clarity

A simple single-task skill with an unambiguous Check-then-Fix sequence. Not 5 because the Check, Explain, and Code Review sections overlap in content and no verification step appears in the body itself (it lives in references/rule.md); not a destructive/batch operation, so no cap applies.

4 / 5

Progressive Disclosure

The body is a concise overview under 50 lines with well-organized sections, and it clearly signals a single one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') that exists in the bundle. Content is appropriately split between overview and detail file.

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.

A solid description with an explicit 'Use when' trigger clause and several concrete review actions. Its main weaknesses are the awkward embedding of the rule title as a noun phrase (weakening the explicit 'what') and missing common synonyms like 'accessibility', 'a11y', or 'modal' in the trigger terms.

Suggestions

State the capability directly (e.g., 'Flags and removes aria-hidden="true" from the document body...') instead of embedding the capitalized rule title as a noun phrase in 'related to Do not use aria-hidden on the document body'.

Add natural trigger synonyms such as 'accessibility', 'a11y', 'modal', or 'screen readers' to broaden the terms users would actually say.

DimensionReasoningScore

Specificity

Lists several concrete actions ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") within a named domain. Not 5 because the core capability is conveyed indirectly by embedding the rule title ("related to Do not use aria-hidden on the document body") rather than being comprehensively stated; not 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

Both what and when are present: an explicit trigger clause ("Use when reviewing rendered HTML, interactive components, or design-system patterns") and concrete actions. Not 5 because the 'what' leans on the awkwardly embedded rule title instead of clearly stating the skill's output (e.g., flagging/fixing aria-hidden on body).

4 / 5

Trigger Term Quality

Includes good natural keywords users would say: "aria-hidden", "screen-reader", "keyboard behavior", "focus flow", "rendered HTML". Not 5 because common variations like "accessibility", "a11y", "modal", and "screen readers" as standalone phrases are missing; not 3 because coverage exceeds just "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

The aria-hidden-on-body rule is a clear niche, but the generic lead-in "reviewing rendered HTML, interactive components, or design-system patterns" is shared phrasing that would overlap with closely related accessibility/frontend review skills. Minor overlap risk, so anchor 4 rather than 5.

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