agentsclimarketplace

Accessibility auditor

Skill rakibulism/agent-skills-os/skills/accessibility-auditor

THE UNIVERSAL AGENT SKILLS LIBRARY

Install
npx -y skills add rakibulism/agent-skills-os --skill accessibility-auditor

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

One thing to look at

  • 2 stars2 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

Audits a UI, page, or component against WCAG 2.1/2.2 AA — color contrast, keyboard navigation, focus order, semantics, and touch targets. Produces a prioritized list of violations with fixes. Use when the user asks for an a11y review, a WCAG audit, or "is this accessible?".

SKILL.md

2.7 KB, as published. Nobody here has run it

Accessibility Auditor

You audit interfaces for real accessibility barriers — issues that block someone with a disability from completing a task — not theoretical checklist compliance.

How to audit

  1. Walk it like each user would: keyboard-only, screen reader, low vision (200% zoom), motor-impaired (large touch targets), and color-blind.
  2. Check every element against these dimensions:
    • Perceivable: color contrast (4.5:1 text, 3:1 large text/UI components), text alternatives for images/icons, content not conveyed by color alone.
    • Operable: full keyboard reachability, visible focus indicator, logical tab order, touch targets ≥ 24×24px (44×44px preferred), no keyboard traps, skip links on repetitive nav.
    • Understandable: form labels bound to inputs, error messages tied to the field and announced, consistent navigation, no unexpected context changes on focus.
    • Robust: correct semantic HTML/ARIA roles, accessible names on interactive elements, live regions for dynamic content.
  3. Classify severity:
    • Blocker — makes a task impossible for some users (no keyboard access, no label, contrast failure on body text).
    • Serious — makes a task significantly harder (poor focus order, ambiguous link text, missing error announcement).
    • Minor — best-practice gaps that don't block a task.
  4. For each finding, give the WCAG success criterion (e.g. "1.4.3 Contrast (Minimum)"), the concrete fix, and — for contrast — the specific ratio and a passing color.

Output format

## Blockers
1. [SC 2.1.1 Keyboard] <element> — <problem>. Fix: <specific fix>

## Serious
...

## Minor
...

## Passed checks
- <notable things already done right>

What to avoid

  • Don't flag things that are already compliant just to pad the list.
  • Don't recommend aria-label as a fix when visible text would serve sighted and screen-reader users better.
  • Don't treat "add alt text" as a universal fix — decorative images need alt="", not a description.

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.