Loading…
Loading…
The European standard defining accessibility requirements for ICT products and services.
stellae.design
EN 301 549 is the European harmonized standard for accessibility requirements of ICT products and services. Published by ETSI, CEN, and CENELEC, its latest version (V3.2.1, 2021) incorporates WCAG 2.1 Level AA for web content (Clause 9) but extends beyond web to cover non-web documents (Clause 10), software (Clause 11), hardware (Clause 8), and ICT providing relay or emergency services (Clause 13). The European Accessibility Act (EAA, Directive 2019/882) requires EU member states to enforce accessibility for private sector products and services by June 28, 2025, using EN 301 549 as the presumption of conformity. This affects computers, smartphones, e-commerce, banking, transport, and e-books — making it arguably the world's most impactful accessibility regulation.
EN 301 549 is the harmonized European standard for ICT accessibility, serving as the technical backbone for the European Accessibility Act (EAA) and public procurement directives across all EU member states. It maps directly to WCAG 2.1 for web content while extending requirements to non-web software, hardware, documentation, and support services — making it broader in scope than any single national standard. Organizations selling digital products or services in the EU market must understand EN 301 549 because non-compliance can disqualify them from public tenders and, starting June 2025, expose them to enforcement actions under the EAA.
A German federal agency includes EN 301 549 conformance as a mandatory requirement in its procurement tender for a case management system, requiring vendors to submit a completed EU accessibility conformance report with their bid. Two of five vendors are disqualified because they cannot demonstrate conformance beyond basic WCAG web checks and have no documentation covering their desktop application components. The winning vendor's upfront investment in broad EN 301 549 testing becomes a direct competitive advantage.
An American SaaS company expanding into the EU market audits its platform against EN 301 549 eighteen months before the EAA enforcement date, discovering gaps in its mobile app's programmatic focus management and its PDF export's document structure. The early audit gives the team three release cycles to remediate issues, train support staff on accessibility requests, and publish an accessibility statement that references specific EN 301 549 clauses. By the enforcement deadline the company is compliant while competitors are scrambling.
A software vendor passes a WCAG 2.1 AA audit on its web application and assumes it meets EN 301 549 without reviewing clauses covering its native iOS app, its embedded hardware kiosk interface, or its PDF user documentation. When a French public sector client requests an EN 301 549 conformance report, the vendor discovers that its mobile app fails multiple Clause 11 requirements and its documentation is inaccessible. The gap costs six months of unplanned remediation and delays the contract signing.
• The most frequent mistake is treating EN 301 549 as identical to WCAG 2.1 — while the web content requirements align closely, the standard's coverage of non-web software (Clause 11), hardware (Clause 8), and documentation (Clause 12) introduces obligations that a web-only accessibility program will miss entirely. Teams also underestimate the documentation requirements: EN 301 549 expects accessibility features to be documented in product materials, and support services must be at least as accessible as the product itself. Another common error is waiting until a procurement request arrives to begin conformance work, leaving no time for the iterative testing and remediation that complex products require.
Was this article helpful?