EU Web Accessibility Directive (Directive 2016/2102)

Article 4 imposes the substantive accessibility obligation: Member States shall ensure that public sector bodies take the necessary measures to make their websites and mobile applications more accessible by making them perceivable + operable + understandable + robust (the POUR principles). The POUR principles are operationalised through compliance with the W3C WCAG 2.x Conformance Level AA (currently WCAG 2.1 + transitioning to WCAG 2.2 as EN 301 549 v4.x is finalised). PERCEIVABLE - information + UI components must be presentable in ways users can perceive (text alternatives + captions + adaptable + distinguishable). OPERABLE - UI + navigation must be operable (keyboard accessible + enough time + seizures + navigable + input modalities). UNDERSTANDABLE - information + UI operation must be understandable (readable + predictable + input assistance). ROBUST - content must be robust enough

• WCAG 2.x AA conformance testing report (automated + manual)
• Assistive-technology compatibility test results (screen reader + voice control + keyboard-only)
• Issue-tracking + remediation evidence
• User testing with persons with disabilities

• Conformance based on automated testing only without manual + assistive-technology validation
• WCAG version + level not documented + reviewed against EN 301 549 v3.2.1 (or later) baseline
• No user testing with persons with disabilities

Article 7 imposes a triple obligation on public sector bodies for every covered website + mobile application. Article 7(1) ACCESSIBILITY STATEMENT - public sector bodies must provide + regularly update a detailed + comprehensive + clear accessibility statement on the compliance of their websites + mobile applications with this directive. The statement is published in an accessible format on the website (or for mobile apps - on the website of the entity offering the app + in the app store at download). The Commission has adopted the model accessibility statement (Implementing Decision (EU) 2018/1523) detailing minimum content: compliance status (fully + partially + non-compliant); non-compliant content + reasons + alternatives; date of statement preparation + review; feedback mechanism + enforcement procedure links. Article 7(1)(b) FEEDBACK MECHANISM - public sector bodies must put in pla

• Model-aligned (2018/1523) accessibility statement per covered website + app
• Feedback-mechanism + ticket / response evidence
• Enforcement-procedure link operational
• Annual review + republication

• Accessibility statement missing model elements (e.g. no review date / no alternatives / no enforcement link)
• Feedback mechanism not actually responding within a reasonable period
• Enforcement-procedure link broken or pointing to generic complaint page

Article 7(4) Member States shall take ADDITIONAL MEASURES to facilitate the application of the accessibility requirements + assist public sector bodies. These include: (a) the Commission may adopt implementing acts to determine in a model accessibility statement the structure of the statement; (b) Member States must facilitate training programmes for the relevant stakeholders on accessibility of websites + mobile applications including persons with disabilities; (c) Member States must take measures to raise awareness of the accessibility requirements + the social benefits + accessibility content provided. The Commission adopted Implementing Decision (EU) 2018/1523 establishing the model accessibility statement under Article 7(1) + (4). The European Commission + the Member State Web Accessibility Directive Expert Group (WADEX) publishes guidance + the Accessibility Statement Generator too

• Accessibility-training programme covering procurement + content authors + developers + testers
• Annual accessibility awareness campaign
• Tracking of EU Commission guidance + WADEX outputs
• Internal coordination with EAA private-sector accessibility (where the entity also offers private-sector products / services)

• No accessibility training programme for content authors + developers
• Awareness raising limited to International Day of Persons with Disabilities annual event
• No coordination between WAD (public-sector) and EAA (private-sector) requirements where the entity has dual scope

Article 5 establishes the DISPROPORTIONATE BURDEN exception. Member States may allow public sector bodies not to comply with the Article 4 accessibility requirements where compliance would impose a disproportionate burden on the public sector body, taking into account the relevant circumstances including: (a) the size + resources + nature of the public sector body concerned; (b) the estimated costs + benefits for the public sector body relative to the estimated benefits for persons with disabilities, taking into account the frequency + duration of use of the specific website or mobile application. Article 5(2) the public sector body must undertake and document an INITIAL ASSESSMENT of the extent to which compliance imposes a disproportionate burden. Article 5(3) the disproportionate burden invocation must be reviewed in light of any changes in the relevant circumstances + every 3 years.

