WCAG 2.2 Connector for AI agents.

A has no native keyboard interactivity, no focusability, and no implicit ARIA role. Adding `onclick` creates a visual button that keyboard and screen reader users cannot operate. Native elements provide focus, Enter/Space activation, and the 'button' role automatically. no extra JavaScript required.

A focus trap constrains Tab navigation inside a specific element. typically a modal, dialog, or dropdown. so users cannot navigate to the underlying page while the overlay is active. WCAG 2.4.3 (Focus Order) requires it for all modal dialogs. Without it, a keyboard user can Tab behind the modal into invisible content.

Yes. The contrastCompliant pivot validates foreground/background color combinations across five states: default, hover, focus, active, and disabled. A button that passes contrast in its default state but fails on hover (e.g., light gray text on white) is flagged as CONTRAST_FAILING.

axe-core and Lighthouse scan rendered HTML in a browser. they detect violations after the code is built and running. Accessibility Prover validates UI specifications before code is written. It reasons about component behavior, keyboard flows, and interaction states at the design level, catching architectural issues that post-build scanners cannot see because they only inspect the final DOM.

Yes. that is a primary use case. AI coding agents default to div-based layouts because divs are syntactically simpler. Accessibility Prover acts as a guardrail: the agent submits its component specification, the prover validates it against 5 pivots, and the agent receives a structured verdict with specific fixes before writing code.

Since June 2025, the EAA requires all digital products and services sold in the EU to meet accessibility standards equivalent to WCAG 2.1 AA (with WCAG 2.2 AA as the recommended benchmark). Non-compliance carries fines up to 5% of annual revenue and potential market withdrawal. Accessibility Prover helps demonstrate compliance as a build-time gate, creating an auditable validation record.

Submit each component as structured text covering 5 dimensions: (1) Layout. the HTML elements and hierarchy, (2) Keyboard. tab order, focus indicators, focus traps, (3) Contrast. foreground and background hex values with computed ratio, (4) Screen Reader. alt texts, aria-labels, form-label associations, (5) Motion. animation properties and prefers-reduced-motion handling. The capability reasons about each dimension independently.

The capability validates against WCAG 2.2 AA, which is the legally required level under the EAA 2025 and the practical target for most products. AAA requirements (e.g., 7:1 contrast ratio, sign language interpretation) are not enforced. they are aspirational goals that few products achieve fully.