S3.06.4Accessibility law applicability matrixdesignresearch

Accessibility laws differ in scope

Aliases: accessibility law applicability · compliance scope matrix · accessibility jurisdiction · regulatory scope

What it is

An accessibility law applicability matrix determines whether a legal duty covers a particular entity role, product or service, population, channel, content class, and release date, then links the result to a technical standard, exception, transition, and evidence. The mechanisms of accessible design do not change by jurisdiction, but enforceable coverage, referenced baseline, deadline, and proof can. Supporting a locale does not by itself make one statute applicable, and an exemption in one instrument does not mean users no longer need accessible access.

Why it happens

Laws draw boundaries around public and private entities, sectors, size, procurement relationships, product classes, and digital channels, and incorporate technical standards in different ways. The European Accessibility Act covers enumerated products and services from 28 June 2025 with provisions including microenterprise service exemptions and transitions. The US ADA Title II web and mobile rule covers state and local governments, references a particular WCAG version, and phases compliance dates by entity conditions. Neither model substitutes for the other or extends to every organization. Delivery must separate the applicability decision from the product accessibility baseline: the former governs legal evidence and deadlines, while the latter remains a quality requirement rather than switching off when one rule is out of scope.

Studying it

Inventory legal entities, operating roles, target markets, products and services, supply chain, procurement contracts, sites, apps, documents, third-party content, and release dates. Accessibility counsel then records source, coverage, referenced standard, exception, transition, and enforcement path for each combination. Technical audits retain standard and version, scope, tools, manual procedures, known defects, and remediation evidence, linked to the applicable rule version. Scenarios cover legacy and new content, third-party integrations, substantial updates, entity changes after acquisition, and cross-border release. Research with disabled people reveals actual barriers but does not independently determine legal applicability; a legal conclusion likewise cannot replace validation of effective access with disabled users.

Where it stops holding

A technical standard such as WCAG and the law or contract incorporating it are different layers. A standards update does not automatically amend every law, while an older legal reference is not a reason to ignore newly understood barriers. Exceptions, fundamental alteration, disproportionate burden, and alternatives commonly have constrained tests and are not product-team checkboxes. Litigation, administrative enforcement, procurement, and sector regulation also differ. For unknown scope, the safe fallback is not to claim exemption: continue the organization's approved stronger accessibility baseline, retain feedback and human assistance, and escalate legal uncertainty to the accountable owner.

Applying it

  • Version an applicability matrix keyed by jurisdiction + entity role/size + product/service + sector + channel/content + contract + effective date. Link official text, legal interpretation, technical-standard version, deadline, exception criteria, owner, and review date.
  • Manage the product accessibility baseline separately from legal minima. Use an approved strong common baseline for multi-region release, adding jurisdiction-specific evidence, reporting, and timing work without disabling accessibility by locale.
  • Attach rule ID and standard version to requirements, designs, code, third-party procurement, test reports, defects, and accessibility statements. Generate an impact manifest for rule updates and reassess legacy content, vendors, and transition items.
  • When rules are absent or conflict, continue the strong baseline and block unreviewed compliance claims while providing an accessible feedback channel and human alternative. Have legal and accessibility specialists review sources regularly, and validate that alternatives work in tasks with disabled users.

Related

  • Same group: S3.06.1 Mandatory consent and notice requirements vary by region · S3.06.2 Age thresholds for minors are not uniform · S3.06.3 Price and tax disclosure can be legally mandated
  • Adjacent: J1.11.1 Whether private entities are legally covered varies greatly by industry and region · J1.11.4 Multi-region products need to meet the strictest applicable jurisdiction
  • Search terms: European Accessibility Act · ADA Title II web rule · accessibility applicability

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/S3.06.4