Image description: A wide reading-room desk in a European public-administration building, a printed tender dossier open under a desk lamp with a single red bookmark ribbon marking the accessibility clause — the quiet bureaucratic surface where procurement accessibility is decided.

Reading Time: 12 minutes

On 4 June 2026 the three European Standards Organizations — CEN, CENELEC and ETSI — released revised guidance on building accessibility into the public procurement of information and communications technology. Published as CEN/CLC/ETSI TR 101 551:2026, the technical report is aimed squarely at contracting authorities: the public bodies that write tender packages and have, since 2016, been obliged to take the accessibility needs of disabled users into account when they buy ICT products and services. If EN 301 549 answers the question “what does an accessible product have to do,” TR 101 551 answers the harder operational question that sits one step earlier — “how do we write that requirement into a tender so that the supplier who wins is actually obliged to deliver it, and so the bids can be compared fairly.”

This is the procurement-side companion to the EN 301 549 conformance question, and the timing is not accidental. The revision lands a year after the European Accessibility Act began to apply on 28 June 2025, and it signals where the regulatory pressure is heading next: away from voluntary good practice and toward contracting authorities being expected, and increasingly required, to write enforceable accessibility clauses into the documents that govern every public ICT contract. For any organisation that bids into public tenders, the document is worth pulling and reading in full. This primer explains what it is, what changed, and what it means on both sides of the tender — for the authorities writing the requirements and for the suppliers answering them.

What was published on 4 June

TR 101 551 is not new. The first edition, V1.1.1, was published in February 2014 under the title Guidelines on the use of accessibility award criteria suitable for public procurement of ICT products and services in Europe. It was one of the deliverables produced under the European Commission’s standardisation request Mandate 376 (M/376), issued in 2005 to instruct CEN, CENELEC and ETSI to harmonise accessibility in European public procurement. The 2026 revision keeps the document’s purpose but rewrites it for a regulatory landscape that did not exist in 2014: an enforceable European Accessibility Act, a maturing Web Accessibility Directive monitoring regime, and an EN 301 549 that has since gone through several versions and been adopted far beyond its original procurement scope.

A technical report (TR) is not itself a standard. It carries no presumption of conformity and creates no legal obligation by itself — that distinction belongs to the harmonised standard EN 301 549. What a TR does is explain how to apply the standard in a specific context. TR 101 551’s context is the tender: the moment a contracting authority converts the abstract requirements of EN 301 549 into the concrete language of technical specifications, award criteria and contract-performance conditions. It is, in other words, the bridge between a 200-page conformance standard and the handful of paragraphs a procurement officer actually pastes into a tender notice.

The Mandate 376 family, and where TR 101 551 sits

EN 301 549 does not stand alone. The Mandate 376 work produced a small family of deliverables that are meant to be read together, and understanding the division of labour between them is the fastest way to understand what TR 101 551 is for.

  • EN 301 549 is the harmonised standard itself: the functional accessibility requirements (clauses 5 to 13), the functional performance statements (clause 4) that describe what a user with a given disability needs to be able to do, and the test procedures for each requirement. It is written, in the Commission’s own words, “in a form suitable for use in procurement.”
  • TR 101 550 — Documents relevant to EN 301 549 — is the background and reference companion: the supporting research and rationale behind the requirements.
  • TR 101 551 — the document revised on 4 June — covers award criteria: how an authority can score accessibility quality as part of the bid evaluation, above and beyond the pass/fail minimum.
  • TR 101 552 covers conformity assessment: how an authority verifies, during and after the contract, that what was promised was actually delivered.

The practical reading is that EN 301 549 sets the bar, TR 101 551 tells you how to reward bidders who clear it by a comfortable margin, and TR 101 552 tells you how to check they kept their word. Most procurement teams reach for EN 301 549 and stop there — which is exactly why so many tenders treat accessibility as a single yes/no checkbox rather than a graded, evidence-backed requirement. The 2026 revision of TR 101 551 is an attempt to close that gap.

Technical specifications versus award criteria — the distinction that matters

European public procurement law draws a sharp line between two kinds of requirement, and accessibility lives in both. The distinction is the single most important thing in TR 101 551, so it is worth being precise.

Technical specifications are the mandatory minimum — the requirements a bid must meet to be admissible at all. Under Article 42 of the Public Procurement Directive (2014/24/EU), technical specifications for any procurement intended for use by natural persons must, except in duly justified cases, be drawn up so as to take accessibility for people with disabilities into account. In practice this means a tender should require conformance with EN 301 549 as a condition of award. A bid that does not commit to the standard fails the specification and is excluded. There is no scoring here — it is a gate.

