agentsclimarketplace

Accessibility review

Skill shinzoxD/knackbox/skills/coding/accessibility-review

Curated, auditable, benchmark-ready Agent Skills library for Claude Code, Codex, OpenCode, Cursor, and more.

Install
npx -y skills add shinzoxD/knackbox --skill accessibility-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Review UI and content for accessibility issues against WCAG-minded practices. Use whenever the user asks for an a11y review, accessibility audit, ARIA help, keyboard navigation, screen reader support, or whether a UI is accessible — even for small component snippets.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.2 KB, as published. Nobody here has run it

Accessibility Review

Accessibility is usability under more constraints. Prefer semantic HTML and native controls before ARIA. Findings should be actionable and severity-tagged.

Review order

  1. [critical] Keyboard traps, missing names on controls, contrast failures on primary UI, content only as color.
  2. [serious] Focus order wrong, incomplete labels, modal focus not managed, skip link missing on large pages.
  3. [moderate] Heading hierarchy skips, redundant ARIA, target size.
  4. [minor] Text alternatives that could be clearer, non-blocking polish.

Checklist

  • Semantics: headings, lists, landmarks, buttons vs links, form labels.
  • Keyboard: tab order, Enter/Space, Escape for dialogs, no keyboard trap.
  • Name/role/value: accessible names, expanded/pressed states.
  • Visual: contrast, focus visibility, zoom to 200% without loss of action.
  • Media: captions/transcripts when media is in scope.
  • Motion: respect reduced motion when animations are significant.

Output format

## A11y review: <surface>

### Findings
1. [critical] … — impact — fix

### What looks good
- …

### Test plan
Keyboard path, screen reader smoke, automated scan suggestions.

Rules

  1. Prefer native elements over ARIA reimplementation.
  2. Do not invent WCAG clause numbers if unsure; describe the user impact.
  3. Screenshots alone are incomplete — ask for HTML/structure when needed.
  4. Separate product bugs from a11y defects only when both matter.
  5. Offer concrete markup fixes, not only "add ARIA".

Edge cases

  • Design-only mock: review labels, contrast assumptions, focus order as guidance.
  • Complex widgets: require keyboard map and state announcements.
  • Charts: text summary or data table alternative.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.