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.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is fixing-accessibility in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

96%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.

Lean, actionable, and well-organized guidance with concrete before/after examples and a clear review process. The only gap is that the nine category rule-lists are inlined rather than split into a references file for progressive disclosure.

Suggestions

Move the nine rule-category lists into a references/rules.md file and keep SKILL.md as an overview that links to it, improving progressive disclosure for the longer-than-50-line body.

Drop the redundant one-line intro 'Fix accessibility issues.' that restates the skill name and frontmatter description.

Add a short validation step to the review workflow (e.g. 'Re-check the element still functions after each fix') to strengthen the feedback loop even for non-destructive edits.

DimensionReasoningScore

Conciseness

Terse bullet rules and before/after snippets assume Claude's competence; no padding explaining what accessibility or ARIA is. The only near-fluff is the one-line intro 'Fix accessibility issues.' which restates the title.

5 / 5

Actionability

Provides copy-paste-ready before/after HTML for the common cases (icon-only button, div-as-button, form error linking) plus concrete rule bullets (aria-describedby, aria-invalid, tabindex > 0, focus trapping) that map directly to edits.

5 / 5

Workflow Clarity

A single-purpose audit/review skill (no batch or destructive operation) with an explicit review sequence — 'fix critical issues first', 'quote the exact snippet, state the failure, propose a small fix' — qualifying for the simple-skill exception; no validation checkpoint is required.

5 / 5

Progressive Disclosure

Well-sectioned single file with no nested references and good navigation, but the nine inlined rule-category reference lists (~90 lines) are bulk that a longer skill would typically split into a references file; no bundle files are present to offload it.

4 / 5

Total

19

/

20

Passed

Description

92%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 states concrete capabilities and an explicit 'Use when' trigger clause with minimal conflict risk. Adding a few common synonyms (a11y, screen reader, accessibility audit) would perfect trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in the domain — 'Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors' — giving comprehensive coverage rather than vague verbs.

5 / 5

Completeness

Explicitly answers both what ('Audit and fix HTML accessibility issues including...') and when ('Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('adding interactive controls, forms, dialogs', 'reviewing WCAG compliance', 'ARIA') but omits some synonyms (e.g. 'a11y', 'screen reader', 'accessibility audit') that would round it to 5.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche (HTML accessibility / WCAG) with distinct, specific triggers unlikely to fire for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.