EU Web Accessibility Directive
Compliance Requirements and Standards
Understand what the EU Web Accessibility Directive requires, how it differs from the European Accessibility Act, and the technical standards, monitoring obligations, and enforcement mechanisms public sector bodies must follow.
The European Union is committed to improving digital access for the 87 million people with disabilities living in the region. The EU published Directive (EU) 2016/2102 of the European Parliament and of the Council of 26 October 2016 on the accessibility of the websites and mobile applications of public sector bodies—known as the EU Web Accessibility Directive—to standardize and harmonize the framework around web and mobile accessibility for public sector organizations.
This directive ensures that public sector websites and mobile apps across all EU member states meet consistent accessibility standards, enabling cross-border access to government services for all citizens.
EU Web Accessibility Directive Overview
The EU Web Accessibility Directive establishes binding accessibility requirements for public sector digital properties. Each member state must transpose the directive into national law, creating country-specific legislation that enforces the harmonised standard.
Key Dates and Transposition
- October 2016 — Directive published
- September 2018 — Deadline for member state transposition into national law
- September 2019 — Compliance deadline for new public sector websites
- September 2020 — Compliance deadline for existing websites
- June 2021 — Compliance deadline for mobile applications
The directive is available on EUR-Lex, the official database of EU law, where organizations can access the full legal text and related implementing decisions.
Who Must Comply?
The EU Web Accessibility Directive applies to public sector bodies, including:
- State, regional, or local authorities
- Bodies governed by public law
- Associations formed by one or more such authorities or bodies governed by public law, if established to meet needs in the general interest (not having an industrial or commercial character)
Encouraged Private Sector Application
The directive encourages member states to extend its application to private bodies that provide public services, such as:
- Healthcare providers
- Childcare services
- Social inclusion organizations
- Transport services
- Utilities (electricity, gas, heat, water)
- Electronic communications and telecommunications
- Postal services
Exclusions
Public service broadcasters and non-governmental organizations that do not provide services essential to the public or specifically for people with disabilities are excluded from this directive.
EU Web Accessibility Directive vs. European Accessibility Act
A common point of confusion: the EU Web Accessibility Directive and the European Accessibility Act (EAA) are separate pieces of legislation with different scopes.
EU Web Accessibility Directive (2016)
- Scope: Public sector websites and mobile applications only
- Applies to: Government agencies, public bodies, and publicly-funded organizations
- Technical standard: EN 301 549 (incorporating WCAG 2.1)
- Enforcement: Member state monitoring and reporting to European Commission
European Accessibility Act (2019, enforced 2025)
- Scope: Specific products and services across public AND private sectors
- Applies to: E-commerce, banking, e-books, telecommunications, transport, consumer-facing digital services
- Technical standard: EN 301 549 (incorporating WCAG 2.1, moving to 2.2)
- Enforcement: National market surveillance with penalties up to €100,000 or 4% annual revenue
Key Differences
The EU Web Accessibility Directive focuses exclusively on public sector digital accessibility, while the EAA extends requirements to private sector products and services. Organizations serving EU markets may need to comply with both—the directive for any public sector work and the EAA for consumer-facing commercial offerings.
For EAA compliance specifically, see our dedicated European Accessibility Act guide.
Technical Standards: EN 301 549 and WCAG
The EU Web Accessibility Directive uses the European harmonised standard EN 301 549. This technical standard has adopted the Web Content Accessibility Guidelines (WCAG) 2.1, covering accessibility for web content, electronic documents, and non-web software such as native mobile apps.
Current and Future Standards
EN 301 549 covers conformance to WCAG 2.1 Level A and AA, but not Level AAA—enabling more seamless harmonisation with other procurement standards. The next version of EN 301 549 (v4.1.1), expected in 2026, is planned to incorporate WCAG 2.2.
Web authors and procurement accessibility specialists are still encouraged to improve and extend accessibility beyond the outlined standards where applicable.
The Four Principles of Accessibility (POUR)
EN 301 549 follows WCAG 2.1's four principles:
Perceivable — Information and user interface components must be presented in ways users can perceive clearly. This includes text alternatives, captions, and sufficient contrast.
Operable — Functionality and navigation must be usable by all. This includes keyboard accessibility, sufficient time, and seizure prevention.
Understandable — Information and operation must be easily understood by people of differing abilities. This includes readable text and predictable behavior.
Robust — Content must be reliably interpreted across assistive technologies and adapt to new user agents. This requires valid code and proper implementation.
What Is the Difference Between EAA and WCAG?
WCAG is a technical standard developed by the W3C that defines how to make web content accessible. The EAA is EU legislation that requires certain products and services to be accessible—and references EN 301 549 (which incorporates WCAG) as the technical standard for compliance.
In short: WCAG tells you how to be accessible; the EAA tells you that you must be accessible and creates legal consequences for non-compliance.
Content Covered by the Directive
For public sector websites and mobile applications, covered content includes:
- Non-textual information (images, graphics, charts)
- Downloadable documents (PDFs, Word files, spreadsheets)
- Forms and interactive elements
- Two-way interaction including digital forms, authentication, identification, and payment processes
Content Exemptions
The directive does not apply to:
- Office file formats published before 23 September 2018
- Pre-recorded time-based media published before 23 September 2020
- Live time-based media (live streams, broadcasts)
- Online maps and mapping services (though essential navigational information must be accessible)
- Third-party content not funded, developed, or controlled by the public sector body
- Heritage collection reproductions that cannot be made accessible without affecting preservation or authenticity
- Intranet/extranet content published before 23 September 2019 (unless significantly updated)
- Archived content not needed for active administrative processes and not updated after 23 September 2019
Accessibility Compliance Requirements
To comply with the EU Web Accessibility Directive, public sector bodies must fulfill three core obligations:
1. Accessibility Statement
Public sector bodies must publish an accessibility statement that includes:
- Explanation of any non-accessible content and reasons why
- Description of accessible alternatives available
- Feedback mechanism for users to report accessibility issues
- Contact information for accessibility requests
- Date of last accessibility review
- Link to enforcement procedure
Users have the right to escalate complaints through an enforcement procedure if their feedback is ignored or inadequately addressed.
2. Monitoring
Member states must monitor conformance using a methodology that includes:
- Periodicity of monitoring and website sampling arrangements
- Sampling of web pages, page content, and mobile app content
- Description of compliance determination methods
- Mechanism to help public sector bodies correct deficiencies
- Arrangements for automated, manual, and usability testing
3. Reporting
Member states must submit accessibility progress reports to the European Commission every three years. Reports covering 2020–2021 and 2022–2024 have been published. Reports must include:
- Results of monitoring activities
- Mechanisms for stakeholder consultation on accessibility
- Procedures for publicizing accessibility policy developments
- Implementation findings and experiences
- Information on training and awareness-raising activities
Disproportionate Burden Exemption
Public sector bodies may claim a "disproportionate burden" exemption for specific accessibility requirements if compliance would impose excessive organizational burden. However, this exemption requires:
- Documented assessment of the burden
- Explanation of which requirements cannot be met and why
- Description of accessible alternatives provided
- Regular reassessment as circumstances change
The disproportionate burden claim must be included in the accessibility statement and cannot be used as a blanket exemption for entire websites or applications.
Enforcement and Penalties
There are no EU-wide penalties for non-compliance. Each member state sets its own penalties through national law for failing to conform with the directive.
Country-Specific Implementations
Member states have implemented the directive through various national frameworks:
- France: RGAA (Référentiel Général d'Amélioration de l'Accessibilité) provides detailed technical requirements
- Germany: BITV 2.0 (Barrierefreie-Informationstechnik-Verordnung)
- UK: Public Sector Bodies Accessibility Regulations 2018 (though now outside EU, similar requirements apply)
Organizations operating across multiple member states should understand country-specific requirements while maintaining baseline EN 301 549 compliance.
How Acquia Can Help
Acquia Web Governance's Web Accessibility Module audits your entire site for digital accessibility against WCAG 2.1 and 2.2 success criteria (and subsequent updates to the guidelines).
Each audit scans your site for machine-testable issues, provides detailed reports for reviewing errors, gives targeted recommendations based on the guidelines, and shows compliance status across Levels A, AA, and AAA. Track and prove your accessibility compliance progress via reports in the History Center.
We also offer accessibility training to ensure your team is well-versed in both automated and manual remediation methods.
Acquia provides free tools to complement your accessibility efforts:
- Color Contrast Checker — Test compliant color combinations for web design
- Accessibility Statement Generator — Meet EU Web Accessibility Directive requirements by producing a public statement declaring your commitment to web accessibility
| Is WCAG a Legal Requirement in the US? |
|---|
|
In the US, WCAG is not directly codified in law for private businesses, but it serves as the benchmark for accessibility litigation under the ADA (Americans with Disabilities Act). For federal agencies, Section 508 of the Rehabilitation Act requires WCAG 2.0 Level AA compliance. State and local governments must meet WCAG 2.1 Level AA under new ADA Title II regulations by April 2026/2027.
|
| Is There an ADA Equivalent in Europe? |
|---|
|
The European Accessibility Act (EAA) is the closest equivalent to the ADA's broad civil rights approach, covering both public and private sectors. The EU Web Accessibility Directive specifically addresses public sector digital accessibility, similar to how Section 508 addresses US federal agencies.
|
| Is WCAG Mandatory in the EU? |
|---|
|
Yes, for public sector bodies. The EU Web Accessibility Directive requires compliance with EN 301 549, which incorporates WCAG 2.1 Level A and AA. The EAA extends WCAG-based requirements to specified private sector products and services.
|
Disclaimer
The information in this article is provided by Acquia Inc. and/or its subsidiaries and affiliates for informational purposes only, offering a general understanding of current legal developments. It should not be construed as specific legal advice, and no attorney-client relationship exists between you and Acquia Inc. This article should not be used as a substitute for competent legal advice from a licensed attorney in your jurisdiction.
An Accessible Vision
Accessibility expert Yahya Sayid discusses the importance of building inclusive digital experiences.