• Documented Article 5(2) initial assessment per content / functionality
• Triennial review evidence
• Alternative-accessible-means documentation in the accessibility statement

• Article 5(4)(a)/(b) inadmissible grounds (priority + time + knowledge) cited as basis
• No triennial review of the disproportionate burden invocation
• No alternative-accessible-means documented in the accessibility statement

Article 14 establishes the COMMISSION REVIEW obligation. The Commission must publish a report on the application of this Directive by 23 June 2022 + every 5 years thereafter. The report shall consider: (a) the conclusions of the monitoring reports published by Member States under Article 8(4); (b) developments in the digital technology sector; (c) the desirability of any amendment to this Directive in particular in relation to: (i) flexibility regarding mobile applications; (ii) inclusion of websites or mobile applications of certain public service broadcasters; (iii) the possibility of extending the scope to include intranets + extranets + private-sector content; (iv) integration with the European Accessibility Act (EAA) following its application from 28 June 2025; (v) the role of certification + conformity-assessment bodies. The first Commission Article 14 report was published in 2022

• Tracking of the Commission Article 14 review (2022 + 2027 expected)
• Internal-readiness gap analysis for potential WAD amendments (private-sector extension + intranet / extranet integration + EAA dovetail + EN 301 549 v4.x)

• No tracking of the Commission Article 14 review outputs + recommendations
• Compliance program not anticipating possible private-sector extension

Article 8 imposes a periodic MONITORING + REPORTING obligation on Member States. Article 8(1) Member States shall PERIODICALLY MONITOR the compliance of websites + mobile applications of public sector bodies with the accessibility requirements set out in Article 4 + on the basis of the methodology established under Article 8(2). The Commission adopted Implementing Decision (EU) 2018/1524 establishing the monitoring methodology (in-depth, simplified, mobile sampling, the WAD monitoring methodology with frequency + scope + sampling). Article 8(4) Member States shall communicate to the Commission EVERY 3 YEARS a report on the results of the monitoring including measurement data. The first report covered December 2018 - December 2021 published in 2022; the second cycle covers 2022-2024 published 2025. Article 8(5) Member States must publish the report including making the data accessible. Ar

• National monitoring authority engagement records
• Triennial monitoring report submission to the Commission
• Internal awareness of the Member State monitoring sampling + remediation expectations
• Tracking of monitoring methodology reviews (every 5 years)

• Public sector body not aware of the national monitoring authority's selection methodology
• Internal monitoring not aligned with the Commission Implementing Decision 2018/1524 methodology
• No tracking of the Commission's 5-year monitoring-methodology reviews

Article 9 imposes the ENFORCEMENT PROCEDURE obligation on Member States to ensure that an adequate + effective enforcement procedure is available to ensure compliance with Articles 4 + 5 + 7 by public sector bodies. The procedure is the BACK-END to the Article 7(1)(c) front-end (the user-facing enforcement procedure link on the accessibility statement). Article 9(2) the enforcement procedure must include the possibility to contact an ombudsman or competent national authority to ensure the assessment of notifications + requests received under Article 7(1)(b) feedback mechanism + to monitor the assessment by public sector bodies. The specific national designation varies by Member State (commonly the national ombudsman + the data protection authority + sector-specific accessibility authority). The Article 9 procedure is the legal hook for individual complaints + collective redress + sectora

• Public sector body engagement records with the national enforcement authority
• Tracking of any Article 9 complaints or inquiries + their outcomes
• Internal documentation of the national enforcement procedure

• Public sector body unaware of its national enforcement authority
• Article 9 complaints not tracked + lessons-learned not internalised

