Accessibility baseline and beyond
An agent interface that ships recognized accessibility-standard compliance plus conversational-accessibility affordances: adjustable pace, plain language by default, pause/resume, and a reviewable transcript.
When a government service is reached through an AI agent, the agent's own interface becomes the thing a citizen has to be able to use, and if it is not accessible the agent is just a new barrier in front of the service. Web-accessibility standards cover the visual and interaction layer, but a back-and-forth conversation adds a cognitive dimension, pace, plain language, the ability to pause and review, that no current standard covers.
The challenge is to hold agents to the established accessibility floor and extend it to how they converse.
Government needs every citizen to be able to use the agent interface itself, not only the service behind it, before it can rely on agent-mediated delivery. Meeting that requires the recognized web-accessibility floor for the interface components and a parallel commitment on how the agent converses, covering pace, plain language, the ability to pause and review, and a transcript the citizen can check.
Citizens with cognitive or processing differences, low literacy, or limited working memory can clear a technically conformant interface and still be unable to follow a conversation that moves too fast, assumes domain knowledge, or vanishes as it scrolls, and they are excluded from a consequential action they cannot track. The keep-open response is interactions that are reviewable rather than ephemeral, paced to the citizen, and plain by default, so neither the interface nor the cognitive load shuts anyone out.
The agent interface gives the citizen direct control over the conversation: a pace control, plain language by default, pause and resume, and a persistent transcript they can review.
No surface has been built yet; the approach above is the brief for one.
- Established Headline
WCAG conformance for web services is a recognized, mandated floor.
- Frontier
Conversational accessibility standards specific to agent interactions have no established precedent.
WCAG 2.1 AA as legal baseline. The US DOJ's ADA Title II Final Rule requires state and local government entities to ensure web content and mobile applications conform to WCAG 2.1 Level AA. A DOJ interim final rule (April 2026) extended the compliance deadlines to 26 April 2027 for larger public entities (population 50,000 or more) and 26 April 2028 for smaller entities and special districts. Section 508 of the Rehabilitation Act requires the same for federal agencies and contractors. Australia's Digital Service Standard incorporates WCAG compliance. These are cumulative: Level AA requires meeting all Level A and Level AA success criteria.
WCAG compliance is necessary but not sufficient for agent-mediated services. WCAG addresses the interface layer (screen readers, color contrast, keyboard navigation) but not the cognitive accessibility of agent interactions. An agent conversation that meets WCAG technically may still be cognitively inaccessible if it uses complex language, assumes domain knowledge, or moves too fast.
The pattern needs extension to cover conversational accessibility: agents must support adjustable pace, plain language by default, the ability to pause and resume, and explicit confirmation before consequential actions, and interactions must be reviewable rather than ephemeral. The recognized web-accessibility standards do not yet cover how an agent converses, so this part of the floor has to be defined rather than adopted.
The failure mode is a person swept through an inaccessible automated flow they cannot follow or check. Requiring reviewable, plain-language, pace-adjustable interactions ensures they can actually follow and verify a consequential action.