← ClaudeAtlas

508-auditlisted

Run a full Section 508 + WCAG 2.2 Level AA accessibility audit on a federal / .gov / public-sector website or ICT product. Triggers: "Section 508", "508 audit", "WCAG", "VPAT", "ACR".
tinh2/skills-hub-registry · ★ 15 · AI & Automation · score 76
Install: claude install-skill tinh2/skills-hub-registry
# Section 508 + WCAG 2.2 Accessibility Audit You run a federal-grade accessibility audit and produce the deliverable trio agencies require (VPAT 2.5 + ACR + remediation plan). Federal procurement is increasingly contingent on these — failure to provide credible 508 documentation eliminates vendors from competition. **Standards landscape (2026)**: - **Section 508 (Revised 2017)**: binding for federal procurement. Incorporates **WCAG 2.0 AA** technical criteria. - **WCAG 2.2 AA** (W3C, October 2023): adds 9 new success criteria (focus appearance, dragging movements, target size, etc.). Many agencies test against 2.2 even though 508 floor is still 2.0. Testing higher is fine. - **ADA Title II** (April 2024 final rule): public entities (state, local governments) must conform to WCAG 2.1 AA by April 2026 (large entities) or 2027 (small). - **Section 504** (federal grantees): similar requirements via funding agreements. ============================================================ === PRE-FLIGHT === ============================================================ Verify: - [ ] **Site URL** + scope (pages to audit). Federal audit baseline: every "key" template + ≥ 25 sampled pages. - [ ] **Site rendering**: static HTML / SSR / CSR? Pure CSR can't be audited by lightweight tools without rendering. - [ ] **Stack**: identify frontend framework + UI library (React + MUI, Vue + Vuetify, etc.). Different defaults. - [ ] **Documentation deliverable target**: VPAT 2.5 Rev 508, VPAT 2.5 Int