What Is the EU Web Accessibility Directive? Requirements and Scope Explained

Overview of the EU Web Accessibility Directive

The EU Web Accessibility Directive (Directive (EU) 2016/2102) sets accessibility rules for public sector websites and mobile applications across EU member states. It requires public bodies to make their online services accessible, publish accessible statements, and provide a feedback route for users.

Who the directive applies to

The directive applies to public sector bodies listed in the directive’s annex. That includes central, regional and local government websites and many public undertakings that deliver public services. It does not directly create new obligations for private businesses outside the public sector, although national rules can differ.

Core requirements

Accessible content

Websites and mobile apps must be perceivable, operable, understandable and robust for people with disabilities. In practice this means following recognised technical standards and fixing barriers such as missing alternative text, poor keyboard support and inaccessible PDF files.

Accessibility statement

Public bodies must publish an accessibility statement for each website and mobile app. The statement must say whether the content meets the accessibility requirements, list parts that are not accessible, explain why, and describe how users can obtain content in an alternative format.

Feedback and complaint mechanism

Each accessibility statement must include a contact point where users can send feedback or complaints. Member states must set up procedures to handle these complaints and to monitor compliance.

Technical standards used to meet the directive

The directive references harmonised European standards and web content guidelines as technical references. Two widely used references are:

• EN 301 549 — the European standard that brings accessibility requirements into a technical form for procurement and testing.
• WCAG — web content accessibility guidelines. Many public bodies use WCAG 2.1 at level AA as the practical target when implementing the directive.

Key dates and timelines

Member states were required to transpose the directive into national law. The directive set target dates for web and app compliance. Websites were given an earlier deadline and mobile apps a later one. Member states also had to set up monitoring and reporting systems.

How enforcement and monitoring work

Enforcement is handled at national level. Each member state must appoint one or more bodies to monitor implementation and to take complaints from users. Sanctions and remedies vary between countries. The European Commission receives regular monitoring reports from member states.

What public sector bodies must do: a practical step-by-step checklist

1. Run an accessibility audit that covers webpages, documents and mobile apps.
2. Compare the audit results to EN 301 549 and WCAG 2.1 AA to identify failures.
3. Create or update an accessibility statement that lists non-compliant pages and planned fixes.
4. Set up a clear feedback channel and a process to handle and log complaints.
5. Prioritise fixes by user impact and update the statement with remediation dates.
6. Add accessibility clauses to procurement templates and train staff who publish content.
7. Schedule recurring audits and public reporting to the national monitoring body.

Sample headings for an accessibility statement

• Scope of this statement (which website or app it covers)
• Compliance status
• List of known accessibility problems
• Alternative ways to get content
• Contact point for feedback
• Revision and review date

Common mistakes to avoid (information gain)

Public bodies often make the same errors. These practical points are easy to miss but important.

• Treating PDFs and office documents as optional. Documents published online must be checked and fixed.
• Testing only with automated tools. Manual testing and keyboard and screen reader checks are essential.
• Forgetting mobile apps. Mobile app accessibility was given a later deadline but remains mandatory.
• Publishing a vague accessibility statement. The statement must name inaccessible content and say how to get alternatives.

What users can expect and do

Users should find an accessibility statement and a way to give feedback on a public body website or app. If a user is not satisfied with the reply, they can bring the issue to the national monitoring body that handles accessibility complaints.

How the directive fits with other EU rules

The directive is one part of the EU accessibility landscape. It sits alongside national accessibility laws and other EU acts that address accessibility of products and services. Public procurement and national regulations often reference the same technical standards used for this directive.

Final practical tips for compliance

• Keep the accessibility statement easy to find from every public-facing page.
• Document remediation work so monitoring bodies can review progress.
• Use EN 301 549 and WCAG 2.1 AA as your technical yardstick.
• Train content editors and procurement officers on accessibility requirements.

If you are responsible for a public website or app and need a starter checklist or a simple template for an accessibility statement, use the sample headings above and build a timeline for fixes that users can see.