Access and Authority

Why Accessibility Proves the Missing Session Layer

Regulators have written rules that attach obligation to the live experience of a participant with a disability. Widely deployed architectures do not appear to produce that proof. Deadlines slip, settlements fail, and litigation moves upstream because the same condition is described from each vantage: no layer owns the interaction at the moment access is required.

The Failure Signal

On April 20, 2026, four days before the long-scheduled compliance date, the Department of Justice published an Interim Final Rule (91 Fed. Reg. 20902) extending ADA Title II web accessibility deadlines. Entities serving fifty thousand or more had been required to bring web content and mobile applications into conformance with WCAG 2.1 Level AA by April 24, 2026. The new deadline is April 26, 2027. Smaller jurisdictions move from April 26, 2027 to April 26, 2028.

The rule did not change. The standard did not change. The obligation did not change. The federal government conceded, four days before the date, that the institutions subject to the rule were not ready. Two years of notice, fifteen years of preceding rulemaking, a published technical standard, and the systems still could not deliver. The DOJ stated that it had overestimated technological readiness and institutional capacity.

Compliance, as the rule actually requires it, attaches to the live experience of a participant with a disability interacting with the system. The architecture deployed across most institutions cannot prove that experience. On May 7, 2026, four days before its own first compliance date, the Department of Health and Human Services issued a parallel Interim Final Rule under Section 504 of the Rehabilitation Act extending its web and mobile application accessibility deadlines by one year. The May 11, 2026 deadline for recipients with fifteen or more employees moved to May 11, 2027; the May 10, 2027 deadline for smaller recipients moved to May 10, 2028. Two parallel federal rulemakings, on independent statutory footings, conceded the same architectural readiness gap within seventeen days.

The Temporary Equilibrium

No widely deployed architecture appears capable of proving deterministic interaction-level compliance at scale. Not in California. Not in the European Union. Not under HHS Section 504. Not under DOJ Title II. Components pass audits. Features ship. Accessibility statements get posted. Provable access during the live interaction is not what any deployed architecture currently produces.

Federal regulators face difficulty enforcing a standard that widely deployed architectures do not appear ready to meet. The DOJ extension is the legible public form of that constraint. Civil plaintiffs cannot recover at the volume the damages structures permit unless the architectures change, and the affirmative-defense bills moving through state legislatures are the legible form of it from the other side. When either statement stops being true, the equilibrium ends. The same condition, viewed from outside accessibility, is the subject of the Compliance Boundary.

Availability Is Not Access

The first mistake is thinking accessibility means adding something. Captions. A transcript. A screen reader label. A signing window. A larger font. An AI summary. Each may be necessary. None of them is the architecture. The architecture is what decides when the accommodation is required, who is entitled to receive it, whether it is available, how it is delivered, what happens when the session changes, and how the system proves the participant received access comparable to everyone else. Most systems have features. They do not have accessibility authority.

A caption toggle does not answer the harder questions. Did the participant need captions? Did they receive them continuously? Did they persist through reconnect, handoff, escalation, device change, or breakout? Were they available without forcing disability disclosure? Were they logged as an accommodation rather than a broadcast attribute? The platform can say captions exist. The law increasingly asks whether access existed.

A second failure happens alongside it. Everyone can turn on captions, summaries, translation, signing avatars, visual description, sentiment analysis, agentic note-taking. The accommodation becomes indistinguishable from preference. An accommodation is not a preference. It is an entitlement attached to a participant in a live interaction, sometimes legally required, medically necessary, or a condition of employment, healthcare access, or public service access. Convenience can fail gracefully. Access cannot.

What Access Actually Requires

Deaf and hard-of-hearing access makes the issue legible. A platform cannot send every interpreter feed, every avatar, every translation, and every fallback to every endpoint as a universal broadcast. Availability cannot mean transmission. The law may push toward universal availability. Physics forbids universal broadcast. The only workable structure is selective delivery under session authority: the system determines entitlement, selects the best modality the moment can support, routes the stream only where it belongs, preserves it through the session's mutations, tears it down when no longer needed, and proves what happened.

Blind and low-vision access exposes the deeper layer. A blind participant does not only need words spoken aloud. They may need to know who joined, who is speaking, who shared a screen, what slide is visible, what chart changed, what poll opened, whether the host changed permissions. That is not content. That is the live state of the interaction. A static accessibility layer cannot govern that.

What the European Union Already Enforces

