← ClaudeAtlas

web-accessibility-auditlisted

Audits one or more live web pages for accessibility issues and produces a prioritized, cited, fixable markdown report. Use this whenever the user shares a URL (or several) and asks for an accessibility check, audit, review, or compliance check — including phrasing like "is this site accessible", "check for a11y issues", "WCAG compliance", "ADA compliance", "screen reader friendly", "accessibility score", or "what's wrong with this page for accessibility". Also use when the user wants to compare accessibility across a few pages, wants to know if a redesign made accessibility better or worse, or needs a client-facing accessibility deliverable — even if they never say the word "audit."
rongiladco/web-accessibility-audit · ★ 0 · Web & Frontend · score 62
Install: claude install-skill rongiladco/web-accessibility-audit
# Web Accessibility Audit Turns a list of page URLs into a markdown accessibility report: what's wrong, which WCAG success criterion it violates, why it matters for a real user, and a concrete fix. This is a prompt-only skill — there's no deployed code, everything below runs inside this Claude Code session. ## 0. Before anything else — ask what you don't know A few things are almost never safe to assume, so confirm them at the start of every run rather than picking a default silently. Ask these as **separate questions**, not bundled into one — version and conformance level are two independent axes, and folding them together makes it easy to misread an answer to one as an answer to both: 1. **WCAG version**, on its own — 2.0, 2.1, or 2.2. If there's no strong preference, you can mention that 2.1 is still the most widely referenced in contracts and regulations today, with 2.2 being newer and adding a handful of criteria — but let the user choose, don't assume it. 2. **Conformance level**, as a separate question — A, AA, or AAA. If asked for a default, AA is the most common target (it's what ADA/EN 301 549 and most contracts reference) — but still ask rather than picking it silently. 3. **The exact list of URLs.** Audit precisely the URLs given — don't crawl the site or follow internal links to find more pages on your own initiative. If more pages should be covered, ask for more links rather than guessing which ones matter. (If crawling would genuinely help for a given reque