language: en · status: in-force · last checked: 2026-09-06

Web Accessibility Directive (Directive (EU) 2016/2102)

The EU's accessibility law for the public sector's own digital estate, published in the Official Journal on 2 December 2016 (OJ L 327, 2.12.2016, p. 1) and in force since 22 December 2016 (the twentieth day after publication, Art. 14). It requires Member States to ensure that websites and mobile applications of public sector bodies are accessible — "perceivable, operable, understandable and robust" (Art. 4) — with a published accessibility statement (Art. 7), national monitoring (Art. 8) and an enforcement procedure (Art. 9). Transposition was due 23 September 2018; it has applied to all in-scope websites since 23 September 2020 and to mobile applications since 23 June 2021 (Art. 12(3)). The Directive is unamended (Cellar lists no amending act; the only consolidated edition is the initial 2016-12-02 one).

The Directive binds public sector bodies, not their suppliers — but its requirements reach vendors through procurement: the harmonised standard that gives a presumption of conformity, EN 301 549, is what public-sector customers put in tender specifications and contracts.

Applicability to EdTech

State schools are public sector bodies. "Public sector body" covers the State, regional or local authorities and bodies governed by public law (Art. 3(1)), which is how publicly maintained schools and the authorities that run them fall in scope. A vendor's portal or app procured by a school is not automatically the school's "website", but content and functions the school offers through third parties remain the school's problem unless the third-party-content exclusion applies (Art. 1(4)(e)) — so accessibility conformance flows into procurement requirements.
The school carve-out is narrow and optional. Member States may exclude websites and mobile applications of schools, kindergartens or nurseries — "except for the content thereof relating to essential online administrative functions" (Art. 1(5)). Whether a given market uses the option is a matter of national transposition; do not assume school-facing products are out of scope.
EN 301 549 is the operative technical bar. Content meeting harmonised standards listed in the OJ is presumed conformant (Art. 6(1)). The listed standard is EN 301 549 (see Sources); for web content its clauses 9.1–9.4 correspond to WCAG 2.1: "Conformance with W3C Web Content Accessibility Guidelines (WCAG 2.1) […] Level AA is equivalent to conforming with all of clauses 9.1 to 9.4 and the conformance requirements of clause 9.6 of the present document" (EN 301 549 V3.2.1, Introduction). In practice, WCAG 2.1 AA is what school customers ask suppliers to evidence.
Exclusions matter for content libraries: pre-recorded time-based media published before 23 September 2020 and live time-based media are excluded (Art. 1(4)(b)–(c)), as are pre-2018 office file formats not needed for active administrative processes (Art. 1(4)(a)).
The accessibility statement is where suppliers surface. Public sector bodies must publish and maintain a detailed statement, including an explanation of any parts that are inaccessible and accessible alternatives (Art. 7(1)); a disproportionate-burden derogation must be explained there too (Art. 5(4)). Schools relying on a vendor's product need the vendor's conformance information to write it.

Document	Covers
SCOPE-AND-DEFINITIONS.md	Arts. 1–3 — subject matter, scope and exclusions (incl. the school carve-out), definitions
ACCESSIBILITY-REQUIREMENTS.md	Arts. 4–6 — the accessibility duty, disproportionate burden, presumption of conformity
STATEMENT-MONITORING-ENFORCEMENT.md	Arts. 7–9 — accessibility statement, monitoring and reporting, enforcement procedure
IMPLEMENTATION-AND-REVIEW.md	Arts. 10–15 — delegation, committee, transposition and application dates, review

Key obligations at a glance

Websites and mobile applications of public sector bodies must be perceivable, operable, understandable and robust (Art. 4).
Compliance is required only to the extent it does not impose a disproportionate burden; the assessment is the body's and must weigh size/resources against benefits for persons with disabilities (Art. 5(1)–(3)); reliance on the derogation must be explained in the accessibility statement with accessible alternatives where appropriate (Art. 5(4)).
Content meeting the OJ-listed harmonised standard (EN 301 549) is presumed conformant (Art. 6(1)).
A detailed, regularly updated accessibility statement with a feedback mechanism, and an "adequate response to the notification or request within a reasonable period of time" (Art. 7(1)).
Application dates: new websites from 23 September 2019, all websites from 23 September 2020, mobile applications from 23 June 2021 (Art. 12(3)).

Enforcement

There is no EU-level enforcer or fine regime: Member States monitor compliance periodically using the Commission's methodology (Art. 8(1), Implementing Decision (EU) 2018/1524), report to the Commission every three years (Art. 8(4)), and must provide "an adequate and effective enforcement procedure" — such as recourse to an ombudsman — covering the Art. 4/5 requirements and the Art. 7(1) statement (Art. 9(1)). Remedies and any penalties are therefore national-law questions in each Member State's transposition.

European Accessibility Act — the private-sector companion: the WAD binds schools' own websites/apps, the EAA binds products and services vendors place on the consumer market; both converge on EN 301 549.
EU AI Act and EU GDPR — the other EU-wide instruments in this corpus that reach EdTech through what public-sector schools may procure and deploy.

Web Accessibility Directive (Directive (EU) 2016/2102)

Applicability to EdTech

Contents

Key obligations at a glance

Enforcement

Sources

Meta

Web Accessibility Directive (Directive (EU) 2016/2102)

Applicability to EdTech

Contents

Key obligations at a glance

Enforcement

Related

Sources

Meta