aria-live-regions

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Announce dynamic content with ARIA live regions. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/aria-live-regions/SKILL.md

Quality

Content

71%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 well-structured, lean review skill that appropriately pushes detail into references/rule.md. Its main weakness is actionability: the Check/Fix/Code Review sections are high-level and the executable code is one level deep in the reference rather than surfaced in the body.

Suggestions

Add 1–2 short inline code snippets (e.g. a polite status region and a role='alert' error region) to the body so the most common fix is copy-paste ready without opening the reference.

Tighten the Check and Fix sections from generic verbs ('use aria-live regions appropriately') to concrete, testable criteria (e.g. 'confirm the live region element exists in the DOM before content is inserted').

Move or trim the opening motivation sentence ('Without live regions, screen reader users miss dynamic updates entirely...') since it explains a concept Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, but the opening 'Without live regions, screen reader users miss dynamic updates entirely...' sentence is a minor over-explanation of motivation Claude already knows.	4 / 5
Actionability	The Quick Reference gives concrete attribute guidance (aria-live='polite'/'assertive', role='alert'/'status'), but the Check/Fix/Code Review sections stay high-level ('use aria-live regions appropriately') and the executable code lives in the reference rather than the body.	3 / 5
Workflow Clarity	Check → Fix → Explain → Code Review provides a clear review sequence with a verification hint ('note how to verify the fix with browser accessibility tooling'), though verification detail is delegated to the reference.	4 / 5
Progressive Disclosure	SKILL.md is a concise overview with a well-signaled one-level-deep pointer to references/rule.md (a real file containing the full examples and verification steps), making navigation easy.	5 / 5
	Total	16 / 20 Passed

Description

83%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 strong description with explicit 'Use when...' trigger guidance and several concrete review actions. It is clearly scoped to ARIA live regions accessibility with only minor overlap risk against related a11y skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete review actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output') rather than vague language, with only minor coverage gaps.	4 / 5
Completeness	Explicitly answers both: 'when' via 'Use when reviewing rendered HTML, interactive components, or design-system patterns related to...' and 'what' via the concrete inspection actions, with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('rendered HTML', 'interactive components', 'design-system patterns', 'ARIA live regions', 'screen-reader output'), though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	The ARIA live regions niche is mostly distinct, but broadening to 'inspect keyboard behavior, focus flow' creates minor overlap risk with sibling accessibility skills.	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/aria-live-regions/SKILL.md
Commit: 30756a7

Reviewed: 20 days ago

Table of Contents

Discovery Implementation Validation

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.