CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

modal-accessibility

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

Quality

78%

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/modal-accessibility/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 overview body with excellent progressive disclosure to a real, one-level-deep reference file. Its weaknesses are structural redundancy (four sections restating the same requirements) and a workflow that presents check/fix/review as parallel modes without explicit validation checkpoints in the body itself.

Suggestions

Add an explicit verification sequence in the body — e.g., the manual keyboard test steps from references/rule.md (open via Enter/Space, tab through without focus escaping, press Escape, confirm focus returns to the trigger) — so the workflow has concrete checkpoints.

Merge or cut the redundant Check/Fix/Explain sections, which each restate the four Quick Reference requirements; a single checklist plus a pointer to references/rule.md for fixes would tighten the body.

Inline one small concrete markup snippet (a role='dialog'/aria-modal='true' container with aria-labelledby) so the Fix guidance is executable before deferring to the reference.

DimensionReasoningScore

Conciseness

The ~45-line body is lean with no explanations of concepts Claude already knows, and every section is 1-2 sentences. It is a 4 rather than 5 because the Check, Fix, Explain, and Code Review sections each restate the same four requirements already given in Quick Reference ("Verify modals have proper ARIA roles, focus trapping, keyboard dismissal (Escape), and return focus on close"), which could be trimmed.

4 / 5

Actionability

Quick Reference gives concrete, exact items ("role='dialog' and aria-modal='true'", "Close on Escape key press and return focus to trigger element") and Code Review specifies exactly what to flag and to "note how to verify the fix with browser accessibility tooling or assistive tech". Not a 5 because the Fix and Check sections are high-level ("Implement accessible modals using role='dialog'...") with all executable detail delegated to references/rule.md.

4 / 5

Workflow Clarity

The Check/Fix/Explain/Code Review sections imply a check-then-fix-then-review flow but read as parallel task modes rather than a sequenced process, and validation checkpoints are only implicit — the actual verification steps (open via keyboard, tab through, press Escape, confirm focus returns) live in references/rule.md while the body only alludes to them. This matches 'steps present but checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

The body is a genuinely concise overview and all implementation detail (code examples, framework guidance, verification steps) is split into references/rule.md, which exists and contains exactly that content — a well-signaled, one-level-deep reference ("For full implementation details, code examples, and framework-specific guidance, see references/rule.md") with easy navigation.

5 / 5

Total

16

/

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 explicit what and when clauses, concrete inspection actions, and good natural trigger terms. Its main defects are a garbled trigger phrase ('related to Make modal dialogs keyboard accessible') and missing common synonyms like a11y or ARIA.

Suggestions

Fix the ungrammatical trigger phrase "related to Make modal dialogs keyboard accessible" — e.g., "related to making modal dialogs keyboard accessible" — the odd capitalization reads as a template substitution error and weakens the when clause's clarity.

Add common synonyms users naturally say — "a11y", "ARIA", "focus trap", "dialog" — to broaden keyword coverage toward the top anchor.

Consider stating one remediation-oriented action (e.g., "implement focus trapping and Escape-key dismissal") so the what covers both checking and fixing.

DimensionReasoningScore

Specificity

"Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" lists several concrete inspection actions with exact targets. It stays at 4 rather than 5 because coverage is inspection-only — no remediation or output actions are stated.

4 / 5

Completeness

Both parts are explicit: the what ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") and the when ("Use when reviewing rendered HTML, interactive components, or design-system patterns..."). It falls short of 5 because the when clause's trigger phrase "related to Make modal dialogs keyboard accessible" is grammatically garbled, slightly muddying the trigger.

4 / 5

Trigger Term Quality

Natural terms users would say are present: "modal dialogs", "keyboard accessible", "focus flow", "screen-reader", "interactive components", "design-system patterns". A few common variations are missing ("a11y", "ARIA", "focus trap"), matching the 'good keyword coverage; a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche (modal dialog keyboard accessibility) with distinct triggers like modal, focus, Escape, screen-reader. Minor overlap risk remains with closely related accessibility-review skills (e.g., focus order or landmark rules), fitting the 'mostly distinct' anchor rather than 'minimal conflict risk'.

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/modal-accessibility/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.