← ClaudeAtlas

a11ylisted

Use when asked to audit, fix, or test web accessibility against WCAG 2.2 AA. Builds a matrix of states and viewports, runs axe-core, and requires evidence per row. Do not use for generic Lighthouse checks.
ChloeVPin/chloe-skills · ★ 0 · AI & Automation · score 71
Install: claude install-skill ChloeVPin/chloe-skills
# A11y Purpose: make web content accessible. Minimum target: WCAG 2.2 Level AA. ## Definitions - **Scope**: the exact pages, journeys, and states you will test. - **Matrix row**: one combination of route, state, viewport, and input mode. - **Evidence**: a recorded result that another person can reproduce. ## Workflow checklist Copy this checklist and track your progress: ``` Audit Progress: - [ ] 1. Choose the mode - [ ] 2. Establish the boundary - [ ] 3. Build the matrix - [ ] 4. Capture the baseline - [ ] 5. Triage findings - [ ] 6. Remediate (remediate mode only) - [ ] 7. Verify (remediate mode only) - [ ] 8. Report ``` ## 1. Choose the mode Two modes exist. Choose one before any other step. - **Audit mode**: inspect and report only. Do not change product source code. - **Remediate mode**: inspect, fix, add regression coverage, and re-verify. Audit mode executes steps 1, 2, 3, 4, 5, and 8. Remediate mode executes steps 1 through 8. ## 2. Establish the boundary Record, in writing, all of the following: 1. Mode: audit or remediate. 2. Target surfaces: changed feature, selected routes, or representative sample. 3. User tasks: the essential actions users must complete. 4. Support baseline: browsers, assistive technology, and versions. 5. Data constraints: authentication, test accounts, and fixtures. 6. Evidence location: where results will be stored. If the scope is ambiguous, choose a narrower scope. A narrow scope produces a true claim. A broad scope produces a