ultra11ylisted

Use to AUDIT existing HTML/CSS/JSX against WCAG 2.2 AA accessibility and produce a dated auditor-conformance report, OR to AUTHOR/REVIEW accessible markup (native-HTML-first, ARIA last). An install-free engine (`node scripts/ultra11y.mjs`, no keys) runs 72 static checks tied to WCAG criteria — alt/lang/title, unlabeled fields, empty links/buttons, tables, headings, ARIA vocabulary, label-in-name, autocomplete — measured against the official W3C ACT corpus. The engine decides 3 of the 55 criteria; the AI agent adjudicates the 38 judgment ones from harvested evidence + a per-criterion decision protocol (`verify --manual`, gated, fannable via `orchestrate`), and the 14 rendering ones go to `scan` — never silently conforming. Library/SFC code is audited as RENDERED captures (`render --setup`); country standards are pluggable packs (`--standard rgaa`, `scan --sample`). check/verify reject invented non-conformities. Triggers: 'audit WCAG/a11y', 'make accessible', 'fix a11y', 'audit RGAA'.
maxgfr/ultra11y · ★ 1 · Code & Development · score 77

Install: claude install-skill maxgfr/ultra11y

# ultra11y — audit WCAG 2.2 AA and write accessible markup On accessibility, an automated tool only sees part of the problem. `ultra11y` owns that with a **division of labour**: the deterministic, install-free engine (`node scripts/ultra11y.mjs <command>` — no `npm install`, no key; the JSX/TSX parser is embedded in the bundle) does the *mechanical* work — detect the machine-checkable non-conformities and tie each to the right **WCAG success criterion** — and **the AI agent** (Claude running this skill) *adjudicates the judgment criteria itself* — alt relevance, link purpose in context, reading order — statically, from the evidence the engine harvests (`verify --manual`), each verdict gated by `verify`/`check`. Only the truly **rendered-DOM** criteria (computed contrast, visible focus, zoom/reflow, content-on-hover) fall to the `scan` tier (axe-core in a real browser); a human is at most optional oversight. Gates stop any hallucinated non-conformity from surviving, and nothing is ever silently "conforming". **WCAG 2.2 Level AA is the worldwide core.** Country standards — France's **RGAA**, the US **Section 508**, the EU **EN 301 549** — are pluggable *standards packs* that map their criteria onto WCAG. Add `--standard rgaa` to re-key reports/criteria; **plug an external pack at runtime** with `--pack ./pack.json` (or a `.ultra11yrc.json`), no rebuild; or contribute your country (see `references/standards.md`). Packs (and their concrete **implementation guidance** — the RGAA