Article 6 establishes the PRESUMPTION OF CONFORMITY regime. Article 6(1) the content of websites + mobile applications that meets the harmonised standards (or parts thereof) the references of which have been published by the European Commission in the OJEU in accordance with Regulation (EU) No 1025/2012 shall be presumed to comply with the accessibility requirements set out in Article 4 + that are covered by such standards or parts thereof. THE CURRENT HARMONISED STANDARD IS EN 301 549 (currently v3.2.1, with v4.x in development). Article 6(2) where no harmonised standards exist for specific accessibility requirements the Commission may adopt implementing acts setting out technical specifications meeting those requirements + ensuring presumption of conformity. Article 6(3) where no harmonised standards or technical specifications exist for specific accessibility requirements the content

• EN 301 549 (v3.2.1 or later) conformance report
• Cross-reference to specific EN 301 549 clauses for each accessibility issue
• Tracking of EN 301 549 evolution (v4.x WCAG 2.2 transition)

• Conformance asserted at WCAG level without EN 301 549 clause-by-clause mapping
• Failure to track EN 301 549 v4.x transition + WCAG 2.2 new criteria
• Equivalent-standard claim made under Article 6(3) without demonstrating equivalent accessibility level

Article 1(4) excludes specific categories from the directive's requirements: (a) websites and mobile applications of public service broadcasters and their subsidiaries; (b) websites and mobile applications of NGOs that do not provide services essential to the public OR services specifically addressing the needs of, or meant for persons with disabilities; (c) the following content of websites and mobile applications: (i) office file formats published before 23 September 2018, unless such content is needed for active administrative processes; (ii) pre-recorded time-based media published before 23 September 2020; (iii) live time-based media; (iv) online maps + online mapping services as long as essential information is provided in an accessible digital manner; (v) third-party content that is neither funded nor developed by, nor under the control of, the public sector body; (vi) reproduction

• Per-property exclusion analysis (which Article 1(4)(c) sub-exception applies + rationale)
• Heritage-collection accessibility assessment
• Decision log for intranet / extranet covered vs excluded

• Broad exclusion claimed without per-property analysis
• Online maps excluded without providing the essential information accessibly
• Heritage exception applied without demonstrating cannot-be-made-accessible analysis

Article 1 establishes the directive's purpose: to approximate the laws + regulations + administrative provisions of the Member States relating to the accessibility requirements of websites + mobile applications of public sector bodies. Article 2 sets the personal scope (Article 2(1) - applies to public sector bodies; Article 2(2) - applies to websites and mobile applications irrespective of the device used for access including via mobile devices). Article 3 (in Article 2 in the source structure) contains key definitions: (1) 'public sector body' = the State, regional or local authorities, bodies governed by public law as defined in Article 2(1)(4) of Directive 2014/24/EU + associations formed by them; (2) 'mobile application' = application software designed + developed by or on behalf of public sector bodies for use by the general public on mobile devices; (3) 'standard' = standard as de

• Internal scope memo identifying which entities qualify as 'public sector body' per Article 3(1)
• Inventory of covered websites + mobile applications + key categories of digital service (intranet / extranet covered or excluded)
• Coverage analysis for time-based media + electronic office file formats per Article 1(4)

• Public-sector body excluding intranet / extranet without Article 1(4)(g) careful analysis
• Mobile application not in scope analysis (per Article 2(2) directive applies irrespective of device)
• Format-coverage analysis missing leading to gaps for PDF / Word / Excel published content

Article 10 establishes the framework for exercise of delegation by the Commission. Article 11 sets the committee procedure (the Committee on the Accessibility of the Websites and Mobile Applications of Public Sector Bodies) which assists the Commission in adopting the implementing decisions including: (a) the model accessibility statement (Implementing Decision (EU) 2018/1523); (b) the monitoring methodology (Implementing Decision (EU) 2018/1524); (c) any technical specifications under Article 6(2). The Committee composition includes Member State representatives + persons with disabilities + civil society + the European Disability Forum + assistive technology vendors + standardisation bodies + the Commission. The Committee meets at least twice a year + publishes opinions + recommendations.