The European Union has been operating under a more demanding regime since June 28, 2025. The European Accessibility Act, Directive (EU) 2019/882, became applicable across all twenty-seven member states on that date. It does not stop at public-sector websites. It reaches e-commerce platforms, banking services, transport ticketing, telecommunications terminals, e-books, audiovisual media, ATMs, point-of-sale terminals, and consumer computing hardware. The technical standard, EN 301 549, incorporates WCAG 2.1 Level AA and adds product and service requirements that go well beyond it. A United States company that accepts an order from a customer in Lyon or Lisbon falls under EAA jurisdiction.

The EAA is the architecturally important regime because it is cross-domain. A vendor can pass a website audit and still fail an EAA review, because the obligation reaches the experience across components: booking flow, payment terminal, consumer device, audiovisual stream, customer service channel. Component compliance is not service compliance.

Litigation Is Moving Upstream

The California Unruh Civil Rights Act provides what the federal ADA does not: a private right of action with statutory damages of four thousand dollars per violation, plus attorney's fees, with treble damages where intent can be shown. That structure is the engine of the country's largest concentration of accessibility litigation. Assembly Bill 2190, currently moving through the 2025-2026 session, would create an affirmative defense to those claims if a business can show, within the bill's defined response window after a pre-lawsuit demand, either a published digital accessibility report disclosing the specific barrier and updating it with remediation, or regular automated and manual testing in good faith. The defense is conditioned on actual evidence of behavior, not on the existence of a policy document.

The architectural point is what the bill assumes about evidence. AB 2190 takes for granted that the relevant proof is dynamic and ongoing: monitoring frequency, remediation timelines, third-party component governance, public disclosure that updates as conditions change. That is the compliance posture the regulators want and the architectures cannot supply. The bill also reaches resource service providers. In its predecessor (AB 1757) and the current draft, the legislature is moving liability upstream toward the developers, vendors, and component providers whose products are embedded in the noncompliant experience. The component layer is in scope. The integration layer is in scope. The session in which access either occurred or did not is in scope.

The Fashion Nova Irony

On February 2, 2026, the DOJ filed a Statement of Interest in a federal court in Oakland opposing a proposed five point one five million dollar class settlement of a website accessibility case against Fashion Nova. The objection was not that the settlement was too small. It was that the settlement website itself was allegedly inaccessible to the class members it was supposed to compensate.

A system designed to remedy an accessibility failure reproduced the failure on the remediation surface. Not because anyone intended the irony. Because the architecture used to build the remediation site was the same architecture that produced the original violation: feature compliance without interaction governance, component testing without session evidence, a static accessibility statement standing in for live, provable access. That pattern is the deeper reason the deadlines slipped.

The Agent Problem Makes Everyone Special

Accessibility is the first visible case of this architecture problem. Agents are about to make it universal. A ten-person meeting with two agents per participant is no longer one meeting. It is one interaction spawning twenty auxiliary participants, twenty derivative records, twenty memory surfaces, twenty action trails, twenty separate authority questions. Who captured the session? For whom? Stored where? Under whose policy? Retained how long? Shared with whom? Allowed to act downstream? Subject to privilege, accommodation rules, or medical, educational, or employment record obligations? A recording banner does not answer any of this. The system has moved beyond recording into producing derivative state, and the derivative state outlives the call.

Once every participant can bring an agent, every participant can create a private fork of the interaction. Some forks are accommodations. Some are surveillance. Some are memory. Some are authority-bearing action that affects downstream systems. The platform cannot govern that by pretending the meeting ended when the call ended.

The Proof Case

The old compliance question was simple. Does the product support accessibility? The new question is harder. Did the live interaction provide effective access to the participant who needed it, using the best available accommodation, while preserving authority, privacy, continuity, and proof? That question cannot be answered by a feature list, a VPAT, or a post-hoc log. It has to be answered during execution, by something that knew at the time of the decision what was admissible. The burden is shifting from documentation of controls to proof of behavior.

The missing layer is not another caption engine, interpreter marketplace, summary tool, or audit dashboard. It is the authority that binds accommodation, auxiliary computation, participant entitlement, and derivative artifacts to the live interaction itself. That authority must sit outside the application feature and outside the transport path. The transport carries the signal. The application exposes the function. The session governs whether the function is admissible for this participant, in this context, under this policy, at this moment. The same separation between transport continuity and authority continuity described in Signal and Authority applies here.

Accessibility is not the edge case. It is the proof case. It shows what happens when a live interaction has to deliver different experiences to different participants under different obligations without breaking the common session. Accessibility does not ask whether a system has features. It asks whether a person could participate. Participation is no longer a property of the interface. It is a property of the session.