EN 301 549 is the European accessibility standard for ICT products and services, and it adopts WCAG 2.1 Level AA as the technical baseline for web content and mobile applications. When a product needs to meet EN 301 549 for web or mobile, meeting WCAG 2.1 AA covers the core requirements. EN 301 549 then adds requirements that go beyond the web, such as hardware, documentation, support services, and non-web software. WCAG sits inside EN 301 549, not alongside it.
| Aspect | How They Connect |
|---|---|
| Web content | EN 301 549 references WCAG 2.1 AA directly through Chapter 9. |
| Mobile applications | WCAG 2.1 AA applies through Chapter 11, with mobile-specific notes. |
| Non-web documents | WCAG criteria are applied to electronic documents under Chapter 10. |
| Beyond WCAG | Hardware, two-way voice, biometrics, and support services have their own clauses. |
| EAA tie-in | EN 301 549 is the technical reference used to demonstrate EAA conformance. |
What Is EN 301 549?
EN 301 549 is the harmonized European standard titled “Accessibility requirements for ICT products and services.” It is published by ETSI in cooperation with CEN and CENELEC. The standard defines accessibility requirements for a wide range of information and communication technology, including websites, mobile apps, software, hardware, telecommunications equipment, and self-service terminals.
The standard was originally created to support European public procurement. Public sector bodies in the EU use EN 301 549 to confirm that the digital products they buy meet accessibility requirements. The standard has since become the technical reference behind the European Accessibility Act.
What Is WCAG?
The Web Content Accessibility Guidelines, or WCAG, are published by the W3C through the Web Accessibility Initiative. WCAG defines how to make web content more accessible to people with disabilities. The guidelines are organized under four principles: perceivable, operable, understandable, and robust.
WCAG 2.1 AA is the version most often cited in regulations worldwide. WCAG 2.2 AA is the most recent stable version and adds requirements focused on cognitive, mobile, and low-vision accessibility. EN 301 549 currently references WCAG 2.1 AA as its baseline.
How Does EN 301 549 Relate to WCAG?
EN 301 549 incorporates WCAG by reference. Chapter 9 of the standard covers web content and points directly to WCAG 2.1 Level A and AA success criteria. If a website meets WCAG 2.1 AA, it meets the web requirements of EN 301 549.
Chapter 11 covers non-web software, including mobile applications. It applies the same WCAG success criteria, with adjustments for software contexts where a criterion does not map cleanly. Chapter 10 covers non-web documents, such as PDFs, and applies WCAG criteria where they fit.
The relationship is layered. WCAG provides the success criteria. EN 301 549 wraps those criteria with additional requirements that WCAG was never written to cover, such as physical hardware buttons, biometric authentication, and customer support channels.
What Does EN 301 549 Cover That WCAG Does Not?
WCAG focuses on web and digital content. EN 301 549 covers ICT as a whole. The standard includes clauses for hardware design including controls, connectors, and indicators; two-way voice communication including real-time text and video relay; closed functionality such as kiosks and ticket machines that do not allow assistive technology to be installed; biometric authentication alternatives; and documentation and support services including help desks and training.
These clauses extend accessibility requirements into areas that purely web-based guidelines cannot address. A self-service kiosk in an airport, for example, has both a screen and physical hardware. WCAG can speak to the on-screen interface. EN 301 549 covers the rest.
How Does This Connect to the European Accessibility Act?
The European Accessibility Act, or EAA, went into effect on June 28, 2025. The EAA sets accessibility requirements for products and services sold or offered in the EU, including ecommerce, banking, ebooks, transport, and consumer electronics.
The EAA is the law. EN 301 549 is the technical reference used to demonstrate conformance with that law. A company that meets EN 301 549 has a strong basis for showing EAA conformance. And because EN 301 549 incorporates WCAG, a website that meets WCAG 2.1 AA is well positioned to meet the digital portion of the EAA.
Should You Evaluate Against WCAG or EN 301 549?
For a website or mobile app, a WCAG 2.1 AA evaluation covers the technical criteria that EN 301 549 references for that content. The evaluation identifies issues against each success criterion and produces a report that can be used as evidence of conformance work.
If your product includes hardware, kiosks, telecommunications features, or non-digital support services, the evaluation scope needs to extend beyond WCAG to address the additional EN 301 549 clauses that apply. For most digital-only products, WCAG 2.1 AA is the right starting point.
Does meeting WCAG 2.1 AA mean a product is EN 301 549 conformant?
For web content, yes, meeting WCAG 2.1 AA satisfies the web requirements within EN 301 549. For mobile apps and non-web software, WCAG 2.1 AA covers most of the technical criteria, but the standard includes a few additional software-specific clauses to confirm. For products that include hardware or other ICT categories, WCAG alone is not enough.
Will EN 301 549 be updated to reference WCAG 2.2?
EN 301 549 is updated periodically. The current published version references WCAG 2.1. Future versions can adopt WCAG 2.2 once the European standards bodies complete their review process. Companies preparing for long-term EAA conformance often choose to evaluate against WCAG 2.2 AA to stay ahead of the next update.
Is EN 301 549 only for European companies?
No. Any company offering products or services in the EU may need to meet EN 301 549 to satisfy the EAA. This includes US-based ecommerce sites, SaaS products, and mobile apps available to EU consumers. The standard applies based on where the product is offered, not where the company is headquartered.
How does EN 301 549 differ from Section 508?
Both standards reference WCAG 2.0 or 2.1 AA for web content and both cover ICT broadly. Section 508 applies to US federal agencies and their suppliers. EN 301 549 applies in the EU, primarily for public procurement and EAA conformance. The technical overlap is significant, which is why many ACRs cover both editions.
EN 301 549 and WCAG are not competing standards. WCAG is the technical foundation for digital content. EN 301 549 places that foundation inside a wider European framework that covers everything from a webpage to a ticket machine.
Contact Kris Rivenburgh for guidance on EN 301 549, WCAG, and EAA conformance.