The European web accessibility directive, formally Directive (EU) 2016/2102, is EU legislation requiring public sector bodies across all member states to make their websites and mobile apps accessible to people with disabilities. Adopted in October 2016, it’s often referred to as the Web Accessibility Directive, or WAD. It was the EU’s first binding, harmonized accessibility rule for the public sector, aiming to give citizens with disabilities consistent, cross-border access to government services regardless of which member state hosted the site.

The directive is distinct from the European Accessibility Act (EAA), a separate and later piece of EU legislation that extends similar accessibility obligations to private businesses.

Who the directive applies to

The Web Accessibility Directive covers websites and mobile applications belonging to public sector bodies, including:

  • National, regional, and local government websites
  • Public healthcare and social service portals
  • Educational institution websites and platforms
  • Tax, benefits, and other administrative service systems
  • Public transportation and utility websites

Certain content is exempted, including heritage collection reproductions that can’t be made accessible without compromising preservation, intranet or extranet content published before September 23, 2019 (unless substantially updated since), and archived content no longer needed for active administrative processes.

The technical standard: EN 301 549 and WCAG 2.1 AA

The directive’s technical requirements are set out in EN 301 549, the European harmonized standard for ICT accessibility. For web content specifically, EN 301 549 incorporates WCAG 2.1 Level AA verbatim, meaning conformance with WCAG 2.1 AA is treated as conformance with the directive.

WCAG 2.2 was published by the W3C in October 2023, but its criteria don’t automatically become legally binding under the directive — new WCAG or EN 301 549 requirements only take legal effect once formally incorporated into a new harmonized version of EN 301 549 and cited in the EU’s Official Journal. A revised standard, EN 301 549 v4.1.1, incorporating WCAG 2.2, was published in September 2026, with Official Journal citation expected in November 2026 — at which point WCAG 2.2 AA is expected to become the operative benchmark for both the directive and the EAA.

The directive’s deadlines were staggered by content type:

  • September 23, 2019: Websites published on or after this date required immediate compliance
  • September 23, 2020: All existing public sector websites, regardless of publish date, were required to comply
  • June 23, 2021: Public sector mobile applications came into scope

By 2022, all deadlines had passed, meaning virtually every public sector website and app operating in the EU is expected to meet the standard today.

Ongoing obligations: accessibility statements and monitoring

Beyond initial compliance, the directive requires covered organizations to:

  • Publish and maintain a detailed, accessible accessibility statement for each website or app, disclosing compliance status and any known exceptions
  • Provide a feedback mechanism so users can report accessibility barriers and request inaccessible content in an alternative format
  • Submit to periodic monitoring by a body designated by each member state, which tests a sample of public sector websites and apps and reports results to the European Commission

The directive vs. the EAA

The Web Accessibility Directive and the EAA work together but cover different ground:

  • Scope: The directive applies only to public sector bodies. The EAA extends accessibility requirements to private businesses selling products and services — including e-commerce, banking, and transport ticketing — across the EU.
  • Technical standard: Both currently reference EN 301 549, meaning the same WCAG version transition affects both laws simultaneously.
  • History: The directive came first, in 2016; the EAA, formally Directive (EU) 2019/882, followed in 2019 and has been enforceable since June 2025.

How accessiBe’s platform supports EU public sector compliance

Meeting the directive’s requirements calls for a platform combining the best in AI automation, developer tools, and human expertise. accessWidget — accessiBe’s AI-powered accessibility interface — helps address common WCAG failure points like screen reader and keyboard navigation gaps on public-facing websites, while accessFlow gives development teams a way to track and resolve issues at the code level in line with WCAG 2.1 and 2.2 requirements. For the manual evaluation and documentation public sector bodies need to support a published accessibility statement, accessServices offers line-by-line audits against WCAG standards and conformance reporting built for organizations operating across multiple EU jurisdictions.