Web Accessibility Directive

The Web Accessibility Directive requires EU public sector bodies to make their websites and mobile apps accessible and publish accessibility statements.

What is the Web Accessibility Directive?

The Web Accessibility Directive (Directive 2016/2102) is an EU law that requires all public sector bodies to make their websites and mobile apps accessible to people with disabilities. It also requires each body to publish an accessibility statement. The directive ensures that citizens across the EU have equal access to government information and services online.^[1]

Who must follow this directive?

The directive applies to public sector bodies — any organization established under public law and funded mainly by public money. This includes:

Central, regional, and local government
Courts and justice systems
Public universities and schools
Public hospitals and healthcare providers
Publicly funded cultural institutions

Private companies are not covered by this directive. However, they may fall under the European Accessibility Act from June 2025.

What are the deadlines?

All deadlines have passed:

New public sector websites (published after 23 September 2018): required to comply from September 2019
Existing public sector websites: required to comply from September 2020
Mobile applications: required to comply from June 2021

Every EU public sector body is now legally required to meet these rules.

What is the technical standard?

The directive requires conformance with EN 301 549, the harmonized European standard. For websites, EN 301 549 points to WCAG 2.1 Level AA. Meeting WCAG 2.1 AA means meeting the directive's technical requirements.^[3]

IT teams should use WCAG 2.1 AA as their testing benchmark. Content teams should follow the standard's rules on headings, images, forms, and document structure.

What content is exempt?

Some types of content are outside the directive's scope:

Broadcasting content (live or on-demand video from broadcasters)
Office files published before September 2018, unless needed for active processes
Pre-recorded audio and video published before September 2020
Online maps, if essential navigation info is available accessibly elsewhere
Third-party content the organization did not fund or control
Cultural heritage items where accessibility would destroy the original character
Intranet sites published before September 2019, until they are significantly redesigned^[2]

What must the accessibility statement include?

Each website and mobile app needs its own public accessibility statement. The statement must cover:

Whether the site fully meets, partly meets, or does not meet WCAG 2.1 AA
A list of known accessibility issues and the reasons for each
The date the statement was prepared and last reviewed
A feedback form or email for users to report problems
Contact details for the national enforcement authority

The European Commission published a model template to help organizations write their statements. National monitoring bodies check a sample of these statements for accuracy on a regular schedule.^[2]

How is compliance monitored?

Each member state has a monitoring body that checks public sector websites and reports to the European Commission every three years. The monitoring method combines automated scans and manual testing.

Citizens can report accessibility failures directly to the public body. If the response is unsatisfactory, they can escalate to the national enforcement authority. Penalties depend on each country's national law.

How does this directive relate to the EAA?

The Web Accessibility Directive and the European Accessibility Act are separate laws that work in parallel:

Web Accessibility Directive — covers public sector
European Accessibility Act — covers private sector (from June 2025)

Both use EN 301 549 as their technical standard. Organizations that supply digital services to both government and commercial clients — such as SaaS platforms used by public hospitals or universities — may need to comply with both.^[1]

How Askem Helps

Public sector bodies under the Web Accessibility Directive must maintain WCAG 2.1 AA compliance and publish an accurate accessibility statement. Continuous monitoring tools help IT and communications teams stay current instead of relying on an accessibility audit that may be months out of date. Tools like Askem detect new issues and send real-time alerts, so teams can update their accessibility statement before the national monitoring body reviews it. For large public organizations with multiple websites — government agencies, universities, hospital networks — centralized monitoring across all domains keeps compliance manageable.

Sources

EUR-Lex — Directive (EU) 2016/2102 on the accessibility of websites and mobile applications of public sector bodies: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32016L2102
European Commission — Web Accessibility Directive overview and model statement: https://digital-strategy.ec.europa.eu/en/policies/web-accessibility
ETSI — EN 301 549 V3.2.1 Accessibility requirements for ICT products and services: https://www.etsi.org/deliver/etsi_en/301500_302000/301549/03.02.01_60/en_301549v030201p.pdf