Skip to main content
European Union · Technical standard

What is EN 301 549?

The harmonised European standard for ICT accessibility. Referenced by both the Web Accessibility Directive (public sector) and the European Accessibility Act (private sector) as the technical compliance path.

Published
v4.1.1 · 2025
Publisher
ETSI · CEN · CENELEC
Web baseline
WCAG 2.1 Level AA
Scope
Web · software · hardware · docs

EN 301 549 is the harmonised European standard for accessibility requirements for ICT products and services. It is published jointly by ETSI, CEN and CENELEC — the three recognised European standardisation organisations — and is mandated in Mandate M/376 of the European Commission.

The standard was first published in 2014 (v1.1.1) and has since gone through multiple updates. The current major version, v3.2.1 (published 2021), was updated by v4.1.1 in 2025 to align with the enforcement of the European Accessibility Act. Future versions are expected to upgrade the embedded WCAG reference from 2.1 to 2.2.

EN 301 549 is not itself a law. It becomes legally binding through two EU directives: the Web Accessibility Directive (WAD, 2016/2102) for public-sector bodies, and the European Accessibility Act (EAA, 2019/882) for private-sector products and services. Conformance to EN 301 549 gives a legal presumption of conformance to both.

The standard wraps WCAG 2.1 Level AA for web and software and adds non-web requirements covering hardware (clause 8), software that isn’t web (clause 11), ICT with two-way voice comms (clause 6), video capabilities (clause 7), self-contained closed products (clause 8), support documentation (clause 12) and ICT provision of biometrics, authoring and user-preference controls.

Scope

Who must comply?

Any organisation subject to the Web Accessibility Directive or the European Accessibility Act is expected to demonstrate EN 301 549 conformance as their compliance path.

Public-sector bodies (via WAD). Every central-government, regional, local authority, public hospital, public university, court system and public-service body in the 27 EU member states (plus Norway, Iceland and the UK for legacy WAD requirements). Covers websites, mobile apps, intranets and extranets used to deliver public services.

Private-sector entities (via EAA). Any company placing covered products (self-service terminals, e-readers, consumer computing, TVs) or providing covered services (e-commerce, banking, e-books, transport, telecoms, emergency comms) on the EU market. Microenterprise exemption applies only to services.

ICT procurement — public buyers. Under EU Directive 2014/24 on public procurement, EN 301 549 is the mandatory technical reference for public bodies buying accessible ICT. Vendors that cannot produce EN 301 549 conformance documentation are routinely disqualified at tender stage.

International vendors. Any non-EU company selling into the EU market must demonstrate EN 301 549 conformance alongside their ACR/VPAT for US federal Section 508. The two documents are different but can share audit evidence — WCAG-based criteria overlap.

Key requirements

The 13 clauses of EN 301 549

The standard is organised into functional performance statements (clause 4) plus 12 topic-specific requirement clauses. Conformance means meeting every applicable clause for your product type.

Clause 4

Functional performance statements

11 outcome-based statements (usage without vision, with limited vision, without colour perception, without hearing, without speech, with limited manipulation, limited reach/strength, seizure risk, limited cognition, privacy maintained, interoperability).

Clause 5

Generic requirements

Applies across all ICT: activation of accessibility features, biometrics alternatives, preservation of accessibility info, operable parts, locking and toggle keys, user-preference settings.

Clause 6

ICT with two-way voice

Phones, VoIP, messaging apps, video-conferencing. Real-time text (RTT), audio bandwidth, caller-ID support, speech-recognition interoperability, video for signed communication.

Clause 7

Video capabilities

ICT that displays video must support captions (display, playback, user controls), audio description and spoken-subtitle playback. Live and recorded content both covered.

Clause 8

Hardware

Physical devices: self-service terminals, ATMs, kiosks, set-top boxes. Tactile keypads, reachable operable parts, port/connector standards, key repeat control, contrast of physical controls.

Clause 9

Web

All 50 WCAG 2.1 Level A and AA success criteria, applied to web content delivered through the product.

Clause 10

Non-web documents

Applies WCAG 2.1 A and AA to PDFs, Word documents and similar. Most tools rely on PDF/UA-1 / ISO 14289-1 for PDF conformance.

Clause 11

Non-web software

Native applications, desktop apps, mobile apps: same WCAG criteria adapted to non-web context plus interoperability with platform accessibility APIs.

Clause 12

Documentation and support

