agentsclimarketplace

Accessibility audit

Skill rafa-js/product-designer/skills/accessibility-audit

Audit a design or implementation for WCAG / a11y issues. Use when the user asks for an accessibility check, a11y audit, WCAG review, or contrast/keyboard/screen-reader verification. Returns specific failures with WCAG references and concrete fixes.From its SKILL.md

Install
npx -y skills add rafa-js/product-designer --skill accessibility-audit

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

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 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.

SKILL.md

3.6 KB, as published. Nobody here has run it

Accessibility Audit

Find a11y failures with enough specificity that an engineer can fix them.

Inputs to confirm

  • Artifact: design file, screenshot, deployed URL, or component spec.
  • WCAG level target: usually 2.1 AA. Ask if uncertain.
  • Surface: web, iOS, Android, desktop — assistive-tech expectations differ.
  • Scope: a single component, a flow, or the whole product.

If a URL is provided and you have browser/inspect capability, prefer testing live. Otherwise audit the artifact.

Method

Walk these checks in order. Stop and report when you find concrete issues — don't aggregate to the point of vagueness.

1. Color & contrast

  • Body text contrast ≥ 4.5:1; large text (≥18pt or 14pt bold) ≥ 3:1; non-text UI (borders, icons) ≥ 3:1.
  • State is never carried by color alone — pair with icon, label, or shape.
  • Verify in grayscale mentally; if hierarchy collapses, color is doing too much.

2. Typography

  • Body text ≥ 16 px on web (or scaled equivalent on native).
  • Line length 45–75 chars.
  • No long bodies in italics, all-caps, or ultra-thin weights.

3. Targets and spacing

  • Tap targets ≥ 44×44 pt (web/iOS) or 48×48 dp (Android Material).
  • Targets don't overlap or sit ≤ 8 px apart.

4. Keyboard

  • Every interactive element reachable via Tab in a logical order.
  • Focus indicator is visible (≥ 2 px outline, contrasting both states).
  • Esc closes modals/menus; Enter/Space activate.
  • No "click-only" patterns (drag-only, hover-only).

5. Screen reader

  • Every input has a programmatic label (<label>, aria-label, aria-labelledby).
  • Every meaningful image has alt text; decorative images use alt="".
  • Icon-only buttons have an accessible name.
  • Modal traps focus and restores it on close.
  • Live regions (aria-live polite/assertive) used for toasts/banners.
  • Headings form a meaningful outline (no skipped levels for styling).

6. Motion & timing

  • prefers-reduced-motion respected — no parallax / large transitions when disabled.
  • No autoplay video with sound.
  • No timeouts under 20 seconds without a way to extend.

7. Forms specifically

  • Label + helper + error all programmatically associated.
  • Inline validation; error identifies the problem and the fix.
  • Required state is in text or icon, not color alone.

8. Content

  • Plain language; grade-8 reading level for general audiences.
  • Error messages: identify the problem + suggest a fix.
  • Don't shout (no body text in ALL CAPS).

References: references/04-ux-foundations/accessibility.md, references/02-theory-and-principles/inclusive-design.md.

Output

## Failures
| # | Severity | WCAG SC | Issue | Where | Fix |
|---|----------|---------|-------|-------|-----|

## Recommendations beyond WCAG
- (inclusive-design improvements that aren't strictly failures)

## What I couldn't check
- (anything that needs live testing, real users, or a screen reader)

Severity — critical (blocks use for affected users) · serious (substantial barrier) · moderate (workaround exists) · minor.

Cite WCAG success criterion (e.g., 1.4.3 Contrast (Minimum)) for each failure when applicable.

When to escalate

If the design fails ≥ 3 critical items, recommend redesigning rather than patching — accessibility usually compounds with hierarchy.

Keep looking

Skills are one crate of 608,475. 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.