NTARI Accessibility Standards

The web's accessibility standards exist because of one old promise: the render belongs to the person reading, not the person writing. This course teaches you the promise's modern machinery, then hands you the promise itself. First, accessibility as working engineers practice it: WCAG 2.2 and ARIA, the laws that cite them, and axe-core — the open-source engine inside Lighthouse and the industry's audits — from a console one-liner to a CI gate that fails builds. You will also learn NTARI's own operational definitions: Policy P2-002's floor of WCAG AA, screen reader compatibility, and transcripts, widened by its seven-language broadcast portfolio and mobile-first, bandwidth-sensitive delivery; and Policy P2-003's five distribution layers and Continental Mirror Network — accessibility across language, device, geography, and time. Every clause names a barrier between a person and use. Then the turn: automation catches at most half the problem, and conformance leaves users petitioning authors for every fix. NTARI's Janus Facing Architecture answers with presentation sovereignty — styling ships as user-editable data, and every participant holds the right to restyle their own render. Since the August 2026 rebuild that guarantee sits in the official document itself, in the Economy & Information layer's frontend tier: frontend designs must be customizeable by the user. You will design and build that right's recommended pattern: an in-app CSS/HTML editor, sanitized at import, meeting the five build requirements — no scripts, no beacons, an unoccludable reset, plain exportable artifacts, honest shipped themes — with the default theme and the editor itself holding the WCAG 2.2 AA floor, verified by the same axe-core you started with. And you will meet a live edge of the corpus: those five requirements carry archived identifiers that bind nothing in the current invariant registry, so conformance to them is self-attested by construction. Week 10 offers you the chance to draft the amendment that would fix it. 10 weeks, one section per week. You leave with a shipped, tested, AGPL-licensed editor, a hostile-theme corpus, a conformance self-check, and a living open-questions document — real work in the commons, not homework. Three posts weekly: one on the material, two to your cohort.