Image description: An EU public-sector procurement officer’s desk showing a printed EN 301 549 standard document with coloured tab-bookmarks, an EU flag pin beside it — the visual marker for the procurement-officer profile.

Reading Time: 10 minutes

”M.” is a composite. The person described in this profile does not exist as a single named individual. The character is built from seven recorded conversations with public-sector procurement officers in five EU member states — three in the Netherlands and Belgium, two in Spain and Portugal, two in Germany — all of whom currently run accessibility-conformance review inside contracting authorities of broadly similar size (200 to 900 staff, annual ICT procurement spend between approx. 8 and approx. 40 million euro). Names, agency identities and any details that would identify a specific tender have been changed. Where direct quotations appear, they are verbatim from one of the seven interviews, attributed to “M.” rather than to the original speaker. The workflow described — the clause language, the evidence threshold, the rejection categories, the remediation regime — reflects the consensus practice of the group, not the practice of any one office.

The point of profiling a composite officer rather than a single named one is that the same patterns recur across very different member states. None of the seven officers we spoke to had received central training in how to enforce EN 301 549 when they took up their role. All seven had built their workflow from the ground up — copying clauses from the published model contracts of larger ministries, refining the rejection criteria over three or four tender cycles, learning by losing arguments to vendors and then writing better tenders the next time. M. is what that learning curve produces. This piece is what M.’s desk looks like in May 2026, four years after the European Accessibility Act entered force and seven years into the maturity of the Web Accessibility Directive.

The route in — how a procurement officer becomes an accessibility enforcer

M. did not start out as an accessibility specialist. The route in was sideways. M. trained as a public-administration generalist, joined a member-state ministry’s procurement office in the late 2010s as a contract administrator, and inherited the accessibility file in 2021 because the colleague who had been handling it left for the private sector and the desk had to go to somebody. At the time the file consisted of a folder of unsigned policy memos and a single previous tender in which an “accessibility clause” had been pasted in from a template the colleague had downloaded from a German ministry’s open-procurement portal. The clause referenced “the relevant European standard” without naming EN 301 549 and demanded “conformance with WCAG 2.0 Level AA” — a version of WCAG that had been superseded for seven years.

The first thing M. did, in early 2022, was rewrite the clause. The rewritten version named EN 301 549 V3.2.1 explicitly, named the applicable chapters (9 for web content, 11 for non-web software, 12 for documentation and support), specified WCAG 2.1 Level AA via the EN’s Chapter 9 reference, and required the vendor to submit a conformance report at tender stage rather than after award. That clause has been refined four more times since then — once after a vendor argued the standard did not bind them because their product was “primarily a back-office tool”, once after a different vendor submitted a self-certification report consisting of two pages of marketing copy, once after the EAA’s transposition act in the relevant member state added explicit penalty references, and once in late 2025 in anticipation of EN 301 549 V4.0.0’s incorporation of WCAG 2.2 AA.

”The mistake I made in the first tender was treating accessibility as a checkbox. The vendor put a tick in the box. We did not ask them to show working. The second tender, I changed one sentence. I said: a tick is not evidence. From that day everything changed.”

M., procurement officer, EU member-state contracting authority

The tender language — what M.’s standard clause looks like in 2026

M.’s standard accessibility clause is now four paragraphs long and runs to about 380 words inside the tender’s technical-requirements section. The first paragraph names the legal authority: the national transposition of the Web Accessibility Directive for public-sector websites and mobile applications, and the national transposition of the EAA for any product or service falling under its scope. The second paragraph names the technical standard — EN 301 549 V3.2.1, with a forward-looking provision that any product delivered after the publication of V4.0.0 in the Official Journal must be re-evaluated against the new version at the supplier’s expense within twelve months. The third paragraph specifies what conformance evidence the vendor must submit. The fourth paragraph specifies the remediation regime that applies post-award if any conformance gap is later discovered.

The third paragraph is the operative one. It demands what M. and the other officers we spoke to call the “European ACR” — an Accessibility Conformance Report following the structure of the US VPAT template but referencing the EN 301 549 clause set rather than Section 508. ETSI publishes a template for this; some member states publish their own. M.’s tender requires the ACR to (a) name each applicable clause of EN 301 549 by number, (b) state for each clause whether the product Supports, Partially Supports, Does Not Support or Not Applicable, (c) provide a one-paragraph remark for every clause whose status is anything other than “Supports”, and (d) attach the underlying audit report on which the ACR is based.

