accessibility-testing

Accessibility testing with axe-core and Playwright. Use when checking WCAG compliance, finding a11y issues, ensuring keyboard navigation, or testing screen reader compatibility.

Quality

80%

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/accessibility-testing/SKILL.md

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 highly actionable, code-first reference with executable examples across the a11y testing surface, held back by a monolithic inline recipe catalog and the absence of a validate/fix/re-scan feedback loop. Splitting recipe groups into the existing references structure would lift the weaker dimensions.

Suggestions

Move the keyboard-navigation, reporting, and CI recipe groups (and the inline HTML report template) into reference files, keeping SKILL.md as a concise overview that points to them one level deep.

Add an explicit feedback loop: after `analyze()`, if violations exist, log/failureSummary, fix the source, then re-run the scan until `results.violations` is empty.

De-duplicate the per-example `import`/`page.goto`/`AxeBuilder` boilerplate by showing one full setup once and trimming it from subsequent examples.

Dimension	Reasoning	Score
Conciseness	Body is overwhelmingly lean, executable TypeScript with almost no explanatory padding and no lecturing on what accessibility/WCAG is; not a 5 because the import/goto/AxeBuilder boilerplate repeats across ~12 examples and the inline HTML report template is padded.	4 / 5
Actionability	Fully executable, copy-paste-ready code covering the common cases (full/element/excluded scans, WCAG A/AA/AAA tag sets, specific rules, keyboard nav, contrast, forms, images, ARIA, reporting, CI); specific examples span the typical usage surface.	5 / 5
Workflow Clarity	Each recipe is a clear micro-workflow (goto, scan, assert) but there is no integrated multi-step process and no validate->fix->re-scan feedback loop, which would be natural for a11y testing; not 4 because checkpoints/feedback loops are absent, not 2 because individual steps are well defined.	3 / 5
Progressive Disclosure	Two real reference files are clearly signaled in a References section, but the 412-line body inlines ~15 near-identical recipe blocks and a long HTML template that could be split into reference files; structure is present but content that should be separate is inline.	3 / 5
	Total	15 / 20 Passed

Description

87%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 that clearly states the capability and provides an explicit 'Use when...' trigger clause with concrete, natural keywords. Minor room to improve specificity and trigger synonym coverage.

Dimension	Reasoning	Score
Specificity	Names the toolset ('axe-core and Playwright') and lists several concrete actions ('checking WCAG compliance, finding a11y issues, ensuring keyboard navigation, or testing screen reader compatibility'), with only minor coverage gaps; not a 5 because the lead 'Accessibility testing' is generic and the action list could be more comprehensive.	4 / 5
Completeness	Explicitly answers both what ('Accessibility testing with axe-core and Playwright' plus enumerated actions) and when via a concrete 'Use when...' clause with multiple trigger phrases, matching the anchor example pattern.	5 / 5
Trigger Term Quality	Includes natural user phrases ('WCAG compliance', 'a11y issues', 'keyboard navigation', 'screen reader compatibility') plus tool names; not a 5 because some synonyms/variants are missing (full word 'accessibility' vs 'a11y', 'ARIA', '508/ADA compliance').	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (a11y testing with axe-core/Playwright) with distinct triggers unlikely to fire for unrelated skills; minimal conflict risk.	5 / 5
	Total	18 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/accessibility-testing/SKILL.md
Commit: 93ed392

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.