CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a lean, well-structured rulebook with attribute-level specificity and useful before/after fix patterns, and it clearly bounds its own scope. Weaknesses are mild: some duplication between the When to Use section, priority table, and quick-reference headers, placeholder-based code snippets, and no post-fix verification step.

DimensionReasoningScore

Conciseness

The rule categories are terse checklist bullets that assume Claude's competence (e.g., "do not use tabindex greater than 0", "modals must trap focus while open"), with only minor trimmable redundancy: the "When to Use" section repeats the description verbatim, a stray "Fix accessibility issues." line, and the priority table overlaps the quick-reference headers. This fits anchor 4 better than 3 because the padding is minor relative to the whole body.

4 / 5

Actionability

Gives concrete, attribute-level rules (aria-label, aria-describedby, aria-invalid, aria-expanded, aria-controls, prefers-reduced-motion) plus before/after HTML snippets for three common cases. Anchor 4 rather than 5 because the snippets use "..." placeholders (e.g., "<svg aria-hidden=\"true\">...</svg>") making them patterns rather than copy-paste-ready code.

4 / 5

Workflow Clarity

The review workflow is unambiguous: quote the exact snippet, state the failure, propose a small fix, and "fix critical issues first (names, keyboard, focus, tool boundaries)", with scope bounded ("Do not rewrite large parts of the UI"). Anchor 4 rather than 5 because there is no verification step after applying fixes; the destructive-operation cap does not apply since the skill mandates minimal, non-destructive changes.

4 / 5

Progressive Disclosure

A single-file skill with well-organized sections (priority table, nine rule categories, common fixes, review guidance) and no buried or nested references; content is appropriately inline for its size. Anchor 4 rather than 5 because at ~140 lines the detailed rule catalog could be split into a one-level-deep reference file, and the under-50-line simple-skill exception does not apply.

4 / 5

Total

16

/

20

Passed

Description

87%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 clearly states both capability and usage triggers with domain-specific keywords. The only weakness is that the action verbs are generic (audit/fix) while specificity is carried by the enumerated sub-areas, and a few common synonyms (a11y, screen reader, alt text) are absent.

DimensionReasoningScore

Specificity

"Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors" names the domain plus five specific sub-areas, matching the anchor for several specific actions with minor gaps. It falls short of anchor 5 because the action verbs themselves (audit, fix) are generic, unlike the multiple distinct concrete verbs in the 5 example.

4 / 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, matching the anchor-5 example pattern. It is not anchor 4 since the 'when' clause is already explicit and specific.

5 / 5

Trigger Term Quality

Includes natural phrases users would say such as "ARIA labels", "keyboard navigation", "color contrast", "dialogs", and "WCAG compliance" — good keyword coverage. Not anchor 5 because common variations like "a11y", "screen reader", and "alt text" are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (HTML accessibility / WCAG auditing and fixing) with distinct triggers like ARIA, keyboard navigation, and focus management, so conflict risk with other skills is minimal — matching anchor 5.

5 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

sickn33/agentic-awesome-skills

Path

plugins/aasb-aas-accessibility-inclusive-ux/skills/fixing-accessibility/SKILL.md

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.