Comparison
EU digital accessibility — public sector vs private sector
A side-by-side comparison of the two main EU regulatory tracks for digital accessibility — Directive 2016/2102 for public-sector bodies and Directive 2019/882 (the European Accessibility Act) for private-sector products and services.
The European Union operates two parallel digital accessibility regimes. One binds the public sector and was rolled out in the late 2010s. The other binds the private sector and became enforceable in 2025. They share a technical standard but diverge on scope, deadlines, monitoring, and enforcement.
Two regulatory tracks at a glance
Public sector — Directive 2016/2102
- Who it binds. Public-sector bodies of EU member states — central government, regional and local authorities, bodies governed by public law, and associations formed by them.
- What it covers. Websites and mobile applications of those bodies, including intranets where they apply.
- Technical standard. EN 301 549, which incorporates WCAG 2.1 Level AA as the baseline.
- Deadlines. Full conformance has been required since 23 September 2020 for new sites and 23 June 2021 for existing sites; mobile apps since 23 June 2021.
- Accessibility statement. Mandatory; standardised template; machine-readable feedback channel required.
- Monitoring. Periodic national audits with EU-wide reporting cycles.
Private sector — Directive 2019/882 (EAA)
- Who it binds. Manufacturers, importers, distributors, and service providers of in-scope consumer products and services placed on the EU market.
- What it covers. Consumer banking, e-commerce, e-books, ticketing, passenger transport interfaces, smartphones, computers, payment terminals, audiovisual media services, and more.
- Technical standard. EN 301 549 — same as the public-sector track for digital surfaces.
- Deadlines. Member-state transposition by 28 June 2022; applicability from 28 June 2025; some legacy services have a phase-out window until 2030.
- Accessibility declaration. Required from market participants; sector-specific information also required.
- Monitoring. Market-surveillance authorities at member-state level with the power to withdraw non-compliant products from the market.
Where they overlap
Both tracks reference EN 301 549 as the technical conformance standard, which folds WCAG into a wider set of requirements covering hardware, documentation, and support services. A team that achieves EN 301 549 conformance on a public website will largely satisfy the corresponding requirements for a private-sector equivalent — though product-specific provisions differ.
TODO (replace with your reporting): flesh out the cross-walk between the two tracks where teams routinely build under both — for example, a bank that runs both a public-information portal (Directive 2016/2102 via public-procurement rules) and consumer banking apps (EAA).
Where they diverge
| Dimension | Public sector (2016/2102) | Private sector (EAA, 2019/882) |
|---|---|---|
| Scope of entities | Public bodies, bodies governed by public law | Manufacturers, importers, distributors, service providers |
| Scope of surfaces | Websites, mobile apps, internal services | Consumer-facing products + services in defined sectors |
| Standard | EN 301 549 (WCAG 2.1 AA baseline) | EN 301 549 + product-specific provisions |
| Applicability date | From 2020 (new) / 2021 (existing) / 2021 (mobile) | From 28 June 2025 (some legacy services until 2030) |
| Accessibility artefact | Accessibility statement (standardised template) | Accessibility declaration + sectoral information |
| Enforcement | National monitoring bodies; reporting cycles to the Commission | Market-surveillance authorities; product withdrawal possible |
| Penalties | Set by member-state transposition; non-uniform | Set by member-state transposition; range €1k–€1M+ |
Source: skeleton draft. Replace with your verified survey across member states.
Reading guide
Pair this comparison with the country legislation hub for the member-state transpositions that turn these directives into local duties, and with the penalties hub for the financial ranges each member state has put on the books.
TODO (replace with your reporting): add a short “when does each apply?” decision tree — a finance app that serves the public sector through a procurement contract, a payment terminal at a public hospital, a private e-commerce site that takes student bookings, etc.