check-accessibility

Check and verify accessibility compliance for Spark UI components. Use when the user wants to test accessibility, verify WCAG compliance, or fix accessibility issues.

Quality

71%

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 ./.cursor/skills/check-accessibility/SKILL.md

Quality

Content

61%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 genuinely executable automated-test commands, but it pads general WCAG knowledge Claude already knows and omits a re-test validation loop after fixing issues. Tightening the generic lists and adding a verify-after-fix checkpoint would meaningfully raise quality.

Suggestions

Add an explicit feedback loop: after 'Fix Issues', re-run 'npm run test:a11y' to confirm the fix passes before considering the work done.

Trim the 'Common Accessibility Requirements' and 'Manual Checks' sections to the non-obvious specifics, dropping restatements of general WCAG knowledge Claude already has.

Make the manual-checks guidance more concrete (e.g., specific keyboard sequences or expected focus order) rather than generic bullets like 'Test keyboard navigation'.

Dimension	Reasoning	Score
Conciseness	The automated-testing section is efficient, but 'Manual Checks', 'Common Accessibility Requirements', and 'Testing Tools' restate general WCAG knowledge Claude already knows ('All interactive elements must be keyboard accessible', 'Proper ARIA labels and roles'), so it is mostly efficient with some unnecessary explanation.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands ('npm run test:a11y -- tabs --workers 1') and names the exact component-key file, with only the manual-checks section lacking specifics — fitting mostly executable guidance with minor gaps.	4 / 5
Workflow Clarity	Steps are numbered (1-5) but the fix step has no validation/re-test checkpoint; because a11y testing is a batch operation, the missing validate→fix→retry feedback loop caps this at the anchor with sequence present but checkpoints missing or implicit.	3 / 5
Progressive Disclosure	Well-organized sections (When to Use, Instructions, Standards) with a single clearly-signaled one-level reference ('.cursor/rules/accessibility-standards.md'); good structure with minor organization gaps, just over the simple-skill line.	4 / 5
	Total	14 / 20 Passed

Description

82%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, well-scoped description that clearly states both capability and trigger conditions for Spark UI accessibility work. It is concise and distinct, with only minor room to broaden trigger-term synonyms and add more varied action verbs.

Dimension	Reasoning	Score
Specificity	Names the domain ('Spark UI components') and 1-2 concrete actions ('Check and verify accessibility compliance', 'fix accessibility issues'), but 'check' and 'verify' are near-synonyms so coverage is not comprehensive — matching the anchor naming domain plus 1-2 concrete actions.	3 / 5
Completeness	Explicitly answers both what ('Check and verify accessibility compliance for Spark UI components') and when ('Use when the user wants to test accessibility, verify WCAG compliance, or fix accessibility issues') with concrete trigger phrases, matching the top anchor closely.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('accessibility', 'WCAG compliance', 'test accessibility', 'fix accessibility issues') with good coverage; only minor variations like 'a11y' are absent, fitting the good-but-incomplete anchor.	4 / 5
Distinctiveness Conflict Risk	Scoped to 'Spark UI components' accessibility with distinct WCAG/a11y triggers, creating a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: leboncoin/spark-web
Path: .cursor/skills/check-accessibility/SKILL.md
Commit: ae95bee

Reviewed: 1 day 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.