{"id":992296,"date":"2026-05-25T14:26:05","date_gmt":"2026-05-25T14:26:05","guid":{"rendered":"https:\/\/ifdb.io\/en301549\/"},"modified":"2026-10-12T11:43:36","modified_gmt":"2026-10-12T11:43:36","slug":"en-301-549-standard","status":"publish","type":"page","link":"https:\/\/ifdb.io\/en\/en-301-549-standard\/","title":{"rendered":"EN301549"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t
DIGITAL ACCESSIBILITY \u00b7 EU STANDARD \u00b7 BFSG \u00b7 EAA \u00b7 WCAG 2.2<\/h6>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

\nEN 301 549<\/span>\n \u2013 the European standard that makes digital accessibility measurable.<\/span><\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

EN 301 549 is the technical standard used in Europe to determine whether a website, an app or a document is accessible \u2013 or not. It translates the requirements of legislation such as the BFSG and the European Accessibility Act into verifiable criteria. Anyone wishing to know exactly what compliance means cannot ignore this standard. On this page, we explain in simple terms what EN 301 549 requires, how it relates to WCAG, and how you can provide robust evidence that will stand up in court and in tendering processes. <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tBook a Demo<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tStart Access Score\u00ae<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Trusted by leading companies across the DACH region
Featured as an expert on ZDF WISO<\/h6>\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span><\/h2><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t

What EN 301 549 is \u2013 and why it goes beyond web guidelines alone<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

EN 301 549 is officially titled \u201cAccessibility requirements for ICT products and services\u201d and is the harmonised European standard for the accessibility of information and communication technology. It was developed jointly by the European standardisation organisations CEN, CENELEC and ETSI. Its scope is deliberately broader than that of a web accessibility guideline alone: it covers websites and mobile apps as well as software, documents, hardware, telecommunications equipment and support services. <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The key area that most managers look at first is digital services. Yet this is precisely where the most common misconception lies: anyone who simply checks their website has only half understood the standard. An inaccessible PDF in the customer portal, a tariff calculator that cannot be operated using a keyboard, or a support chat without screen reader support are just as much covered by EN 301 549 as a contrast error in the page header. <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

What EN 301 549 is \u2013 and why it goes beyond web guidelines alone<\/h3>

EN 301 549 is officially titled \u201cAccessibility requirements for ICT products and services\u201d and is the harmonised European standard for the accessibility of information and communication technology. It was developed jointly by the European standardisation organisations CEN, CENELEC and ETSI. Its scope is deliberately broader than that of a web accessibility guideline alone: it covers websites and mobile apps as well as software, documents, hardware, telecommunications equipment and support services. <\/p>

The key area that most managers look at first is digital services. Yet this is precisely where the most common misconception lies: anyone who simply checks their website has only half understood the standard. An inaccessible PDF in the customer portal, a tariff calculator that cannot be operated using a keyboard, or a support chat without screen reader support are just as much covered by EN 301 549 as a contrast error in the page header. <\/p>

From legislation to standard: how the BFSG, EAA and EN 301 549 work together<\/h4>

Laws set out obligations \u2013 but they rarely specify how these should be met from a technical perspective. EN 301 549 fills this gap. In Germany, the Accessibility Strengthening Act (BFSG), which transposes the European Accessibility Act into national law, requires certain products and services to be accessible. The European Accessibility Act has been in force since 28 June 2025, and EN 301 549 is regarded as the technical standard underpinning both sets of regulations. <\/p>

In practical terms, this means that if your digital offering meets the requirements of EN 301 549, the legal obligation is generally deemed to have been fulfilled \u2013 this is known as the \u2018presumption of conformity\u2019. For the public sector, this requirement has long been established through the Web Accessibility Directive and BITV 2.0. With the BFSG, the same technical benchmark now also applies to large parts of the private sector: e-commerce, banking, insurance, telecommunications and transport services. The standard has thus evolved from a niche issue in the public sector into a binding benchmark for the market. <\/p>

The presumption: the legal leverage behind the provision<\/h4>

The fact that the legal obligation is \u2018generally deemed to have been met\u2019 if you comply with EN 301 549 sounds like a formality. It is the most important tool that the standard provides you with. <\/p>

EN 301 549 is a harmonised<\/strong> standard \u2014 it is referenced in the Official Journal of the EU. This is precisely what gives rise to the presumption of conformity: anyone who can demonstrate that their products and services are designed in accordance with the standard is presumed to meet the requirements of the legal act in which it is cited. This is not an argument you need to construct yourself, but rather the approach expressly provided for by the legislator. <\/p>

The true value of this only becomes apparent in a crisis. Without reference to EN 301 549, in the event of a complaint or an inspection by market surveillance authorities, you would have to demonstrate in detail that your product meets the abstract requirements of the law \u2014 criterion by criterion, off the top of your head, under time pressure. With documented evidence in accordance with the standard, the balance shifts in your favour: you demonstrate compliance with the standard, and compliance with the law is presumed. <\/p>

The true value of this only becomes apparent in a crisis. Without reference to EN 301 549, in the event of a complaint or an inspection by market surveillance authorities, you would have to demonstrate in detail that your product meets the abstract requirements of the law \u2014 criterion by criterion, off the top of your head, under time pressure. With documented evidence in accordance with the standard, the balance shifts in your favour: you demonstrate compliance with the standard, and compliance with the law is presumed. <\/p>

EN 301 549 and WCAG \u2013 why the standard sets higher requirements than the guidelines<\/h4>

The two terms are often used synonymously, and this regularly leads to gaps in compliance evidence. The W3C\u2019s WCAG (Web Content Accessibility Guidelines) are the internationally recognised basis for accessible web content. EN 301 549 adopts these criteria \u2013 and then adds its own, more stringent requirements on top. Specifically, the currently referenced version, EN 301 549 V3.2.1, fully incorporates WCAG 2.1 at Level AA. This means that every WCAG success criterion is also an integral part of the standard. <\/p>

However, the standard does not stop there. Among other things, it sets out requirements for hardware, biometric procedures, speech output and real-time communication, as well as for software and documents that WCAG does not address at all. So, even if a site is \u2018only\u2019 WCAG-compliant, it may still fail an EN 301 549 audit \u2013 for example, because a PDF is not tagged in accordance with PDF\/UA or because an application outside the browser contains barriers. In practical terms, this means that WCAG is the foundation and EN 301 549 is the building. Both must be evaluated. <\/p>

How the standard is structured \u2013 the key chapters<\/h4>

EN 301 549 is structured in a modular way, and certain sections are particularly relevant for digital services. Chapter 5 brings together the generic requirements \u2013 principles that apply to almost every product, such as operability without the need for specific physical abilities or usability with assistive technologies. Chapter 9 is devoted to the web and refers directly to the WCAG success criteria; this is the part most people refer to when they talk about an \u2018accessible website\u2019. Chapter 10 focuses on non-web documents, such as PDFs, Office files and similar formats \u2013 this is often where the biggest hidden gap lies in public authorities and large organisations, as existing document archives are rarely checked. Chapter 11 deals with software, native apps and user interfaces outside the browser, and Chapter 12 makes it clear that documentation and support services \u2013 help pages, guides and customer service \u2013 must also be accessible. <\/p>

The breadth of this issue is the reason why an automated scanner alone cannot provide a reliable assessment in accordance with EN 301-549. Tools can detect some technical errors, but they cannot assess whether a screen reader reads out the ordering process clearly or whether a complex document is structured logically. <\/p>

Modular design: They do not comply with the entire standard, but with the relevant sections<\/h4>

At first glance, the list of chapters in EN 301 549 seems overwhelming, and we regularly hear the same phrase: \u2018We\u2019ll never manage that.\u2019 But nobody has to. The standard has a modular structure, and depending on the products and services you offer, different chapters will apply to you \u2014 an online shop will have different requirements to a hardware manufacturer, and a bank will have different requirements to a streaming service. You do not need to comply with the entire standard, but only with the specific parts that apply to your offering. <\/p>

The sequence of the standard also follows a logic that is worth understanding: it begins with the question of what people need to be able to do. Only then does the question arise as to how the relevant technology makes this possible. It is not the technology that sets the standard, but its use. <\/p>

There is a downside to this approach: the scope must be right. Anyone who only checks the \u2018Web\u2019 chapter \u2013 simply because it is the best known \u2013 has not worked in a modular way, but has taken the easy option. The first step in any robust audit is therefore not a test, but an honest assessment: which chapters actually apply to us? <\/p>

A case study<\/strong>: A service provider was convinced that a website thoroughly tested for compliance with WCAG met all the requirements. An audit against the full EN 301 549 standard revealed the shortcoming: all contractual documents and forms were available as PDFs that were neither tagged in accordance with PDF\/UA nor otherwise made accessible, and the only support channel was a telephone hotline with no text-based alternative. The website was compliant, but the overall service offering was not. <\/p>

Functional performance characteristics: the core of the standard<\/h4>

The conceptual core of EN 301 549 is missing from almost every superficial description \u2014 and it is no coincidence that it features right at the start of the standard: the functional performance characteristics. These do not describe technical details, but rather the overarching uses that a product must enable. These include, amongst others: <\/p>