Accessibility is usually legally constrained while usability is not, which changes how each is driven

What it is

The two live in different organizational positions: accessibility carries legal obligations in most jurisdictions (public services, procurement, accessibility clauses for marketed products) with legal and tender consequences for violations; usability is rarely legislated and runs on quality standards, market competition, and professional norms. The obligation status sets the advocacy mode: accessibility can be driven top-down from compliance; usability must be argued bottom-up from value.

Why it happens

A legal line changes the decision structure: with a clear compliance threshold, accessibility work gains "must-do" status, a stable budget line, an accountable owner, and an external basis for audits and acceptance; usability has no such hard line, so its investment competes with every other product value and must keep proving itself in commercial language—conversion, retention. Each mode has strengths and weaknesses: compliance secures the floor but tends to stop at "over the line" (see the checklist limits), while value-driven work can pursue the ceiling without guarantees. Mature organizations treat the compliance line as accessibility's floor, not its target, and use value arguments to support both.

Studying it

Studying the two modes is organization and policy research: compare accessibility levels before and after regulation takes effect (regulatory effect evaluation), and differences in deep usability—real task performance by disabled users—between compliance-driven and value-driven organizations. The practical implication is an evidence structure that is measurable and auditable: accessibility work naturally leaves conformance documents and audit trails, and usability work should borrow that discipline (versioned measurement records) to strengthen its standing inside the organization.

Where it stops holding

The legal landscape shifts by jurisdiction and sector: not every product falls in scope, statutes often cite standards (such as WCAG levels) and lag behind them, and usability occasionally does enter law (operating procedures in safety-critical domains). Reading "there is a law" as "following the standard is immunity" is wrong—compliance audits examine the evidence chain, and criteria-level compliance with real-world unusability can still lose a case. And no hard law for usability does not mean no norms: industry standards and procurement requirements frequently carry usability clauses.

Applying it

• Map the regulations and procurement requirements that apply to the product, run accessibility compliance status as a standing dashboard with named owners.
• Set voluntary targets above the legal line (internal standards exceeding statutory levels) so "just over the line" never becomes the quality ceiling.
• Let usability borrow compliance's evidence discipline: versioned measurement archives and acceptance records, so value arguments have paper trails.

Related

• Same group: B5.13.1 Accessibility addresses a wider range of abilities; usability addresses achievement for a specified user group · B5.13.2 Passing accessibility checks is not the same as being usable by disabled users · B5.13.3 Improvements made for extreme ability conditions usually raise usability for ordinary users too
• Nearby: J1 Accessibility and Inclusion · R2 Design Systems and Engineering Delivery
• Search terms: accessibility legislation · compliance · procurement requirements