Which version of Standard EN 301 549 applies currently?

Currently, Version 3.2.1 from 2021 applies. This version was published in the Official Journal as a harmonized standard on August 18, 2021, and is legally effective. Successor Version 4.1.1 referencing WCAG 2.2 is expected in October 2026 and is not yet harmonized.

Is Standard EN 301 549 legally mandatory?

Standard EN 301 549 is not a law itself, but becomes mandatory through legislation. The Accessibility Strengthening Act (BFSG) has applied since June 28, 2025, making these requirements binding for commercial enterprises. Public bodies are bound to the same standard through public sector directives. Non-compliance can lead to administrative fines up to €100,000.

What software requirements does Standard EN 301 549 specify?

Software must interface with assistive technology, be fully operable without a mouse, and expose state information programmatically. The standard also requires clear error handling, adequate contrast ratios, and resizable interfaces across desktop and mobile applications.

How do Standard EN 301 549 and the WCAG relate to each other?

The WCAG exclusively addresses web content requirements. Standard EN 301 549 adopts these success criteria in full and extends them to software, mobile apps, digital documents, products, and services. WCAG is therefore a subset of the standard, rather than a competing accessibility framework.

Standard EN 301 549 – The European Standard for Accessibility

Q: What does Standard EN 301 549 regulate?

Standard EN 301 549 is the European benchmark for the accessibility of information and communication technology. It outlines the requirements for accessible information across web content, software, apps, documents, products, and services so that people with disabilities can perceive, operate, and understand this information.

The EN 301 549 standard is the European benchmark for the accessibility of information and communication technology. It outlines requirements for accessible information across web content, software, apps, documents, products, and services. People with disabilities must be able to perceive, operate, and understand this information.

The standard translates the objective of digital accessibility into auditable criteria. For web content, EN 301 549 adopts the WCAG in full; for software and applications, the standard formulates its own dedicated requirements. Its scope therefore extends far beyond that of the WCAG alone.

The standard becomes mandatory through statutory law. The BFSG has applied since June 28, 2025, making accessibility mandates binding for private-sector businesses. Public sector bodies follow the same standard via national public directives, while the overarching European framework is set by the European Accessibility Act.

Standard EN 301 549 at a Glance

✓ Publisher: ETSI jointly with CEN and CENELEC
✓ Current Version: 3.2.1 from 2021, harmonized version since August 18, 2021
✓ Scope: Web content, software, apps, documents, products, and services
✓ Foundation: WCAG 2.1 Level AA compliance for all web content
✓ Legal Status: Mandatory via BFSG and public sector directives

What Standard EN 301 549 Regulates

Standard EN 301 549 outlines functional accessibility requirements for information and communication technology, or ICT. It formulates these criteria in a technology-neutral manner. Thus, the standard does not dictate a specific technical framework, but rather a measurable result: information must be accessible, operable, and understandable.

This is precisely where it differs from the WCAG. The WCAG focuses on web content within the browser. Standard EN 301 549 extends these requirements to all channels through which companies and public sector bodies provide information. Software, digital documents, mobile apps, and hardware fall under its scope just as traditional web content does.

✓ Web Content: Websites and web portals compliant with WCAG 2.1 Level AA
✓ Software and Applications: Desktop and browser-based software applications
✓ Apps: Mobile applications across all operating systems and end devices
✓ Documents: PDFs, forms, and attachments containing structured information
✓ Products: Self-service terminals, kiosks, and hardware featuring digital user interfaces
✓ Services: Support channels, help documentation, and product information

Version 3.2.1 and the Harmonized Version of the Standard

The currently valid Version 3.2.1 dates from March 2021. As a harmonized European standard, this version was published in the Official Journal on August 18, 2021. Organizations meeting the requirements of this version can claim the presumption of conformity.

A new version is on the horizon: Draft 4.1.0 appeared in November 2025, and the final Version 4.1.1 is expected in October 2026 as the official harmonized version. It elevates the technical baseline to WCAG 2.2 and adds requirements concerning focus appearance, dragging movements, and accessible authentication. Until then, Version 3.2.1 remains the authoritative evaluation benchmark for digital accessibility.

1 Version 3.2.1 (2021): Based on WCAG 2.1; current harmonized and mandatory version
2 Draft 4.1.0 (2025): Consultation draft featuring expanded accessibility requirements
3 Version 4.1.1 (expected 2026): Based on WCAG 2.2; triggers presumption of conformity for the EAA

Requirements of Standard EN 301 549 for Web Content

For web content, the standard directly references the WCAG. All information on a website must be structured so that it is perceivable, operable, understandable, and robust. These four WCAG principles form the benchmark against which auditing bodies measure accessibility.

