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.

66

Quality

80%

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

68%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 concise, actionable accessibility rulebook with good structure and concrete code examples. Weakest area is workflow clarity: it offers priorities and a report format rather than an explicit sequenced review workflow with a re-verification checkpoint.

Suggestions

Add an explicit numbered review workflow (e.g. 1. scan controls for names, 2. check keyboard/focus, 3. quote violation + fix, 4. re-verify the fixed element) with a validation/re-check step.

Pair more of the rule bullets with a small before/after example, especially for forms/errors and announcements where the pattern is non-obvious.

Dedupe the 'prefer minimal/native, don't refactor' guidance so it appears once (in tool boundaries) rather than across three sections.

DimensionReasoningScore

Conciseness

Mostly lean bullet-list constraints that assume Claude's HTML/ARIA competence, with minor redundancy — 'prefer minimal/native' and the no-refactor guidance recur across 'how to use', 'tool boundaries', and 'review guidance'.

4 / 5

Actionability

Provides concrete, specific rules (exact aria attributes, patterns) plus three executable before/after HTML examples and an explicit review report format; minor gap is that most rules lack a paired example.

4 / 5

Workflow Clarity

A priority order and a three-part report format give a rough sequence, but there is no explicit step sequence or validation/re-verify checkpoint (e.g. re-check the element after applying a fix).

3 / 5

Progressive Disclosure

Well-organized into clearly headed sections with a priority table and is appropriately self-contained (no bundle files exist, none needed); not a 5 because it is a single inline ~130-line document with no one-level-deep reference split.

4 / 5

Total

15

/

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, well-structured description that clearly states capabilities and explicit usage triggers in the recommended 'what + Use when' pattern. Only minor gap is a few missing natural synonyms in trigger terms.

DimensionReasoningScore

Specificity

Names the domain and lists multiple concrete actions — 'ARIA labels, keyboard navigation, focus management, color contrast, and form errors' — giving comprehensive coverage rather than generic phrasing.

5 / 5

Completeness

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

5 / 5

Trigger Term Quality

Strong natural keywords (ARIA, keyboard navigation, focus, contrast, forms, dialogs, WCAG, accessibility) but misses common synonyms a user might say such as 'screen reader', 'alt text', 'tab order', or 'a11y'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (HTML/WCAG accessibility) with distinct triggers; minimal risk of firing 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.