CtrlK
BlogDocsLog inGet started
Tessl Logo

fixing-accessibility

Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance.

95

1.06x
Quality

93%

Does it follow best practices?

Impact

99%

1.06x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-3

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

A tight, well-organized accessibility ruleset with concrete before/after examples and a priority table. The main gap is the absence of an explicit validate-after-fix feedback loop in the review workflow.

Suggestions

Add an explicit verification step to the review workflow, e.g. after applying a fix, re-check the snippet to confirm the violation is resolved before moving on.

Add a short checklist of the top critical checks (names, keyboard, focus) at the end of "review guidance" so Claude can confirm coverage rather than relying on the scattered rules.

DimensionReasoningScore

Conciseness

Lean rule-based content with no padding explaining concepts Claude already knows; every section earns its place (priority table, terse rules, before/after snippets).

3 / 3

Actionability

Concrete, copy-paste-ready before/after HTML in "common fixes" plus specific actionable rule checks ("icon-only buttons must have aria-label", "do not use tabindex greater than 0"). It is below 3 only in that the bulk is guidance rather than executable commands, but as an instruction skill the guidance is specific and actionable.

3 / 3

Workflow Clarity

Invocation modes and a structured review output (violations / why / fix) are sequenced, but there is no explicit verification checkpoint that a fix actually resolves the violation. Not 3 because validation/feedback loops are implicit rather than stated.

2 / 3

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-organized into clearly labeled sections (priority table, quick reference, common fixes, review guidance), which per the simple-skill note scores 3 without external references.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 concise, concrete, and well-triggered: it names specific accessibility actions and gives an explicit "Use when" clause. It cleanly answers both what and when without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors" — matching the anchor for enumerating specific actions.

3 / 3

Completeness

Explicitly states what ("Audit and fix HTML accessibility issues...") and when ("Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance"), satisfying both halves.

3 / 3

Trigger Term Quality

Covers natural terms users would say — "ARIA labels", "keyboard navigation", "forms", "dialogs", "WCAG compliance" — with good variation rather than jargon.

3 / 3

Distinctiveness Conflict Risk

A clear HTML accessibility niche with distinct triggers (ARIA, keyboard, WCAG) makes it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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
ibelick/ui-skills
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.