scanning-for-accessibility-issues

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill scanning-for-accessibility-issues

This skill enables Claude to perform comprehensive accessibility audits. It uses the accessibility-test-scanner plugin to identify WCAG 2.1/2.2 compliance issues, validate ARIA attributes, check keyboard navigation, and assess screen reader compatibility. Use this skill when the user requests an accessibility scan, audit, or compliance check, or when terms like "WCAG", "ARIA", "screen reader", "accessibility testing", or "a11y" are mentioned. It provides actionable insights for improving web application accessibility.

60%

Overall

Validation — 81%

Implementation — 20%

Activation — 100%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning
body_output_format	No obvious output/return/format terms detected; consider specifying expected outputs	Warning

	Total	13 / 16 Passed

Implementation

20%

This skill content is overly verbose and lacks actionable guidance. It describes what the skill does conceptually but fails to provide the concrete command syntax, parameters, or example outputs that Claude would need to actually execute accessibility scans. The content reads more like marketing copy than technical instructions.

Suggestions

Add the actual command syntax with parameters: e.g., `a11y-scan --url <url> --standard wcag21aa --format json`

Include a concrete example of scan output and how to interpret the results

Remove the 'How It Works', 'When to Use', and 'Best Practices' sections - this information is either obvious or already in the description

Add validation steps: how to verify the scan completed successfully, how to handle common errors

Dimension	Reasoning	Score
Conciseness	Verbose and padded with unnecessary context. Explains obvious concepts like 'How It Works' steps that Claude doesn't need, includes redundant 'When to Use' section that duplicates the description, and 'Best Practices' contains generic advice Claude already knows.	1 / 3
Actionability	No concrete, executable guidance provided. References 'a11y-scan' command but never shows actual syntax, parameters, or example output. The examples describe what will happen rather than showing how to do it.	1 / 3
Workflow Clarity	Steps are listed in a logical sequence but lack validation checkpoints. No guidance on what to do if the scan fails, how to interpret specific error types, or how to verify fixes were successful.	2 / 3
Progressive Disclosure	Content is organized into sections but everything is inline in one file. No references to detailed documentation for WCAG guidelines, ARIA patterns, or advanced configuration options that would benefit from separate files.	2 / 3
	Total	6 / 12 Passed

Activation

100%

This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes comprehensive trigger terms that users would naturally use, explicitly states both what the skill does and when to use it, and occupies a clear niche that distinguishes it from other skills. The description uses proper third-person voice throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'identify WCAG 2.1/2.2 compliance issues, validate ARIA attributes, check keyboard navigation, and assess screen reader compatibility.' Also mentions the specific tool used (accessibility-test-scanner plugin).	3 / 3
Completeness	Clearly answers both what ('perform comprehensive accessibility audits', 'identify WCAG 2.1/2.2 compliance issues', etc.) AND when with explicit 'Use this skill when...' clause listing specific trigger scenarios and terms.	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'accessibility scan', 'audit', 'compliance check', 'WCAG', 'ARIA', 'screen reader', 'accessibility testing', 'a11y'. These are terms users would naturally use when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on accessibility testing with distinct triggers like 'WCAG', 'ARIA', 'a11y', and 'screen reader'. Unlikely to conflict with general testing or code review skills due to the specific accessibility domain focus.	3 / 3
	Total	12 / 12 Passed

Reviewed

15 days ago

Table of Contents

Validation Implementation Activation

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.