Award criteria are different. They are how competing admissible bids are ranked to find the “most economically advantageous tender” (MEAT). Award criteria let an authority give measurable extra credit for quality that exceeds the minimum: a product tested with real assistive technology, a supplier that runs usability sessions with disabled users, a commitment to ongoing accessibility monitoring across the contract term, conformance to WCAG 2.2 AA rather than the older baseline, or a documented remediation SLA. TR 101 551 is the guidance on how to phrase, weight and evidence these criteria so they are objective, non-discriminatory, linked to the subject-matter of the contract, and capable of being scored consistently across bids. Get this wrong and an award criterion becomes legally challengeable; get it right and accessibility quality becomes a genuine competitive lever rather than a box every bidder ticks identically.

The four-stage procurement model

TR 101 551 frames accessibility as something that runs through the whole procurement lifecycle, not a clause bolted on at the end. The model the Mandate 376 toolkit established, and which the revision retains, has four stages.

One — needs analysis and market engagement. Before drafting anything, the authority establishes what accessibility the service actually requires given who will use it, and tests whether the market can supply it. A citizen-facing portal carries different obligations from an internal back-office tool. This is also where pre-tender market dialogue can flush out whether realistic suppliers exist for an ambitious requirement.

Two — technical specifications. The authority writes the mandatory accessibility requirements into the tender by reference to EN 301 549, identifying the relevant clauses for the product type. Referencing the standard rather than copying fragments of it avoids the common error of paraphrasing a normative requirement into something weaker or contradictory.

Three — award criteria. The authority decides what accessibility quality, above the minimum, it will reward, assigns weightings, and states the evidence each criterion requires. This is the stage TR 101 551 is principally about, and the stage most tenders skip.

Four — contract performance and verification. The authority sets conditions for the life of the contract — periodic re-testing, accessibility reporting, monitoring obligations, remediation timelines — and the mechanism by which delivery is verified against the promise. This is where TR 101 552 on conformity assessment takes over, and where an accessibility commitment either becomes real or quietly evaporates after signature.

What the 2026 revision changes

The most consequential change is one of framing. The 2014 edition was written for a world in which accessible procurement was strongly encouraged good practice. The 2026 edition is written for a world in which it is increasingly an enforceable expectation, because the European Accessibility Act and the Web Accessibility Directive now create downstream obligations that a public body cannot meet if its suppliers do not. A municipality whose citizen portal must comply with the Web Accessibility Directive cannot achieve that compliance if the vendor it procured the portal from was never contractually required to deliver it. The revised TR 101 551 makes this dependency explicit and pushes accessibility upstream into the tender, where it can actually be controlled.

Three substantive updates follow from that reframing. First, the guidance is re-anchored to the current EN 301 549 and to WCAG 2.2 level AA, with worked examples of award criteria that reward conformance against the present requirement set rather than the 2014 baseline. Second, it strengthens the treatment of contract-performance conditions and ongoing monitoring — recognising that accessibility regresses with every release, so a one-time conformance claim at delivery is worth little without a continuing obligation to retest. Third, it tightens the link between accessibility award criteria and the legal requirement under Directive 2014/24/EU that award criteria be objective, verifiable and connected to the subject-matter of the contract, so that authorities can use them without inviting a procurement challenge from a losing bidder.

What this means for contracting authorities

For a contracting authority running a procedure under any Member State’s national public-procurement law, the revised TR 101 551 is a direct instruction set. The headline message is that accessibility belongs in the tender documents as enforceable language, not in a non-binding annex of aspirations.

Concretely, that means three habits. Require EN 301 549 conformance as a technical specification, so that non-compliant bids are inadmissible rather than merely scored lower. Add at least one weighted accessibility award criterion with a stated evidence requirement, so that suppliers who genuinely invest in accessibility are rewarded against those who only assert it. And write a contract-performance condition that survives the signature — periodic re-testing, an accessibility point of contact, a remediation SLA — so the obligation does not lapse the moment the contract is awarded. National procurement agencies across the EU are expected to fold this guidance into their model tender templates over the coming cycles, and centralised national procurement frameworks are a natural vehicle for exactly that kind of standard clause. Authorities that adopt the language early avoid the far more expensive alternative: discovering after go-live that a procured system fails the very Web Accessibility Directive obligation the authority is itself monitored against.

What it means for bidders and suppliers

If you bid into public ICT tenders, the practical effect of the revision is that accessibility moves from a thing you might be asked about to a thing that is scored, and increasingly a thing that gates admissibility. The winning move is to be able to demonstrate, with evidence, what most competitors only assert. That is a documentation and tooling problem before it is an engineering one.

