Proactive AI Governance: WCAG 2.2 for AI-native (A2UI) Design Systems

For regulated industries like fintech a post-build checklist, a scan, a report that tells you what already went out the door is not an option. That reactive WCAG 2.2 model doesn’t survive agent-composed interfaces as a retroactive implementation layer. Additionally, conformance is defined for the page or the process as well, because a component can be correct by itself and still fail in composition.

When an AI agent assembles a surface at runtime from a Lit component catalogue, you can’t audit your way to accessibility. The first place to enforce it, and the most leveraged one, is the boundary where a component is admitted to the Lit catalogue.

I made the accessibility contract a condition of a component being approved into the Lit catalogue, reported in the preview, and enforced at approval.

The four declarations. Every component must declare four things: its role, its label, its keyboard behavior, and its screen-reader announcement.

The standard: The gate validates every WCAG criterion identifier against standards/wcag-2.2.jsonld—a machine-readable, JSON-LD representation of WCAG 2.2 Success Criteria, structured with @context, @id, and @type so the validator reads criteria from the file rather than from a model’s memory.

What designers still own: The component library and its tokens, the layout primitives, the allowed nesting, the frame and the slots. The approved page patterns, the content strategy and the page-level semantics: headings, landmarks, reading order, and focus order.

The ingest reports. The designer ingests a Figma component into the design system. The drawing and the measured facts are unchanged. Beside them, the preview shows which declarations are present, which are missing, and where each present value came from. The ingest never refuses to draw and never changes the design. It reports so that the designer can adjust their designs to comply.

The contract travels. Once complete, the contract is stored with the catalogue entry, including WCAG 2.2 criterion identifiers and verification modes. Every composition the agent produces is checked against it.

The contract is built around the failure modes agents actually produce: placeholder-only labeling, a container pretending to be a button, hallucinated alt text, visual-only structure, color-only state, and suppressed focus. The four declarations, the WCAG identifier check, and the required properties are enforced at runtime.

An audit tells you what shipped. A gate decides what may be shipped, then designers are empowered to make adjustments instantly.

We want to create foundational architectures that prevent heavy layers of governance.

The New Success Criteria (9 added)

WCAG 2.2 adds nine criteria. Six of these are at Levels A or AA, meaning they are required for typical legal compliance . These are the ones most relevant to a design system gate.

Focus & Keyboard:

  • 2.4.11 Focus Not Obscured (Minimum) (AA): When an element receives keyboard focus, it cannot be entirely hidden by author-created content like sticky headers or cookie banners .

  • 2.4.12 Focus Not Obscured (Enhanced) (AAA): The stricter version; no part of the focused component can be hidden .

  • 2.4.13 Focus Appearance (AAA): Sets a minimum size and contrast requirement (3:1) for the focus indicator .

Pointer & Touch:

  • 2.5.7 Dragging Movements (AA): Any function that uses dragging must have a single-pointer alternative (e.g., click-to-move instead of drag) .

  • 2.5.8 Target Size (Minimum) (AA): Interactive targets must be at least 24 by 24 CSS pixels, with specific exceptions for spacing, inline text, or essential presentation .

Forms & Cognition:

  • 3.2.6 Consistent Help (A): If a help mechanism (chat, contact link, FAQ) repeats across pages, it must appear in the same relative order each time .

  • 3.3.7 Redundant Entry (A): Information the user already entered in a process must be auto-populated or available to select, rather than forcing re-entry .

  • 3.3.8 Accessible Authentication (Minimum) (AA): Login processes cannot require a cognitive function test (like remembering a password or transcribing a code) unless an alternative (password manager support, copy-paste, passkeys, object recognition) is provided .

  • 3.3.9 Accessible Authentication (Enhanced) (AAA): Removes the object-recognition and personal-content exceptions .