Law lags new interaction forms, leaving them in a grey zone

What it is

Success criteria were written for documents and web controls before voice-only agents, and before spatial interfaces that take gesture as the only input. Law then freezes a dated edition of a standard into the statute. Accessibility law lag means new interaction forms often sit in a grey zone: does the object even count, and which clause maps. That is not an express licence to skip a channel. Grey is not a blank permit.

Why it happens

When legislation incorporates a standard, it brings a version and a commencement date. Interaction is invented faster than statutes are revised, so three mismatches appear: the object is unlisted (is this a “website” or a “service”), the means are unlisted (no success criterion for this input), the evidence is unlisted (what would count as having met the duty). The second layer is that courts and regulators fill gaps by analogy — a voice skill treated as a public-facing service, an in-app WebView still treated as a web page. Analogy is unstable; the same product can be grey in one place and white in another. Overlays and generative UIs built for defending claims did not exist when the criteria were drafted either; “the clause does not mention them” does not prove they already meet the channel duty.

Studying it

List new product forms (voice-only, head-mounted, gesture-only, realtime generated UI) against the object definitions in current statutes and the success-criterion list of the incorporated standard. Tag each as clearly covered / analogisable / no counterpart. Record whether a regulator has issued guidance on that form.

Independent variables: interaction form; object wording in the statute; year of the incorporated standard. Dependent variables: coverage tag; presence of official guidance; whether legal and accessibility teams inside the org split.

Do not take lab usability data on a new interaction as a conclusion about legal coverage; they are different questions.

Where it stops holding

Ordinary web apps, and native browsing that is informationally equivalent, usually still sit cleanly inside existing objects; do not grey yourself in order to delay a channel. Security or authentication limits can narrow an implementation; they cannot declare a whole form unregulable. A revised standard (new success criteria) does not automatically rewrite every statute that still cites an old edition; and an unrevised statute is not permission to ignore new problems. If a grey-zone product also offers the same service in a clearly obligated form (a website alongside a voice skill), that clearer side still has to pass.

Applying it

• At kickoff of a new form, write a one-page map: can current object definitions bite, which success criteria analogise, which have no counterpart. Items with no counterpart still need a functionally equivalent channel; do not wait for the statute.
• Legal and accessibility share one form list. One side may not say “grey, so skip” while the other ships the same function on a clearly covered web page.
• Treat every generative layout change as a new object that still owes name, focus, and keyboard contracts from the web, not as something that “cannot apply.”
• How to check: pick an unnamed form (voice checkout, or gesture-only browsing) and write down how a person finishes the same task without that form. No equivalent channel plus an internal memo that says “wait for the law” means rewrite the memo as an unfinished channel defect.

Related

• Same group: J1.11.1 Private-sector mandates vary sharply by industry and region · J1.11.2 Litigation and complaints are the de facto enforcement in many places · J1.11.4 Multi-region products must meet the strictest jurisdiction
• Nearby: J1.03 Ergonomics Standards · J3.05 Single Pointer Alternatives
• Search terms: accessibility law lag · grey zone interaction · standard incorporation by date