Part of these criteria can be tested automatically, such as color contrast ratios or missing alt texts. Others require manual evaluation, such as keyboard accessibility for complex forms or evaluating whether error messages are clearly phrased.

✓ Perceivable: Text alternatives, captions, and sufficient visual contrast
✓ Operable: Complete keyboard navigation control and visible focus indicators
✓ Understandable: Plain language, clear form labels, and helpful error handling
✓ Robust: Valid markup ensuring assistive technology parses information correctly

Software, Apps, and Documents under Standard EN 301 549

Beyond web content, the standard governs the accessibility of software and digital documents. Software must expose state information programmatically so that a screen reader can read it out loud. Mobile apps are subject to the exact same requirements as desktop software.

Digital documents also fall squarely within this scope. An accessible PDF requires a logical reading order, proper heading hierarchies, and alternative text for images. Publishing information exclusively as scanned, unstructured documents fails to meet the standard.

✓ Software: Compatibility with assistive tools and mouse-free operation
✓ Browser Applications: Correct ARIA roles and names for all UI controls
✓ Apps: Support for native system settings like text scaling and high contrast
✓ Documents: Tagged PDFs featuring structured and understandable information

Who Must Comply with Standard EN 301 549

Standard EN 301 549 is not a law in itself. It becomes mandatory through legal frameworks that reference it. This chain of reference makes the standard the central technical reference point for digital accessibility across Europe.

Affected entities include private-sector businesses offering digital products and consumer services—such as in e-commerce, banking, or passenger transport. The standard is equally mandatory for public sector bodies at federal, state, and municipal levels. Ignoring these mandates risks warning notices and administrative fines up to €100,000.

✓ European Accessibility Act: Defines the legal objective; the standard provides the technical roadmap
✓ BFSG: Mandatory for private enterprises since June 28, 2025
✓ Public Sector Directives: Mandatory for public authorities and government bodies
✓ Web Accessibility Directive: European mandate for public sector web portals

Implementing Standard EN 301 549 in Practice

The implementation begins with a comprehensive audit. Organizations catalog all web content, software, apps, documents, products, and services, mapping them against the respective chapters of the standard. Example: A bank launching a new mobile banking app must document keyboard accessibility, contrast ratios, and screen reader output.

Accessibility does not end with the initial release. Every new version of software or a web portal must continue to meet the requirements. Continuous monitoring exposes non-compliant deviations before site visitors or market surveillance authorities report them. Implementation is therefore an ongoing operational process, not a one-time project.

1 Inventory: Catalog all web content, software applications, and digital documents
2 Audit: Perform automated scans combined with manual evaluations of accessibility
3 Prioritize: Sort deviations from the standard by severity and user impact
4 Remediate: Embed accessibility criteria permanently into development workflows
5 Document: Publish an accessibility statement containing transparent status details

SiteCockpit Solution

easyMonitoring: Audit Standard EN 301 549 Requirements Automatically

easyMonitoring scans your web content against the WCAG criteria that Standard EN 301 549 utilizes as its technical foundation. You receive prioritized remediation tasks covering contrast errors, missing alt text, unlabeled form fields, and keyboard traps. Every new deployment of your site is re-audited so that non-compliant deviations remain transparent.

Discover easyMonitoring →

Frequently Asked Questions About Standard EN 301 549

Which products and services fall under Standard EN 301 549?

The standard applies to web content, software, mobile apps, documents, hardware with digital interfaces, as well as support services and product documentation. The deciding factor is whether information is being provided or digital features are being operated by users.

What changes with Version 4.1.1 of Standard EN 301 549?

Version 4.1.1 elevates the underlying baseline from WCAG 2.1 to WCAG 2.2. New criteria govern focus appearance, dragging movements, and accessible authentication. Additionally, this version is designed to trigger the presumption of conformity for the European Accessibility Act.

How do companies demonstrate compliance with Standard EN 301 549?

Proof is established through documented auditing of all relevant requirements, complemented by a published accessibility statement. Automated scans cover part of the criteria, while manual testing with assistive technology covers the rest. Documentation must remain current for every software version.

Does Standard EN 301 549 apply to public sector bodies as well?

Yes. Public sector entities are bound to the same standard as private companies via public directives and European web accessibility rules. The difference lies not in the technical criteria, but in enforcement deadlines, oversight bodies, and reporting procedures.

Check Compliance with Standard EN 301 549 Now

Unsure which requirements your web content already meets? easyMonitoring delivers a prioritized accessibility audit report with clear action steps. No installation needed—up and running in minutes.

Try for free

EN 301 549