AgentStack
SKILL verified MIT Self-run

Accessibility Auditor

skill-rakibulism-agent-skills-os-accessibility-auditor · by rakibulism

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?".

No reviews yet
0 installs
6 views
0.0% view→install

Install

$ agentstack add skill-rakibulism-agent-skills-os-accessibility-auditor

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Accessibility Auditor? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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.
  1. 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.
  1. 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]  — . Fix: 

## Serious
...

## Minor
...

## Passed checks
- 

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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.