Public services and public procurement are where mandates usually attach

What it is

A city is buying a booking system. The tender states that an accessibility conformance statement is required, citing a band inside a harmonised standard. A personal blog or an internal demo page is usually not stopped at this step. Public services and public procurement are the hooks a mandate most often hangs from: either you are a public body providing a service, or you are selling into a public body. Once the hook is on, missing evidence keeps you out of the contract. It is not “we will talk after launch.”

“Public” is wider than a .gov host. Health booking, public-transport ticketing, and utility accounts are treated in many instruments as public or public-interest services as well.

Why it happens

Public money and public functions were the first places thought worth legislating: a service paid for by taxpayers that shuts some people out is politically indefensible, and procurement language is a gate that already exists. The gate works as evidence before contract — statement, test scope, cited standard written into the tender; no delivery, no shortlist. A vendor who is not itself a public body still hits the gate once it enters that chain.

The second layer is the extension of “public service.” Instruments often follow function, not domain name: school admissions, health appointments, travel tickets, identity and benefits. Passenger transport and e-commerce on the EU list also treat services offered continuously to the public as an extension of a public-facing duty, not as “ministry websites only.” Mandates “usually” hang here because this is where a budget gate and a statutory function exist — not because every other actor is forever left unwritten.

Studying it

Read tenders and public-function lists, not judgments. Pull one public buyer’s tender or an EN 301 549 / GOV.UK statement template; copy the mandatory clause, the level asked, the form of evidence asked. Then list the function categories that jurisdiction writes down as public services or public-sector websites.

Independent variables: whether the buyer is a public body, whether the service is listed as a public or public-interest service, whether a procurement procedure is in play. Dependent variables: whether a mandatory clause appears, whether the next round is reachable without a statement, what evidence form is named.

The table answers “does this deal have a gate,” not what patches the gate if it fails. Writing “public procurement is mandatory” as “only government websites have an accessibility duty” shrinks the hook wrongly.

Where it stops holding

Not every internal tool of every public body sits under the same gate — purely internal admin systems, pilots not yet public, may be written separately. International organisations, military, and intelligence often have their own regimes; civilian public-service clauses do not paste onto them. Developer tools and back offices for civil servants can still sit under the gate if they were bought in the same procurement package, even when the end user is not a resident. Transition periods and orders under a small-value threshold may be procedurally excused; that is a procurement-law threshold, not accessibility principle cancelled.

Applying it

• When the buyer is public or the service is listed as a public function, copy the tender’s accessibility clause and cited standard into the project charter, and assemble evidence in the buyer’s template.
• Treat a commercial product sold to a public buyer as a procurement-chain problem: the brand may be private; the deliverable still needs a conformance statement and a test scope.
• A pass on the marketing site does not cover the mobile app and the counter-top terminal bought in the same package; keep evidence per form.
• How to check: open the tender or contract annex and find the page of the accessibility clause; then check that the deliverable holds the statement and test date the clause named. No clause but a claim of “government procurement already covered,” or a clause but only a marketing screenshot, means the gate was not taken seriously.

Related

• Same group: J1.04.1 Who and what a law covers changes with the jurisdiction · J1.04.3 Compliance is the legal floor, not the product goal
• Nearby: J1.02 Conformance levels · J1.12 Accessibility statements and conformance documentation · J1.03 Ergonomics standards
• Search terms: public procurement · EN 301 549 · Section 508