EN 301 549

Legal Review: Cecilia Pirchio

v4.1.1 Update

EN 301 549 is the European accessibility standard for ICT products and services. The version cited in the Official Journal of the European Union today is v3.2.1, based on WCAG 2.1 Level AA. The latest version, v4.1.1, was published on 2 September 2026 and is based on WCAG 2.2 Level AA. Its citation is expected in late 2026.

Introduction

EN 301 549 is the European standard that defines accessibility requirements for digital technologies.

It provides a structured framework for making websites, mobile applications, software, and digital products accessible to people with disabilities.

The standard plays a central role in European accessibility regulation. It is the harmonised standard that supports the European Accessibility Act and is used across national laws such as BFSG, BaFG, RGAA, and the Stanca Law.

For organizations operating in Europe, EN 301 549 is the key standard used to translate legal requirements into practical implementation.

What is EN 301 549?

EN 301 549 is a European harmonised standard published jointly by three European standards bodies: CEN (European Committee for Standardization), CENELEC (European Committee for Electrotechnical Standardization) and ETSI (European Telecommunications Standards Institute).

It defines accessibility requirements for Information and Communication Technologies (ICT), including:

• websites

• mobile applications

• software

• digital documents

• multimedia content

• hardware interfaces (such as kiosks and terminals)

The standard is designed to ensure that digital technologies are usable by people with a wide range of disabilities.

It is used by:

• public sector organizations

• private companies

• procurement bodies

• regulatory authorities

to define and assess accessibility requirements.

Current version of EN 301 549

EN 301 549 is updated periodically to keep pace with new technologies and with changes to WCAG.

Two versions are relevant today:

• EN 301 549 v3.2.1, published in March 2021. This is the version currently cited in the Official Journal of the European Union. It is based on WCAG 2.1 Level AA.

• EN 301 549 v4.1.1, published on 2 September 2026. This is the latest version of the standard. It is based on WCAG 2.2 Level AA.

How v4.1.1 is being rolled out

The standard sets fixed dates for national standards bodies:

• 24 August 2026: adopted by CEN, CENELEC and ETSI

• 2 September 2026: published

• 30 November 2026: deadline for national standards bodies to announce it

• 31 May 2027: deadline to publish it as a national standard or endorse it

• 31 May 2028: deadline to withdraw conflicting national standards

These dates cover national adoption. They are separate from citation in the Official Journal, which is the step that makes v4.1.1 the legal reference.

What is the scope of EN 301 549

One of the key differences between EN 301 549 and WCAG is its broader scope.

While WCAG focuses primarily on web content, EN 301 549 covers a wider range of digital technologies.

This includes:

• web and mobile interfaces

• downloadable documents (e.g. PDFs)

• software applications

• multimedia and video content

• ICT hardware and user interfaces

This makes EN 301 549 particularly relevant in public procurement and regulated environments, where accessibility must be ensured across entire systems, not only websites.

Relationship with WCAG

EN 301 549 incorporates WCAG as its foundation for web accessibility.

In practice:

• WCAG defines accessibility requirements for web content

• EN 301 549 includes those requirements and extends them

• additional criteria cover software, documents, and hardware

Version 4.1.1 moves the requirements for web pages, documents and software from WCAG 2.1 to WCAG 2.2. This adds six success criteria:

• 2.4.11 Focus Not Obscured (Minimum)

• 2.5.7 Dragging Movements

• 2.5.8 Target Size (Minimum)

• 3.2.6 Consistent Help

• 3.3.7 Redundant Entry

• 3.3.8 Accessible Authentication (Minimum)

It also removes criterion 4.1.1 Parsing, which WCAG 2.2 made obsolete.

This means that organizations already working with WCAG are covering a significant part of EN 301 549 requirements.

What are the other changes in v4.1.1?

• Real-time communication: the real-time text requirements are revised and now also cover total conversation, where video, text and voice are shared at the same time. New scenarios include emergency communication.

• User preferences: these requirements are reorganised. New clauses cover web pages (9.7) and non-web documents (10.7), alongside the existing clause for software (11.7).

• EAA mapping: v4.1.1 is the first version to map its clauses directly to the requirements of the EAA (Annex ZB). A new Annex ZA, which replaces Annex A of the previous version, maps the standard to the Web Accessibility Directive.

Relationship with the European Accessibility Act

The European Accessibility Act (EAA) defines legal accessibility obligations across the EU.

EN 301 549 provides the technical standard used to meet those obligations.

In practice:

• the EAA defines what must be accessible

• EN 301 549 defines how accessibility is implemented

Organizations preparing for the EAA typically use EN 301 549 as the reference point for compliance.

The legal link works through citation in the Official Journal of the European Union. Meeting the cited version of EN 301 549 gives a presumption of conformity with the accessibility requirements of the EAA.

Where EN 301 549 applies

EN 301 549 is widely used across both public and private sectors.

Public sector

It is commonly required for:

• government websites and platforms

• public administration services

• education and healthcare systems

• digital public services

Public sector organizations are often required to demonstrate compliance with EN 301 549. For public sector websites and mobile apps, the accessibility obligation comes from the Web Accessibility Directive (Directive (EU) 2016/2102). Meeting EN 301 549 is one voluntary way to show conformity with it.

Public procurement

EN 301 549 is strongly tied to public procurement requirements.

When public bodies purchase digital products or services, they often require vendors to meet EN 301 549 accessibility criteria.

This applies to:

• software procurement

• digital platforms

• IT systems

• service contracts

Accessibility becomes a requirement during the purchasing process, not only after deployment.

Private sector (under regulation)

With the introduction of the European Accessibility Act, EN 301 549 also becomes relevant for private organizations offering:

• e-commerce services

• banking services

• telecommunications

• transport and ticketing systems

What EN 301 549 compliance means in practice

Applying EN 301 549 involves ensuring that digital technologies are accessible across different contexts and use cases.

This includes:

• accessible websites and mobile applications

• compatible software interfaces

• accessible documents such as PDFs

• multimedia with captions or alternatives

• hardware interfaces that support different interaction methods

Accessibility must be considered across entire systems, not only individual components.

Common areas covered by EN 301 549

The standard addresses a wide range of accessibility requirements.

Examples include:

• keyboard accessibility

• screen reader compatibility

• colour contrast and visual presentation

• accessible forms and interactions

• captions and audio descriptions

• document accessibility

• interoperability with assistive technologies

These requirements reflect how users interact with digital systems in real conditions.

Does EN 301 549 guarantee compliance?

EN 301 549 provides the technical framework for accessibility in Europe.

Compliance with the standard is a key step, but legal compliance also depends on:

• national legislation (e.g. BFSG, BaFG, RGAA, Stanca Law)

• enforcement mechanisms

• documentation and reporting requirements

The standard supports compliance, while laws define how it is enforced.

How organizations approach EN 301 549

Organizations typically implement EN 301 549 through a structured process:

1. Assess accessibility across systems

2. Identify gaps against EN 301 549 requirements

3. Remediate accessibility issues

4. Integrate accessibility into development and procurement processes

5. Monitor accessibility over time

Because EN 301 549 covers multiple technologies, implementation often involves cross-functional teams.

How Accessiway supports EN 301 549 compliance

Accessiway supports organizations in implementing EN 301 549 through:

• accessibility audits aligned with EN 301 549 and WCAG

• automated accessibility monitoring

• remediation guidance across web, mobile, and documents

• accessibility training

• continuous compliance support

Learn more about how we support accessibility on our paltform page.

These services help organizations align with EN 301 549, the European Accessibility Act, and related national regulations.

Accessibility becomes more effective when it is integrated across systems and maintained over time.