EAA WCAG evidence and procurement acceptance

EN 301 549 connects WCAG testing with wider European ICT accessibility procurement. V3.2.1 applies to ICT products and services, including web pages, mobile applications, desktop software, hardware, and combinations of hardware and software, and supports the Web Accessibility Directive. ETSI now publishes EN 301 549 V4.1.1 (2026-09). Publication of an edition does not by itself establish an EAA presumption of conformity; verify the relevant Official Journal citation and the requirements it covers. Procurement records must identify which edition and clauses the contract requires.

A WCAG report can support accessibility acceptance for web content, documents, and software interfaces, but it does not by itself prove EU Accessibility Act conformity. Record which EN 301 549 clauses were tested, which clauses were not applicable, which non-WCAG requirements also matter, and whether an EAA harmonised-standard reference published in the Official Journal covers the requirement at issue.

Procurement acceptance criteria should be written as contract tests, not marketing promises. For each deliverable, name the exact service, user journey, platform, software build, document set, hardware model, and assistive technology environment covered by the evidence. Then state the EN 301 549 clauses or EAA Annex I requirements the supplier must satisfy before payment, launch, or renewal.

For covered products and services, Article 24 treats the applicable Annex I requirements as mandatory accessibility requirements within the public procurement directives. That rule does not make every supplier statement sufficient and does not turn the buyer's contractual acceptance into a legal conformity decision. The buyer still needs testable criteria, corrective-action thresholds, retest rules, and a clear decision on whether an issue blocks acceptance, allows conditional acceptance, or is out of scope for the procured item.

Use a four-step acceptance decision: confirm the procured item and EAA or procurement scope; identify every applicable EN 301 549 clause and Annex I requirement; test the delivered version and representative end-to-end journeys; then record accept, conditional accept, or reject with defects, compensating access, owner, deadline, and retest evidence. Contractual acceptance closes a procurement gate, not the supplier's continuing product or service duties.

Supplier evidence should be specific enough for a buyer, auditor, or authority to reproduce the conclusion. Ask for the test scope first: product or service name, version, build, modules, languages, markets, environments, content formats, assistive technologies, testing method, tester independence, known limitations, and remediation status.

For products, the EAA requires manufacturers to draw up technical documentation and an EU declaration of conformity when the applicable product procedure demonstrates compliance. For services, providers must prepare information explaining how services meet applicable accessibility requirements and keep that information while the service operates. Procurement files should preserve those product or service records separately from WCAG test reports.

Article 15 creates a presumption of conformity only for products and services that conform with harmonised standards, or parts of them, whose references have been published in the Official Journal, and only so far as those standards cover the relevant accessibility requirements. The Commission's harmonised standards page also states that use of harmonised standards remains voluntary and that operators may choose another technical solution to demonstrate compliance.

An acceptance memo should say what is presumed, what is technical evidence, and what remains a legal or product decision. If EN 301 549 has been used outside a cited EAA harmonised-standard reference, describe it as a technical benchmark or contractual requirement, not as an automatic presumption of EAA conformity.