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.

1.06x

Quality

—

Does it follow best practices?

Impact

99%

1.06x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

100%

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

A tight, instruction-only accessibility checklist that is token-efficient, concrete, and well-structured with executable before/after examples. The review workflow is unambiguous and content is appropriately self-contained.

Dimension	Reasoning	Score
Conciseness	Lean bullet-list rules with no padding or explanation of concepts Claude already knows; every line states a constraint. Matches the lean-and-efficient anchor.	3 / 3
Actionability	Concrete directives ("icon-only buttons must have aria-label", "do not use tabindex greater than 0", "modals must trap focus") plus copy-paste before/after HTML in "common fixes". Fully actionable.	3 / 3
Workflow Clarity	Single-purpose review skill with an unambiguous flow: review against rules, report violations (quote/why/fix), fix critical issues first (priority table). No destructive/batch ops requiring validation feedback loops, so the simple-skill exception applies.	3 / 3
Progressive Disclosure	Well-organized into a priority table, nine categorized rule sections, common fixes, and review guidance; no nested references and no monolithic wall. No external bundle files exist or are needed for a focused checklist.	3 / 3
	Total	12 / 12 Passed

Description

100%

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 concise, third-person description that names concrete capabilities and provides explicit use-when triggers, hitting all four dimensions. Voice is imperative/third person with no first- or second-person slip.

Dimension	Reasoning	Score
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 multiple-specific-actions anchor.	3 / 3
Completeness	Answers both what (audit/fix the listed a11y issues) and when ("Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance") with an explicit trigger clause.	3 / 3
Trigger Term Quality	Natural terms a developer would say are well covered: "interactive controls, forms, dialogs", "WCAG compliance", "ARIA labels", "keyboard navigation"; not merely technical jargon.	3 / 3
Distinctiveness Conflict Risk	Clear niche (HTML accessibility) with distinct, narrow triggers; unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ibelick/ui-skills
Commit: 6dbd684

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.