The last sub-clause is the one that does the work. A blank ACR with “Supports” entries across the board can be produced by any vendor in under an hour. An underlying audit report cannot. M.’s tender explicitly requires that the audit be a third-party audit by a body listed in the relevant national accreditation register, or — where the contract value is below the threshold at which third-party audit is proportionate — that the audit be performed by an in-house team whose evaluators hold a recognised qualification (in M.’s practice, IAAP CPACC or WAS) and whose audit methodology is documented and reproducible. Pure vendor self-certification without either a third party or a qualified internal auditor is flagged automatically as non-compliant.

The evidence threshold — what counts and what gets flagged

The single biggest change M. made between 2022 and 2026 was tightening the evidence threshold. In 2022, M. would accept any ACR submitted on the vendor’s letterhead, provided the format matched the ETSI template. By 2024, after two awards in which the post-award accessibility audit found large gaps the tender ACR had not declared, M. had switched to a sliding scale: third-party audit accepted at face value; in-house audit accepted subject to spot-check; vendor self-certification accepted only if accompanied by a signed declaration that the underlying methodology can be produced on demand and that the signing officer is personally accountable for its accuracy under the contract’s misrepresentation clause.

In practice, the spot-check is the lever. M. now spot-checks approx. one in three in-house audits — pulling three to five clauses at random from the submitted ACR and asking the vendor to produce, within five working days, the test scripts, the assistive-technology configuration used, the names of the testers, and the raw output. Vendors who can produce these in five days pass. Vendors who cannot, or who produce them in a form that contradicts the ACR’s claimed status, are rejected.

There are now four named patterns that get a tender flagged in M.’s office. The first is “WCAG 2.0 leakage” — clauses citing WCAG 2.0 instead of 2.1, usually a sign of an old template that has not been refreshed. The second is “Supports without remark” — every clause marked Supports with no explanatory remark anywhere, which the spot-check almost always punctures. The third is “Section 508 substitution” — a vendor submitting a US VPAT against Section 508 in place of an EN 301 549 ACR, which is non-responsive on its face but still common from US-headquartered suppliers. The fourth is “Out-of-scope claim” — a vendor stating that EN 301 549 does not apply because the product is back-office software, or B2B, or used only by internal staff. In the public-sector context M. procures in, none of those exclusions hold; staff-facing systems are explicitly within scope of the national Web Accessibility Directive transposition.

”I do not reject a tender for honest gaps. I reject a tender for dishonest paperwork. A vendor who says ‘Partially Supports’ and explains why is having a conversation with me. A vendor who says ‘Supports’ on every line is hoping I do not read it.”

M., procurement officer, EU member-state contracting authority

Rejections and remediation — the argument that splits the profession

The biggest argument inside the profession in 2026 is not whether to require EN 301 549 in tenders — that is settled — but what to do when a tender’s ACR reveals gaps. There are two camps. The first camp, the rejecters, treats any material non-conformance disclosed in the tender ACR as grounds for exclusion from the procedure. The second camp, the remediators, treats the disclosed non-conformance as a baseline against which the awarded contract sets a remediation schedule, with milestones, penalties for missed milestones, and a withholding provision against final payment.

M. has moved across the line twice. In 2022 and 2023 M. rejected. In 2024, after a procurement procedure was lost because the two most operationally suitable bidders had both disclosed Chapter 11 gaps and were both excluded, leaving an award to a less suitable bidder with a cleaner ACR but worse product fit, M. shifted to remediation. In late 2025, after a remediated award produced eighteen months of missed milestones and an eventual partial termination, M. shifted partway back. The current practice in M.’s office is to reject on conformance grounds only when the disclosed gap is in a Chapter 9 (web) clause that is fundamental to the user task — keyboard operability, focus visibility, programmatic name — and to remediate when the gap is in a Chapter 11 software clause that has a credible technical path to fix.

