AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Accessibility Auditor

skill-sourav15mukherjee-skillforge-free-skills-accessibility-auditor · by sourav15mukherjee

>-

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

Install

$ agentstack add skill-sourav15mukherjee-skillforge-free-skills-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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-sourav15mukherjee-skillforge-free-skills-accessibility-auditor)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
5mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
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

Scan web application source code for WCAG 2.1 accessibility violations and produce a prioritized remediation report.

Workflow

  1. Discover UI components and templates

Find all files containing HTML, JSX, TSX, Vue, Svelte: ``bash find . -maxdepth 5 \( -name "*.tsx" -o -name "*.jsx" -o -name "*.vue" -o -name "*.svelte" -o -name "*.html" \) -not -path "*/node_modules/*" -not -path "*/.next/*" | head -100 `` Prioritize: layouts, navigation, forms, interactive widgets, media components.

  1. Check images and media (WCAG 1.1.1)
  • ` without alt` — Critical
  • Icon-only buttons without accessible labels — Critical
  • SVG without role="img" and aria-labelMajor
  • `/` without captions — Major
  1. Check semantic HTML (WCAG 1.3.1)
  • ` instead of ` — Critical
  • Missing landmark elements (`, , `)
  • Heading levels that skip (h1 → h3)
  • Inputs without associated ``
  1. Check ARIA usage (WCAG 4.1.2)
  • Interactive elements without accessible names
  • aria-hidden="true" on focusable elements — Critical
  • Missing roles on custom widgets (tabs, dialogs, accordions)
  • Missing state attributes (aria-expanded, aria-selected)
  1. Check keyboard navigation (WCAG 2.1.1)
  • Custom controls without tabIndex
  • Missing onKeyDown handlers on custom interactive elements
  • outline: none without replacement focus style
  • Keyboard traps in modals
  1. Check focus management (WCAG 2.4.3)
  • Modals without focus trapping
  • Missing skip navigation link
  • Route changes without focus management
  1. Check color contrast (WCAG 1.4.3)
  • Low-contrast text/background combinations
  • Information conveyed by color alone
  • Common Tailwind pitfalls: text-gray-400 on bg-white = 2.7:1 (fails AA)
  1. Check forms (WCAG 3.3.1)
  • Inputs without labels
  • Placeholder as only label — Major
  • Error messages not linked via aria-describedby
  1. Generate the audit report by severity:

Critical — Blocks assistive technology access Major — Significant barriers Minor — Improvement opportunities

Each finding: file:line, WCAG criterion, current code, fixed code, who is affected.

Rules

  • Always reference specific WCAG 2.1 success criteria by number
  • Provide before/after code snippets for every finding
  • Distinguish decorative images (alt="" is correct) from informative ones
  • Check both JSX and CSS files
  • Prioritize critical issues over minor improvements
  • Note which user groups are affected per finding

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.