← ClaudeAtlas

novahiz-wcag-auditlisted

novahiz-wcag-audit runs a WCAG 2.2 Level A/AA accessibility audit across source code, live pages, and structured reports. Use when auditing web accessibility, checking WCAG compliance, fixing contrast, keyboard, ARIA, or screen-reader issues, or producing an accessibility audit report.
novahiz/novahiz · ★ 1 · AI & Automation · score 73
Install: claude install-skill novahiz/novahiz
# novahiz-wcag-audit End-to-end WCAG 2.2 A/AA audit: scan the source, check the live page, fix what fails, then produce a cited report. ## Pick a path | Input | Path | |-------|------| | Files only, no running app | Scan, Fix, Verify in code | | URL or running app | Scan, Live audit, Fix, Re-verify | | User asks for a report | Run both paths, then Report | ## Workflow **1. Scope.** Confirm the target (files, folder, URL), the claim level (AA by default), and what is out of scope. **2. Scan.** Review the source against [references/wcag22-aa.md](references/wcag22-aa.md) in this order: structure and semantics, then keyboard and focus, then forms and errors, then images, media, and ARIA, then color and contrast with `scripts/contrast.mjs`. Record each finding with SC id, severity, `file:line`, evidence, and a proposed fix. **3. Live audit** when a page is available. Playwright MCP only. Never Chrome or Chromium; the Edge profile rules apply. - Keyboard pass with Tab and Shift+Tab: focus visibility and traps. - Landmarks and heading order from the accessibility tree or snapshot. - Contrast from computed styles fed to the contrast script, plus reflow at 320 CSS px and 200% text zoom. - Optional axe-core only if the page already loads it. No heavy npm install for a one-off audit. Automated tools catch a fraction of the problems. Keyboard and screen-reader checks are mandatory before claiming AA. **4. Fix.** Prefer semantic HTML over ARIA. Work by severity: blockers first,