Quick Answer
WCAG and EN 301 549 are not competing standards, so there is no need to choose between them. WCAG sets the accessibility rules for web content, and EN 301 549 incorporates those rules into a broader European standard that also covers software, documents, hardware, and other technology WCAG does not address. EN 301 549 V4.1.1 has now moved its web chapter to WCAG 2.2, though V3.2.1, based on WCAG 2.1, remains the version currently tied to EU harmonisation for the Web Accessibility Directive. For EU compliance, organizations need to confirm which version of EN 301 549 currently applies to their specific legal and product context.
Introduction
Searching “EN 301 549 vs WCAG” often reflects a common assumption: that these are two different, competing accessibility standards, and a business has to pick one, or figure out which one takes priority. In practice, the relationship is simpler than that. One is a global content guideline. The other is a European regulatory standard that includes the first one inside it, then builds significantly beyond it.
WCAG, the Web Content Accessibility Guidelines, is published by the W3C and defines what makes web content accessible. EN 301 549 is a European standard published by ETSI, in cooperation with CEN and CENELEC, that sets accessibility requirements for a much wider range of technology, and it uses WCAG as its foundation for the web portion of that work rather than writing a separate set of web rules from scratch.
This distinction matters right now because both standards sit behind real EU legal obligations. The Web Accessibility Directive uses harmonised EN 301 549 requirements as its technical accessibility framework, and the standard has recently moved to WCAG 2.2 for its web requirements while also being extended to support the European Accessibility Act, which means understanding how the two standards relate now has real compliance stakes attached to it, not just academic interest.
This guide explains what each standard actually covers, exactly how they relate, which version of WCAG is currently referenced, and who is required to comply with which one.
What Is WCAG?
The Web Content Accessibility Guidelines are published by the World Wide Web Consortium’s Web Accessibility Initiative. WCAG defines accessibility requirements for web content, including web pages and web applications, organized around four principles, that content should be perceivable, operable, understandable, and robust. Each success criterion is written to support conformance evaluation, although determining conformance can require human judgment as well as automated checks.
WCAG organizes its success criteria into three conformance levels: A, AA, and AAA. EN 301 549 V3.2.1 specifies WCAG 2.1 Level AA conformance requirements for its web requirements, though a newer edition has since moved to WCAG 2.2, covered later in this guide. WCAG itself is a content guideline. It is not, on its own, a law, and it does not specify how a government or regulator should enforce it, that part is left to whichever law or standard chooses to reference it.
What Is EN 301 549?
Who develops EN 301 549 and why does it exist
EN 301 549 is a harmonised European standard titled “Accessibility requirements for ICT products and services.” It is developed by ETSI’s Human Factors technical committee together with CEN and CENELEC, in response to standardisation requests from the European Commission. The standard has its roots in European ICT accessibility and public procurement. It was written with detailed test procedures and evaluation methodology attached to each requirement, described to a level of detail intended to give consistent, comparable results regardless of who runs the test. Today its role extends beyond procurement: it also provides a technical route for demonstrating conformity with certain EU accessibility requirements, when the relevant version has been formally referenced for that purpose.
The standard opens with a set of functional performance criteria, covering things like usage without vision, usage with limited hearing, usage with limited manipulation or strength, and usage with limited cognition, language, or learning. These describe the underlying user needs the rest of the standard is built to address, before getting into specific testable requirements.
What does EN 301 549 cover beyond the web
The standard covers far more than websites. Its clauses address generic ICT requirements, two-way voice communication, video, hardware, web content, non-web documents, non-web software, documentation and support services, and relay or emergency service access. EN 301 549 is structured so that requirements apply according to the type and functionality of the ICT product or service being evaluated.
A requirement that depends on a particular feature does not automatically apply to a product that does not have that feature. A piece of hardware with no video functionality, for example, is not expected to meet the video-related requirements, and a product with no two-way voice communication is not assessed against the real-time text requirements built for that use case. This means an organization does not blindly test every clause against every product; it first identifies what the product or service actually contains, then determines which requirements apply.
How Do EN 301 549 and WCAG Actually Relate?
How Clause 9 uses WCAG for web content
Clause 9 of EN 301 549 V3.2.1 contains the web accessibility requirements based on WCAG 2.1, specifying WCAG conformance requirements at Level AA. The newer V4.1.1 edition carries this same approach forward but moves Clause 9 to WCAG 2.2, covered in detail in the next section. In practice, this means EN 301 549 does not define a separate, competing set of web accessibility rules under either version. For the web, it builds directly on WCAG’s own success criteria, not an alternative version of them.
What EN 301 549 adds beyond WCAG
The difference is everything outside Clause 9. Non-web documents, covered in a dedicated clause, sets requirements for things like PDFs and other files that are not web pages but still need to be perceivable and operable, text alternatives, proper structure, and captioning where relevant. Non-web software covers native applications such as mobile apps, with its own EN 301 549 requirements for how well they work with assistive technology like screen readers at the operating system level.
It is worth being precise here: WCAG itself is a web standard. The W3C separately publishes WCAG2ICT and WCAG2Mobile as informative guidance on applying WCAG concepts to non-web technology and mobile apps, but the actual binding requirements for non-web software within EN 301 549’s scope come from EN 301 549 itself, not from WCAG directly. A separate hardware clause sets physical requirements like reachable controls and tactile indicators for physical devices such as self-service kiosks or ticket machines. Another clause covers documentation and support services, meaning a product’s manuals and customer support also need to be accessible, not just its interface.
Which Version of WCAG Does the Harmonised EN 301 549 Use?
This is one of the points readers ask about most, and it is currently in flux, so precision matters here.
The version of EN 301 549 currently tied to the Web Accessibility Directive’s presumption of conformity is V3.2.1, published in March 2021. Its own text states plainly that it reflects the content of the W3C WCAG 2.1 Recommendation, at Level AA.
A newer edition, EN 301 549 V4.1.1, has now been officially adopted by ETSI’s National Standardisation Bodies following the voting period, and published dated September 2026. Clause 9 of this edition now refers to WCAG 2.2 instead of WCAG 2.1, and the update also revises the document and software clauses to align with WCAG 2.2, while adding new annexes mapping the standard’s requirements directly to both the Web Accessibility Directive and the European Accessibility Act.
Publication and adoption by ETSI is a significant step, but it is separate from legal effect under EU law: a presumption of conformity applies once a specific version is cited in the Official Journal of the European Union, and as of this writing, V3.2.1 remains that cited, harmonised version for the Web Accessibility Directive. Anyone citing EN 301 549 conformance should check which version and which WCAG level their claim is actually based on, since the standard’s technical content and its legal status under a specific directive can move on separate timelines.
Who Actually Has to Comply With EN 301 549?
Public sector bodies, under the Web Accessibility Directive
The EU’s Web Accessibility Directive uses EN 301 549 as its technical accessibility framework for public sector websites and mobile apps. Where EN 301 549 is cited in the Official Journal of the European Union under this Directive, conformance with the standard’s relevant clauses gives what the standard itself calls a presumption of conformity with the Directive’s essential requirements. That is a specific legal mechanism, not simply a general claim of good practice, and it applies to the specific clauses the standard’s own annex maps to the Directive, not automatically to every clause in the full document.
Private sector organizations, under the European Accessibility Act
The European Accessibility Act is legislation that establishes accessibility requirements for specified products and services, including e-commerce, banking, and e-books. EN 301 549 is an important technical standard that has been updated, through V4.1.1, to include requirements and mappings relevant to the EAA’s implementation. Organizations should identify the legal requirements that apply to their product or service under the EAA, then determine the relevant harmonised standards or other applicable technical specifications, rather than assuming EN 301 549 is automatically the single required route.
Does Meeting WCAG Mean You Meet EN 301 549?
For the web portion specifically, meeting the applicable WCAG requirements addresses the core content of EN 301 549’s web clause. It does not, by itself, demonstrate conformity with every applicable EN 301 549 requirement. Depending on what the organization actually builds and provides, whether that includes native mobile software, hardware, documents, or support services, other requirements may still apply.
A company that only operates a website, with no native app, no physical hardware, and no separate document library, may find that its WCAG conformance work covers nearly everything relevant to them. A company that also ships a native mobile app, provides downloadable PDF reports, and offers phone-based customer support has several more requirements to work through, none of which a web-only WCAG audit would have touched.
The right way to determine full EN 301 549 conformance is to work through the standard’s requirements for the specific product or service in question, not to assume that a WCAG audit alone covers everything.
How Do You Actually Test for EN 301 549 Compliance?
A practical approach follows a clear sequence.
- First, identify the legal framework that actually applies – the Web Accessibility Directive, the European Accessibility Act, or another applicable law. This determines which version of EN 301 549 and which requirements are relevant.
- Second, identify which EN 301 549 requirements apply to the specific product or service, based on what it actually contains.
- Third, test web content against the applicable WCAG requirements, using a mix of automated and manual methods.
- Fourth, test whatever other applicable requirements exist – non-web documents, native software, hardware, or support services.
- Fifth, combine automated and manual testing throughout: automated testing can identify many issues that can be checked programmatically, but it cannot evaluate every aspect of accessibility or replace human evaluation.
- Sixth, where appropriate, testing should also consider relevant assistive technologies and real user journeys.
- Finally, document findings clearly and retest after fixes are made, since a single pass does not confirm the fix actually resolved the problem in practice.
BarrierBreak’s EN 301 549 Testing service follows this same logic, evaluating the applicable accessibility requirements of EN 301 549 across the relevant parts of an ICT product or service, rather than limiting the assessment to web content alone, and provides a report identifying what needs to change to meet the applicable requirements.
Frequently Asked Questions
Is EN 301 549 legally binding on its own?
EN 301 549 is a technical standard, not a law itself. It becomes legally significant through the laws that reference it, such as the Web Accessibility Directive, which use it as the technical benchmark for compliance once a specific version is formally cited for that purpose.
Does the European Accessibility Act use EN 301 549 as its technical standard?
EN 301 549 is an important technical standard within the European accessibility framework and has now been updated, through EN 301 549 V4.1.1, to support EAA implementation, including new sections mapping its requirements to the Act. The EAA itself remains the legislation; EN 301 549 is a technical standard developed to help demonstrate conformity with it, not the source of the legal obligation itself.
What happens if only some EN 301 549 requirements apply to my product?
That is expected, and it is how the standard is designed to work. Requirements apply according to the type and functionality of the product or service being evaluated, so only the ones relevant to what it actually does apply. A product with no video functionality, for instance, is not assessed against the video-related requirements, and a product with no two-way voice communication skips the real-time text requirements entirely.
Is an accessibility statement the same thing as EN 301 549 compliance?
No. An accessibility statement is a separate transparency and communication mechanism required under certain accessibility laws, such as the Web Accessibility Directive for public sector websites and mobile apps. It does not itself prove that a product conforms to EN 301 549 or WCAG; conformance requires evaluation against the applicable requirements.
Does EN 301 549 apply to companies outside the EU?
It can, where the applicable EU law, such as the European Accessibility Act, covers the product or service and its market activity in the EU. The obligation comes from the applicable legislation, not from EN 301 549 itself, and not from where the company is headquartered.
Is there a US equivalent to EN 301 549?
Section 508 serves a broadly similar role in the United States, setting ICT accessibility requirements for federal agencies, and it also references WCAG for web content. The two standards are not identical in scope or structure, but organizations already working with one often find meaningful overlap with the other.
Further Reading
EAA Digital Accessibility Compliance: What the Carrefour Ruling Teaches Every Business
