Private-sector mandates vary sharply by industry and region

What it is

The same web shop may fall under the European Accessibility Act as an e-commerce service in the EU, and in another country may carry no dedicated private-sector duty, only a general equality clause. A bank, an ebook store, a passenger ticketing flow, and a personal blog, even in one place, are not equally likely to be named. Private-sector accessibility mandates ask whether the private actor is an obligated party this time — not the already clearer duties on government sites and procurement.

Why it happens

When legislators draw a private-sector line, they use product type, turnover, headcount, and whether the offering is public-facing, not “any website.” The EU lists e-commerce, banking, ebooks, ticketing, and similar services, with exceptions for some micro service providers. In the United States, pressure on private sites comes largely through public-accommodation theory, not a technical rule identical to the public sector. Many jurisdictions still keep mandates on public bodies and on vendors they buy from. The second layer is that lobbying and transition calendars rewrite the list into a timetable: the answer for the same private firm can reverse between 2024 and 2026. “We are private, so we need not” is false in one market and temporarily true in another — truth tracks the sector entry, not corporate ownership as such.

Studying it

Build a table of region × sector × size that records only private-sector duties: whether a dedicated statute exists, which services it lists, what the exceptions are, and the commencement date. Do not copy public-sector rules into the same column. Use official texts and regulator guidance. Do not invent damages from judgments.

Independent variables: jurisdiction, sector class, whether the actor is a micro entity. Dependent variables: whether a private mandate is enforceable; whether an exception applies; which technical baseline version the duty points to.

Testing with disabled users can reveal barriers; it cannot by itself decide whether this private firm has a legal duty in that place.

Where it stops holding

Internal tools, pure business-to-business platforms, and back offices not offered to the public often sit off the list, and can still be pulled in by customer contracts. A public body running something that “looks private” must not take a private-sector exception. Listing status and funding rounds are not the drawing rule. Absence of a duty is not absence of a user need; what is missing is the mandate, not the requirement. This card does not treat “whether compliance is the goal” — that is a different attitude question.

Applying it

• Before entering a market or a sector, check whether that place's private-sector list names a service like yours, note commencement dates and micro-entity exceptions, then decide statutory duty versus a voluntary baseline.
• File product classes in a legal memo: ecommerce checkout, content subscription, ticketing, bank onboarding may each map to a different entry. “We are an app” is not a classification.
• Keep the voluntary baseline and the statutory duty on separate ledgers, so “no mandate here yet” cannot become a feature flag.
• How to check: take a private service about to ship, list target markets, and mark each “dedicated private duty / equality law only / explicit exemption.” Exemption used to switch a channel off goes back. Duty with no test evidence goes back too.

Related

• Same group: J1.11.2 Litigation and complaints are the de facto enforcement in many places · J1.11.3 Law lags new interaction forms, leaving them in a grey zone · J1.11.4 Multi-region products must meet the strictest jurisdiction
• Nearby: J1.04 Legal Requirements · S3.06 Regional Regulatory Differences in Interface Requirements
• Search terms: private sector accessibility mandate · European Accessibility Act · ADA Title III