Three preparations pay off directly. First, hold a current, honest EN 301 549 conformance record for the products you offer — ideally an Accessibility Conformance Report in the VPAT/EU format, kept current rather than reconstructed under tender deadline. Second, be ready to answer award criteria with concrete evidence: assistive-technology test results, usability sessions with disabled participants, and a clear statement of WCAG 2.2 AA conformance with known exceptions named rather than hidden. Third — and this is where the contract-performance shift bites hardest — be able to commit to ongoing monitoring across the contract term, because authorities are increasingly writing that obligation into the conditions of performance rather than accepting a one-time conformance snapshot.

That ongoing-monitoring requirement is where automated accessibility platforms earn their place in a bid response. Continuous scanning catches the regressions that every release introduces and produces the periodic evidence a contract-performance condition now asks for. The serious tools in this category include Qualibooth, axe Monitor, Siteimprove and Level Access — and the right choice depends on how the monitoring output maps to the EN 301 549 and WCAG 2.2 criteria a given tender names. Automated monitoring is necessary but not sufficient: it reliably surfaces machine-detectable failures, while the manual, assistive-technology and usability testing that award criteria increasingly reward still requires human auditors. A credible bid pairs continuous monitoring with a documented manual-audit cadence, and says so in the response rather than leaving the evaluator to assume it. You can see what an automated EN 301 549 / WCAG 2.2 scan looks like on our own accessibility scanner, and the criteria themselves are catalogued in the WCAG quick reference.

A checklist for tender packages

Distilled to the operational essentials, here is what TR 101 551:2026 implies for any tender — read from either side of the table.

  • Specification gate. EN 301 549 conformance is a mandatory technical specification, not an award criterion. A bid that does not commit to it is excluded.
  • Reference, don’t paraphrase. Cite the relevant EN 301 549 clauses by reference. Paraphrasing a normative requirement weakens or distorts it.
  • At least one weighted accessibility award criterion, with an explicit, verifiable evidence requirement — test reports, AT results, usability findings — and a stated weighting.
  • WCAG 2.2 AA as the current baseline, named explicitly so older 2.1-era responses are not treated as equivalent.
  • A contract-performance condition covering periodic re-testing, monitoring and a remediation SLA, so the obligation outlives the award.
  • Conformity assessment defined up front (per TR 101 552): who verifies delivery, how, and on what cadence.
  • Bidders: an evidence pack ready before the deadline — conformance report, monitoring approach, manual-audit cadence — not assembled in the final 48 hours.

Conclusion: the tender is where accessibility is decided

The revised TR 101 551 does not change what an accessible product has to do — that is still EN 301 549’s job. What it changes is the centre of gravity. For a decade, accessibility in public ICT was something a buyer hoped for and a supplier promised, with little machinery in between to make the promise binding or to reward the suppliers who took it seriously. By rebuilding the guidance around enforceable specifications, weighted and evidenced award criteria, and contract-performance conditions that survive the signature, the 4 June revision treats the tender package as the place where digital accessibility is actually decided. For contracting authorities that is a prompt to write better tenders; for the suppliers who answer them, it is a prompt to be able to prove, not just assert, that what they ship is accessible — and to keep proving it for the life of the contract.

For the wider regulatory picture, see the EN 301 549 explainer, the European Accessibility Act guide, the EAA first-year enforcement report, and our teardown of accessibility language in a real RFP. National regimes are catalogued in the regulations index.

Primary sources

  1. CEN/CLC/ETSI TR 101 551 — Guidelines on the use of accessibility award criteria suitable for public procurement of ICT products and services in Europe (2026 revision; original V1.1.1, February 2014). etsi.org/standards
  2. ETSI EN 301 549 — Accessibility requirements for ICT products and services (V3.2.1, 2021). etsi.org/deliver/etsi_en/301549
  3. CEN/CLC/ETSI TR 101 550 — Documents relevant to EN 301 549; and TR 101 552 — guidance on conformity assessment for accessibility in public procurement.
  4. European Commission. Standardisation Mandate M/376 to CEN, CENELEC and ETSI in support of European accessibility requirements for public procurement of products and services in the ICT domain (2005).
  5. Directive 2014/24/EU of the European Parliament and of the Council on public procurement, particularly Article 42 (technical specifications) and Articles 67–69 (award criteria). eur-lex.europa.eu/eli/dir/2014/24/oj
  6. Directive (EU) 2019/882 — European Accessibility Act, applicable from 28 June 2025. eur-lex.europa.eu/eli/dir/2019/882/oj
  7. Directive (EU) 2016/2102 — Web Accessibility Directive (accessibility of public-sector websites and mobile applications). eur-lex.europa.eu/eli/dir/2016/2102/oj
  8. CEN, CENELEC and ETSI. Accessible ICT Procurement Toolkit (Mandate 376 deliverable), and national transpositions of Directive 2014/24/EU into Member-State public-procurement law.