CtrlK
BlogDocsLog inGet started
Tessl Logo

accessibility-wcag

Web accessibility patterns for WCAG 2.2 compliance including ARIA, keyboard navigation, screen readers, and testing

82

1.06x
Quality

73%

Does it follow best practices?

Impact

95%

1.06x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/accessibility-wcag/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, highly actionable, and well-organized with executable patterns and a verification checklist, but as a self-contained 211-line catalog it lacks an explicit multi-step workflow with feedback loops and makes no use of progressive disclosure through reference files.

Suggestions

Add a short "Implementation workflow" section with an explicit sequence — audit landmarks → fix ARIA/keyboard → verify contrast → test with screen reader and keyboard only — with a re-check loop on failure, to lift workflow_clarity.

Move the larger worked examples (Modal/Tabs TSX, full form) into reference files under references/ and link to them from a lean overview, so progressive disclosure is used and SKILL.md stays scannable.

Cross-reference the final Checklist from each pattern section so verification is signaled at the point of use.

DimensionReasoningScore

Conciseness

The body is lean and code-heavy with only brief, value-dense prose (e.g. "WCAG AA requires 4.5:1 contrast for normal text, 3:1 for large text"), avoiding explanations of concepts Claude already knows; it does not pad, so it sits at the efficient level 3 rather than the partly-unnecessary level 2.

3 / 3

Actionability

It provides fully executable, complete HTML/TSX/CSS patterns (Modal with role="dialog", Tabs with arrow-key handling, handleArrowKeys, SignupForm, focus-visible contrast CSS) that are copy-paste ready, matching the "fully executable code" anchor.

3 / 3

Workflow Clarity

Content is organized into clear sections and ends with a verification Checklist (including "Page tested with screen reader… and keyboard only"), but it is a patterns catalog rather than a sequenced multi-step workflow with explicit validate→fix→retry feedback loops, so it stops short of level 3 and is above the unclear level 1.

2 / 3

Progressive Disclosure

The 211-line body is well organized into seven clear sections with no nested-reference problem, but everything is inline in a single file with no progressive disclosure via reference files, and the under-50-line exception does not apply, so it sits at level 2 rather than the well-split level 3.

2 / 3

Total

10

/

12

Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and clearly niched within web accessibility, but it lacks an explicit trigger/"Use when" clause and omits common variations such as "a11y", which hold trigger-term quality and completeness at the mid-level.

Suggestions

Add an explicit "Use when…" clause naming natural triggers, e.g. "Use when making UIs WCAG-compliant, fixing accessibility issues, or when the user mentions ARIA, screen readers, keyboard navigation, or a11y."

Include the common abbreviation "a11y" and variations like "accessibility audit" to improve trigger-term coverage.

Reframe the topic list slightly as actions (e.g. "Apply ARIA roles, implement keyboard navigation, verify screen-reader support") to strengthen specificity.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capability areas — "ARIA, keyboard navigation, screen readers, and testing" — rather than vague language, matching the anchor for listing several specific items; it is above level 2 because it goes beyond naming only a domain and a couple of actions.

3 / 3

Completeness

It clearly answers WHAT ("Web accessibility patterns for WCAG 2.2 compliance including ARIA, keyboard navigation, screen readers, and testing") but provides no explicit "when"/"Use when…" trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Terms like "Web accessibility", "WCAG 2.2", "ARIA", "keyboard navigation", and "screen readers" are natural, but coverage misses common variations such as "a11y" and there is no explicit trigger clause, so it does not reach the full-coverage level 3.

2 / 3

Distinctiveness Conflict Risk

The accessibility/WCAG niche is clearly delimited and uses domain-specific triggers unlikely to fire for unrelated skills, matching the "clear niche with distinct triggers" anchor.

3 / 3

Total

10

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rohitg00/awesome-claude-code-toolkit
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.