Compliance is the legal floor, not the product goal

What it is

Counsel says last year’s band already passed, and accessibility disappears from the roadmap. Booking still fails: cognitive load, language, a gesture the instrument had not named. Legal compliance is the floor legislation could write and measure at the time: meet it, and you are not on the unlawful side of the line. It is not the goal of including people in the product. Building code keeps the stair from collapsing. It does not make anyone want to live there.

Treating the legal checklist as design-done systematically drops barriers the list never named — not because those people matter less, but because the legislative cycle had not written that far.

Why it happens

Law encodes a lagging political consensus. What can enter a statute is usually what already has a stable test and a harmonised standard to cite. Cognitive load, the quality of plain language, interaction forms not yet named, often still sit outside that consensus. “Lawful” then means “the set the instrument named was met.” Failures outside the set can be legally absent and still present on the task.

The second layer is the direction of incentive. Once an organisation takes compliance as the goal, it optimises the shape of evidence (statement, sample, date), not who still cannot finish the critical path. After the floor is treated as the finish, the next budget only maintains that evidence. It will not touch problems the instrument did not ask for. This sits next to “meeting a technical standard can still be unusable” without being the same cut: that cut compares technical criteria with task success; this one compares a legal duty with a product ambition. A product can be lawful and unusable, or usable and still treat lawful as a ceiling — the second is the floor mistaken for a target.

Studying it

On a product that already holds compliance evidence, open a separate off-list barrier register: reports from disabled users, cognitive walkthroughs, critical-path failures the instrument never named. Code each failure as “actually inside a cited criterion, missed in testing” or “the criterion set never covered it.”

Independent variables: presence of a compliance statement, whether the failure falls inside cited criteria. Dependent variables: count of off-list failures, share that block task completion, whether any accessibility item remains on the roadmap after the compliance pass.

The material is user reports and task observation, set against the statute’s cited set — not another checker score. Do not write “the floor is not enough” as “enforcement is soft here.” That is an enforcement mechanism, not the meaning of the floor.

Where it stops holding

In tightly regulated domains whose instruments already write most of the critical path (some public-benefits journeys), the gap between floor and goal is thinner; a separate task-success gate is still worth having, the increment is just smaller. On new forms the instrument has not covered, the floor may be close to blank; stopping at “the law did not write it, so we will not” maximises exclusion. If a contract writes a higher clause as a delivery condition, the contract is the goal for that deal; the law remains the lower line. Treating compliance as a floor does not dismiss compliance — without the floor, even that set need not be done.

Applying it

• After the compliance list is green, keep a column on the roadmap for off-list barriers, fed by disabled users’ reports and critical-path observation, not by counsel’s ticks.
• Split repairs: a cited criterion that was missed belongs to compliance maintenance; a failure the criteria never covered belongs to the product goal. Do not send the second kind back to counsel as “we are already lawful.”
• The public statement may name the band that is lawful; the internal goal names task completion and who is still shut out. Do not merge the two lines.
• How to check: lay the current compliance evidence beside the last three months of barrier reports, and list items that still exist and sit outside cited criteria. If the roadmap holds zero corresponding items and the reports do not, the floor was treated as the end.

Related

• Same group: J1.04.1 Who and what a law covers changes with the jurisdiction · J1.04.2 Public services and public procurement are where mandates usually attach
• Nearby: J1.03 Ergonomics standards · J1.09 Cost and timing of accessibility · J1.12 Accessibility statements and conformance documentation
• Search terms: compliance floor · legal minimum · beyond conformance