← ClaudeAtlas

review-a11ylisted

Use to REVIEW code changes for accessibility — '/review-a11y', 'review my changes/PR/branch for a11y', 'accessibility review of this diff'. Scopes to exactly the code under change (staged files, working diff, or branch vs merge-base), runs the bundled install-free ultra11y engine (node scripts/ultra11y.mjs, no keys; static WCAG 2.2 AA checks tied to success criteria, cross-file JSX/TSX via --graph), then adds YOUR judgment: refute false positives (SFC/library-source findings are preliminary), decide alt relevance and link purpose, name the rendering criteria (contrast, focus, zoom) as residual risks — never invent a non-conformity. Output: a severity-ranked review (blocking → major → minor) with file:line, concrete fixes, residual risks and a one-line verdict, in the conversation's language (technical tokens stay in English). Companion of the ultra11y skill (full audits, reports, PRD, RGAA packs). Triggers: 'review a11y', 'a11y review', 'accessibility review'.
maxgfr/ultra11y · ★ 1 · Code & Development · score 77
Install: claude install-skill maxgfr/ultra11y
# review-a11y — accessibility review of changed code The review counterpart of the `ultra11y` skill: where `ultra11y` produces full audits and compliance deliverables, **this skill reviews exactly the code under change** — a diff, a branch, a PR — and reports like a code reviewer. Same division of labour: the deterministic, install-free engine bundled with this skill does the *mechanical* work (machine-checkable WCAG 2.2 AA non-conformities, each tied to a success criterion, cited `file:line`), and **the AI agent** *adjudicates the judgment* — refute false positives, decide alt relevance/link purpose/focus logic statically from the code, and route what needs a rendered DOM to `scan`. A human is at most optional oversight. **Engine resolution:** every command below is `node scripts/ultra11y.mjs …` where `scripts/ultra11y.mjs` lives **next to this SKILL.md** (the engine ships inside the skill; no install, no key). Run it with the reviewed project as the working directory. In the ultra11y repository itself, the repo root's `scripts/ultra11y.mjs` is the same file. > **Core rules** (shared with `ultra11y`): > 1. **Never invent a non-conformity**: report only what the engine found or what you can > see and cite in the code under review. > 2. **Review the change, not the world**: findings outside the reviewed scope are noted in > one line at most ("pre-existing, out of scope"), never mixed into the verdict. > 3. **Residual is explicit, never silently conforming**: the *rend