The EU Web Accessibility Directive Explained

What the directive is and why it exists

The EU Web Accessibility Directive — formally Directive (EU) 2016/2102 — is legislation requiring public sector bodies across the European Union to make their websites and mobile apps accessible to people with disabilities.

It was adopted in October 2016 and required member states to transpose it into national law. Deadlines for compliance were staggered: public sector websites needed to comply from September 2020, and mobile applications from June 2021.

The directive addresses a specific problem: across Europe, roughly 80 million people live with some form of disability, and public services — government portals, health information, tax systems, educational platforms — were routinely inaccessible to them. Citizens with disabilities were being excluded from digital services they had both the legal right and practical need to use.

Who it covers

The directive applies to public sector bodies, defined broadly to include:

• National, regional, and local government departments and agencies
• Educational institutions funded by public bodies
• Public broadcasting organizations
• Public hospitals and healthcare services
• Libraries and cultural institutions
• Any other body established for the specific purpose of meeting needs in the general interest, not having an industrial or commercial character, and financed or controlled by a public body

It does not cover private sector organizations — that’s the domain of the European Accessibility Act, which came into force in 2025.

Non-EU public bodies that provide services to EU residents are not directly subject to the directive, though they may face its practical requirements through procurement obligations or partnership requirements.

What it requires

Technical standard: EN 301 549

The directive requires compliance with EN 301 549, the European harmonized standard for ICT accessibility. For websites and web applications, EN 301 549 references WCAG 2.1 Level AA as the technical benchmark.

This means public sector websites must meet the full set of WCAG 2.1 AA success criteria — covering perceivability (alt text, captions, contrast), operability (keyboard access, no time limits, no seizure risks), understandability (readable language, predictable navigation, error handling), and robustness (compatibility with assistive technologies).

Accessibility statement

Every covered website and mobile app must publish an accessibility statement containing:

• A declaration of the level of conformance achieved
• A list of known non-accessible content, with reasons for the exception
• A description of accessible alternatives where non-accessible content exists
• Contact information for users to report accessibility problems
• A link to the enforcement body where users can escalate unresolved complaints

Accessibility statements must be kept current. Publishing a statement and then ignoring it is not compliance — it’s documentation of failure.

Feedback mechanism

Users must be able to contact the organization to report accessibility barriers and request information in an accessible format. The organization must respond within a reasonable timeframe.

This feedback mechanism creates a direct channel between citizens and public bodies, and feeds into the complaint escalation process.

Disproportionate burden exception

The directive allows public bodies to claim a “disproportionate burden” exception — temporary relief from specific requirements where compliance would require resources or effort out of proportion to the benefit. However:

• The exception must be assessed case by case
• It must be documented in the accessibility statement
• It cannot be claimed for entire websites or apps — only for specific, identified barriers
• It must be reviewed periodically

The bar for claiming disproportionate burden is high, and national enforcement bodies have expressed skepticism about broad applications of the exception.

How it’s enforced

Member state monitoring

Each EU member state designates a monitoring body responsible for checking that public sector websites comply with the directive. The monitoring methodology was specified in an EU implementing decision: a mixture of automated testing and manual sample review.

Monitoring bodies are required to report to the European Commission every three years, summarizing the state of compliance across their public sector.

Complaint mechanisms

Citizens who encounter inaccessible public sector digital services can use the feedback mechanism to request remedy. If the public body doesn’t respond adequately within 12 weeks, the user can escalate to the designated enforcement body — which must investigate the complaint and take corrective action where violations are found.

Enforcement powers vary across member states. Some have issued formal notices and required specific remediations; others have been slower to use their enforcement authority actively. As the directive matures, enforcement pressure is increasing.

Consequences of non-compliance

Public sector bodies found in breach face formal corrective orders from enforcement bodies, public identification as non-compliant, and reputational consequences — particularly relevant for local authorities and government agencies whose accessibility performance is now publicly reported.

Unlike private sector enforcement under ADA or EAA, the directive doesn’t typically result in large financial penalties against public bodies (though national implementations vary). The primary sanction is reputational and the obligation to remediate.

What the directive means in practice

For public sector web teams, compliance with the directive means:

1. Conducting an accessibility audit against WCAG 2.1 AA — both automated and manual
2. Publishing an accurate accessibility statement that reflects current conformance, not aspirational compliance
3. Establishing a functioning feedback process — a real contact point, not a generic web form that goes unmonitored
4. Creating a remediation roadmap for known issues with realistic timelines
5. Integrating accessibility into ongoing development so new content and features maintain compliance

The common failure mode for public sector organizations is treating the directive as a documentation exercise: publish a statement, tick the box, move on. The monitoring data from member state reports consistently shows that many public sector websites are still significantly non-compliant despite years of the directive being in force.

If you manage a public sector digital service and haven’t tested your accessibility recently, a free automated scan gives you an immediate baseline. For the complete audit your accessibility statement needs to accurately reflect, talk to our team about a full review.