Product documentation must be accessible, must describe accessibility features, must be offered free of charge. Support services must be able to answer accessibility queries.

Clause 13

ICT providing relay

ICT that provides a text or video relay service must meet real-time and privacy requirements for Deaf users, including RTT support and consistent call-handling.

Penalties & enforcement

What non-compliance costs

EN 301 549 itself doesn’t carry penalties — they sit in the WAD (for public sector) and the EAA national transpositions (for private sector). But the consequences of a failed EN 301 549 audit are immediate.

Lost tender

Procurement disqualification

The most common and immediate consequence. Public-sector ICT tenders under EU procurement rules require EN 301 549 conformance evidence. Vendors without it are routinely excluded.

WAD action

Enforcement body complaints

National enforcement bodies (Commissioner, Ombudsman or equivalent) can order remediation, publish non-compliance, and in some states levy administrative fines.

EAA fines

Member-state penalties

EAA national transpositions link EN 301 549 non-conformance to financial penalties — up to €1M in Spain, 5 % of turnover in Italy, €100k in Germany and Ireland.

Reputational and market-access risk. Products and services named in public non-conformance reports lose consumer trust quickly. Several member states publish a public non-compliance registry.

Cross-referenced with WCAG. Because EN 301 549 wraps WCAG 2.1 AA, any automated or manual WCAG audit that reveals failures directly translates into EN 301 549 non-conformance — same finding, double regulatory exposure.

Deadlines

Versions and milestones

EN 301 549 updates roughly every 3–4 years. Staying on the current version is part of ongoing compliance; older versions do not automatically satisfy newer WAD or EAA expectations.

February 2014

v1.1.1 published

First release. Technical requirements for ICT accessibility in public procurement under Mandate M/376.

January 2018

v2.1.2 published

Aligned with the 2016 Web Accessibility Directive. Added explicit WCAG 2.0 AA mapping and functional performance clauses.

November 2019

v3.1.1 published

Major update: upgraded web/software reference from WCAG 2.0 to WCAG 2.1 Level AA. Expanded non-web and documentation clauses.

March 2021

v3.2.1 published

Current stable baseline at EAA entry into force. Editorial improvements and clarifications but the same WCAG 2.1 AA core.

2025

v4.1.1 published

Updated to align with enforcement of the European Accessibility Act (June 2025). Adjustments to hardware, self-service terminals and consumer-product clauses.

Expected 2026–2027

Move to WCAG 2.2

ETSI/CEN/CENELEC consultation under way. Next major version expected to embed WCAG 2.2 AA, raising the baseline for all EU compliance.

How to comply

Your EN 301 549 conformance checklist

Treat EN 301 549 as your single European accessibility reference. If you meet it, you cover the WAD, the EAA, EU public procurement and most national public-sector requirements in one audit cycle.

Identify which clauses apply to your product type
A pure web app uses clauses 4, 5, 9, 12. A mobile app adds clause 11. A consumer PDF adds clause 10. A kiosk adds clauses 6, 7, 8, 13. Scope first, audit second.
Audit web and app against WCAG 2.1 Level AA
50 success criteria across Perceivable, Operable, Understandable, Robust. Automated scan plus manual keyboard, screen-reader, zoom and contrast testing.
Audit PDFs against PDF/UA-1 / ISO 14289-1
Clause 10 for non-web documents. Tagged structure, reading order, alt text, table headers, title metadata, language, logical order.
Document functional performance (clause 4)
For every product, demonstrate how the 11 outcomes are met — use without sight, hearing, speech, etc. This is narrative evidence, not just a WCAG checklist.
Produce a clause-by-clause conformance report
Structured report mapping each applicable clause to evidence: test results, screenshots, assistive-tech logs, ACR/VPAT supplementary evidence.
Publish an accessibility statement
Required under WAD and EAA. State standard version (EN 301 549 v4.1.1), scope, non-conformance list, feedback mechanism and national enforcement contact.
Retain technical documentation for 5 years
EAA requires this explicitly. National market-surveillance bodies can request evidence without prior notice during this period.
Re-audit on every major release and every EN 301 549 update
A 2021-era audit does not demonstrate v4.1.1 conformance. Re-audit when the standard updates or when material product changes ship.
Next step

Test against EN 301 549 and WCAG 2.1/2.2 AA

Our checkers map every failure directly to the EN 301 549 clause, the WCAG criterion, and the EAA / WAD provision. One audit, all three European references.