AgentStack
SKILL verified MIT Self-run

Accessibility Audit Websites

skill-thegoat395-codex-skills-accessibility-audit-websites · by TheGoat395

Audit website accessibility. Use for semantic structure, headings, alt text, forms, focus states, keyboard navigation, color contrast, labels, ARIA misuse, reduced motion, captions, skip links, modals, menus, carousels, and final frontend QA aligned with WCAG-style accessibility expectations.

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

Install

$ agentstack add skill-thegoat395-codex-skills-accessibility-audit-websites

✓ 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 Audit Websites? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Accessibility Audit Websites

Use this skill to make sites usable for more people and prevent polished visuals from hiding broken interaction.

Workflow

  1. Inspect the project, scripts, routes, local/deployed URL, production surfaces, and available QA/deployment tooling.
  2. Read [Accessibility Audit Websites Guide](references/accessibility-audit-websites-guide.md) before claiming the site is ready.
  3. Run the narrowest meaningful checks for the risk: visual, mobile, accessibility, performance, forms, media, SEO, analytics, deployment, or handoff.
  4. Fix issues when they are in scope; otherwise record exact evidence and remaining risk.
  5. Summarize commands, URLs, screenshots/checks, changed files, and what was not tested.

Always Protect

  • Inspect before changing or shipping: framework, package scripts, build output, routes, forms, media, animation stack, deployment target, environment variables, analytics, SEO metadata, accessibility risks, and available browser QA tooling.
  • Do not claim something was tested unless it was actually tested; report exact commands, URLs, screenshots, viewports, failures, skipped checks, and remaining risk.
  • Verify desktop and mobile rendered output, not only source code. For visual or motion work, inspect screenshots, browser behavior, console errors, network failures, and responsive layout.
  • Treat forms, checkout, booking, CMS content, analytics, environment variables, and deployments as production surfaces with error, loading, empty, success, and rollback states.
  • Respect accessibility, performance, reduced-motion, and no-JavaScript/no-WebGL/no-autoplay fallbacks where relevant.
  • Keep secrets out of code, logs, screenshots, summaries, widgets, and committed files.
  • Prefer project-local tooling and existing scripts before adding dependencies. Explain any new dependency before installing it.
  • End with a concise handoff: changed files, commands run, checks passed, checks not run, deployment URL if any, and next risks.

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.