VPATFast.com

Home / Guides / What is EN 301 549, and how does it relate to WCAG?

Guide · Updated November 21, 2026

What is EN 301 549, and how does it relate to WCAG?

How EN 301 549 is structured, how clause 9 maps to WCAG, which clauses a SaaS product usually covers, and how it relates to the EU VPAT and the EAA.

European buyers often ask for an "EN 301 549" conformance report, which is the EU edition of the VPAT. Many teams know WCAG well but are unsure what EN 301 549 adds. This guide explains how the standard is structured, how it relates to WCAG, and which clauses a SaaS product usually needs to fill in.

What it is

EN 301 549 sets accessibility requirements for ICT products and services. It is published jointly by the European standards organizations ETSI, CEN and CENELEC. It covers more than the web: software, hardware, documentation and support services are in scope too. The version referenced by the EU rules for public sector websites and apps is v3.2.1. A new version is in preparation; check its publication in the Official Journal of the EU before you adopt it.

How it relates to WCAG

Clause 9 (Web) references WCAG directly. In v3.2.1 it covers WCAG 2.1 Level A and AA, and each requirement number is the WCAG number with "9." in front. For example, WCAG 1.1.1 becomes 9.1.1.1, and WCAG 2.4.7 becomes 9.2.4.7. Clause 11 (Software) and clause 10 (Non-web documents) also reuse many WCAG criteria, adapted for software and documents.

So if your product has been tested against WCAG 2.1 AA, you can largely reuse those results for clause 9. The six new A and AA criteria in WCAG 2.2 (such as 2.5.8 Target Size (Minimum) and 3.3.8 Accessible Authentication (Minimum)) are not required by v3.2.1, but test them anyway: the next version is expected to follow WCAG 2.2, and many customers already ask for WCAG 2.2 directly. See the six new WCAG 2.2 criteria for details.

Clause structure

ClauseTopicNotes
4Functional performance statementsDescribed by user ability: without vision, limited vision, without perception of color, without hearing, limited hearing, without vocal capability, limited manipulation or strength, limited reach, minimizing photosensitive seizure triggers, limited cognition, language or learning, and privacy. SaaS products usually fill this in.
5Generic requirementsClosed functionality, biometrics, preserving accessibility information during conversion, and similar. Partly applicable to SaaS.
6ICT with two-way voice communicationApplies only if the product has voice or video calling.
7ICT with video capabilitiesCovers captions and audio description when the product plays video.
8HardwareUsually not applicable to pure SaaS.
9WebWeb content, mapped one to one to WCAG A and AA. The core of a SaaS report.
10Non-web documentsFor example, PDF or Word files the product exports or offers for download.
11SoftwareDesktop and mobile apps, plus requirements for authoring tools.
12Documentation and support servicesAccessibility of help documentation and support channels.
13ICT providing relay or emergency service accessApplies only to ICT that provides these services.

Clauses 1 to 3 cover scope, references and definitions. You do not answer them in the report.

Which clauses a SaaS product usually fills in

  • Always: clauses 4, 9 and 12.
  • Depending on the product: clause 10 if you export or offer PDF or Word files for download; clause 11 if you have a desktop or mobile app; clause 6 if you have calling features; clause 7 if you play video.
  • Usually not applicable: clause 8 (hardware) and clause 13 (relay and emergency services). When you mark them Not Applicable, explain why in the remarks.

How it relates to the EU EAA

The European Accessibility Act (EAA) defines which products and services must meet accessibility requirements. EN 301 549 is the most common reference for showing that you meet the technical requirements, but the harmonized standards under the EAA are still being written. To find out whether your product is in scope and what it needs to do, read what the EAA means for SaaS and talk to legal counsel.

Next step

Use the EAA accessibility statement generator, or choose "EU e-commerce and digital services: EU + EAA statement" as the target market in the generator, to create a draft EU edition ACR for EN 301 549 and a draft statement. The result is a self-assessed draft; confirm it against your actual test results before you publish it.

Ready to draft your ACR?

The preview is free. US$49 one-time per product to download the ACR and the statement.

Open the generator