• Tracking of Commission Implementing Decisions affecting WAD compliance (2018/1523 + 2018/1524 + any future)
• Tracking of Committee opinions + recommendations

• Compliance program treating only the directive text without the implementing decisions
• No tracking of Committee outputs that may shape future amending implementing decisions

Article 12 transposition: Member States must transpose this directive by 23 September 2018. Article 13 STAGGERED APPLICATION DATES: the Article 4 + 5 + 7 + 8 accessibility requirements apply on staggered dates: (a) 23 September 2019 - for websites of public sector bodies published on or after 23 September 2018 (the 'new' websites); (b) 23 September 2020 - for all other public-sector websites (the 'pre-existing' websites); (c) 23 June 2021 - for mobile applications. The staggered timeline gave public sector bodies 1-4 years to achieve compliance. As of 2026-05-28 ALL three deadlines have long passed and full compliance is mandatory. Article 14 entry into force on the twentieth day following publication in the OJEU (22 December 2016). Article 15 addressees: the directive is addressed to the Member States.

• National transposition cross-reference
• Compliance evidence applicable to ALL three categories (new websites + pre-existing websites + mobile apps)

• Pre-existing-website compliance treated as voluntary or not yet achieved (it has been mandatory since 23 September 2020)
• Mobile app compliance overlooked (mandatory since 23 June 2021)

Article 15 entry into force on the twentieth day following publication in the OJEU. WAD was published in OJEU L 327 on 2 December 2016, so the entry into force date is 22 December 2016. Article 15 also confirms the directive is addressed to the Member States (recital). Future evolution: as of 2026-05-28 WAD is fully applied + Member States have completed at least 2 monitoring cycles (2018-2021 + 2022-2024). The Commission's planned consolidated 2026-2027 accessibility-framework communication may propose: (a) WAD amendments to consolidate with EAA; (b) extension of WAD to private-sector content under public-sector contract; (c) intranet + extranet inclusion; (d) certification-body conformity-assessment regime; (e) tighter Article 5 disproportionate-burden criteria. Future evolution includes the ongoing EN 301 549 v4.x transition aligning with WCAG 2.2 + Mobile Accessibility Project + ongo

• Tracking of the Commission's planned 2026-2027 accessibility-framework communication
• Internal-readiness gap analysis for potential WAD-EAA consolidation + WCAG 2.2 + AI-content accessibility

• No tracking of Commission accessibility-framework communications + amendments pipeline
• No readiness analysis for WCAG 2.2 new criteria (focus appearance + accessible authentication + dragging movements + target size)

The Web Accessibility Directive (WAD, 2016/2102) and the European Accessibility Act (EAA, 2019/882) form the EU's combined accessibility framework. WAD covers PUBLIC-SECTOR websites + mobile applications. EAA covers PRIVATE-SECTOR products + services (computers + operating systems + ATMs + ticketing + payment terminals + smartphones + e-readers + e-commerce + banking + transport ticketing + electronic communications + audiovisual media services + e-books). EAA applied from 28 June 2025 (Article 31 EAA) and uses the SAME EN 301 549 harmonised-standard reference as WAD. Entities that are BOTH public-sector AND offer private-sector products / services (e.g. a publicly-owned bank + a state-owned telecoms provider + a public broadcaster's commercial subsidiary) face DUAL compliance: WAD for public-sector websites + EAA for private-sector services. The cross-reference matters because: (a) the

• Dual-compliance gap analysis for entities subject to both WAD + EAA
• Single EN 301 549 conformance file serving both regimes
• Separate WAD + EAA accessibility statements / DoC

• Single accessibility-program treating WAD + EAA as substitutes
• No EN 301 549 conformance-file reuse leading to duplicate testing effort
• No tracking of EAA market-surveillance authority + WAD enforcement authority