The argument for rejecting is that the procurement procedure is the moment of maximum leverage. Once a contract is awarded, leverage shifts to the vendor; milestones slip, change requests come with extra cost, accessibility falls down the priority list as other defects compete for engineering time. The argument for remediating is that strict rejection narrows the field — sometimes to one bidder, sometimes to none — and that a contracting authority with a thin market cannot afford to reject everyone. Both arguments are right under different conditions. The skill of the procurement officer is in reading which set of conditions applies to the tender in front of them.

The post-award clauses — what makes remediation actually work

When M. remediates, the contract carries four specific clauses. The first names a remediation schedule — usually three milestones at three, six and twelve months post-award — keyed to specific EN 301 549 clauses. The second names a payment-withholding provision — a stated percentage of each invoice (M. uses approx. 15 percent) held back until the milestone for the period is signed off. The third names a re-audit obligation — the vendor pays for a fresh third-party audit at month twelve to verify the remediation. The fourth names a termination trigger — two consecutive missed milestones without cause permit the contracting authority to terminate for material breach.

M.’s observation is that the payment-withholding provision does almost all the work. Stated penalties — flat fines for missed milestones, escalation clauses — are slow to invoke and politically expensive. A withheld invoice line is mechanical. The vendor’s finance team applies pressure to the engineering team on the next working day. The remediation gets done.

What smaller agencies should copy

Most of M.’s practice is not specific to large contracting authorities. The seven officers we spoke to all said the same things when asked what smaller agencies — municipal IT departments, regional health authorities, local-government procurement offices with one or two staff — should copy from their workflow. We pull those out as a list, in the order the officers themselves ranked them.

  • Name the standard by number and version. Do not write “the relevant European accessibility standard”. Write “EN 301 549 V3.2.1, with V4.0.0 to apply on publication in the Official Journal”. A named standard is enforceable; an unnamed one is rhetorical.
  • Demand the ACR at tender stage, not at award. The ACR is your filter. If you cannot see it before you award, you cannot exclude on it.
  • Demand the underlying audit, not just the ACR. The ACR is a summary; the audit is the evidence. Refuse self-certified ACRs with no audit attachment.
  • Spot-check one in three in-house audits. Even if you do not have time to spot-check everything, randomised spot-checking changes vendor behaviour across the entire bidder pool.
  • Reject on Chapter 9 fundamentals; remediate on Chapter 11 gaps. Keyboard, focus, programmatic name are non-negotiable. Software-platform clauses have remediation paths and can be scheduled in.
  • Use payment withholding, not flat fines. Withhold approx. 15 percent per invoice against the next milestone. Pay it out only when the milestone is signed off. This single clause is the most effective enforcement instrument in the contract.
  • Re-audit at month twelve at the vendor’s cost. A second audit, done by a different third party from the one that produced the tender ACR, is the only way to know whether the remediation actually closed the gap.
  • Refuse Section 508 substitution. A US VPAT against Section 508 is not an EN 301 549 ACR. Send it back and ask for the European document.
  • Copy clauses from larger ministries. Every EU member state has a ministry that publishes its model accessibility clauses. Start there. Do not draft from scratch.
  • Document your rejections. Build a one-page memo for every tender you reject on accessibility grounds. After three or four memos you have an institutional position that the next vendor’s lawyers cannot argue around.

The desk at the end of the day

M.’s desk, when we visited the composite version of it on a Thursday afternoon in early May, had a printed copy of EN 301 549 V3.2.1 with coloured tabs along the right edge — green for clauses M. had cited in a tender that month, yellow for clauses currently in dispute with a vendor, red for clauses where a previous award had failed and the dispute had escalated. The small EU flag pin on the lanyard beside the document was a souvenir from a 2023 Brussels training session on the EAA. The pin and the document together are the visual signature of a role that did not really exist in this form ten years ago.

M. ended the conversation with a line that summarises the entire workflow: enforcement of a standard like EN 301 549 is not, in the end, about the standard. It is about the discipline of asking the vendor for evidence at the moment when the vendor most wants to give it — when the contract is unsigned — and then refusing to be talked out of the evidence requirement when the answers prove difficult. The standard exists. The contracting authority’s job is to make the standard cost something when it is ignored.