EU Public Sector Web Accessibility

The Web Accessibility Directive (Directive 2016/2102) is the primary EU law governing public sector web accessibility. It requires websites and mobile applications of public sector bodies across all 27 member states to meet EN 301 549 — which incorporates WCAG 2.1 Level AA.

Key requirements and deadlines (all now passed):

• New websites: Compliant since September 23, 2019
• Existing websites: Compliant since September 23, 2020
• Mobile applications: Compliant since June 23, 2021
• Accessibility statements: Every public sector website must publish a detailed accessibility statement using the EU model template

The directive covers all public sector bodies: central government, regional and local authorities, public universities, hospitals, courts, police, and bodies governed by public law. The only exceptions are broadcasters and live-streaming content.

While the Web Accessibility Directive and the EAA are separate laws, they share the same technical standard (EN 301 549/WCAG 2.1 AA) and together create comprehensive digital accessibility coverage — the directive for the public sector, the EAA for the private sector.

Despite being legally required to comply since 2020, many EU government websites still fail basic accessibility checks. The European Commission's 2024 monitoring report found that only 37% of public sector websites fully met WCAG 2.1 AA. Common violations:

• PDF forms and documents not tagged: Government forms (tax returns, permit applications, benefit claims) published as untagged PDFs. Citizens using screen readers cannot complete or read them. WCAG 1.3.1 and 1.1.1 violations — and the single most reported issue
• Complex navigation menus without ARIA markup: Multi-level dropdown menus for department navigation that lack aria-expanded, aria-haspopup, and keyboard support. WCAG 2.1.1 and 4.1.2 violations
• Online forms without error identification: Tax filing, benefit application, and registration forms that show errors only visually (red borders) without programmatic error messages or suggestions. WCAG 3.3.1 (Error Identification) and 3.3.3 (Error Suggestion) violations
• Video content without captions: Council meetings, ministerial statements, and public consultation videos published without synchronized captions. WCAG 1.2.2 (Captions) violation
• Authentication barriers on digital ID systems: eIDAS-compliant login flows with time-limited steps that do not accommodate users who navigate slowly with assistive technology. WCAG 2.2.1 violation
• Tables used for layout: Government web pages using <table> elements for page layout instead of CSS, confusing screen readers about the content structure. WCAG 1.3.1 violation

The Web Accessibility Directive requires each member state to designate a monitoring body and enforcement mechanism. Enforcement varies significantly:

• Germany: The BFIT (Federal Monitoring Body for IT Accessibility) conducts simplified and in-depth monitoring. Citizens can file complaints through the federal arbitration body (Schlichtungsstelle). Non-compliance results in binding recommendations and public reporting
• France: DINUM manages the RGAA (accessibility framework). Public bodies must publish accessibility statements and improvement plans. Non-compliance results in fines up to €20,000 per service per year, increasing with continued failure
• Netherlands: The Accessibility Monitor publishes compliance scores for all government websites publicly. Named-and-shamed approach with improvement deadlines
• Ireland: The National Disability Authority monitors public sector websites and publishes annual compliance reports. Formal enforcement through ministerial direction

The European Commission reviews member state monitoring reports every three years. The 2024 review found significant gaps in enforcement — leading to EU-level pressure for stricter national enforcement. Citizens can also raise complaints through national ombudsmen and equality bodies.

Run a free CompliScan scan on your government website to identify WCAG 2.1 AA violations. Automated testing catches 30-40% of issues — critical for the simplified monitoring that EU member states conduct using automated tools.

Government-specific compliance workflow:

• Accessibility statement preparation: CompliScan results identify known non-compliance issues you must disclose in your mandatory accessibility statement, with specific WCAG criteria references
• PDF document audit: Flag untagged or improperly structured PDF forms and documents — the number-one government accessibility issue
• Form accessibility testing: Identify labeling, error handling, and keyboard navigation issues in citizen-facing forms (tax, benefits, permits, registrations)
• Ongoing monitoring: CompliScan Shield ($49/mo) provides weekly scans for 3 domains — meet monitoring body expectations with continuous compliance evidence

For government IT departments managing multiple departmental websites, the Agency plan ($299/mo) covers up to 50 domains with centralized reporting. Shield Pro ($149/mo) adds PDF reports you can attach to your accessibility statement as compliance documentation. Present these to monitoring bodies during audits to demonstrate proactive accessibility management.