ultra11ylisted

# 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 active coding agent** *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". **Do not confuse rules with criteria.** The bundle ships 93 static checks, WCAG AA has 55 success criteria, and RGAA has 106 criteria. Several rules may evidence one criterion, one rule may contribute to several pack criteria, and most criteria remain open until a scan or an adjudication. The only honest run-level coverage is the grid's live provenance tally (`moteur + scan + agent`, plus any named undecidable residue), never a fixed promise such as “48 agent criteria”. GitHub summaries