Skip to main content

Web accessibility laws in Ireland: the Directive and the EAA

Published · Updated

If you run a private business, the Web Accessibility Directive almost certainly isn’t your law. It’s for public bodies. The law that might apply to you is the European Accessibility Act, and this guide shows you how to tell.

It’s easy to mix them up. Search for web accessibility laws in Ireland and you’ll often land on the National Disability Authority’s pages about public-sector websites. Those pages are about the Directive, not the Act.

The short answer

  • The Web Accessibility Directive covers public bodies: government departments, councils, the HSE and similar. It doesn’t cover private businesses.
  • The European Accessibility Act covers certain services, including selling online. If customers can buy from you, or book and pay, on your website, it likely applies to you.
  • Microenterprises providing services are exempt from the Act. That means fewer than 10 people, and turnover or balance sheet of €2 million or less. Most cafés, B&Bs and small shops are likely to be microenterprises.
  • If neither applies, Irish equality law still expects you to make reasonable changes for disabled customers.

The two laws, in plain words

The EU Web Accessibility Directive is Directive 2016/2102. Ireland brought it in with S.I. No. 358/2020, the European Union (Accessibility of Websites and Mobile Applications of Public Sector Bodies) Regulations 2020. We’ll call them the public-sector rules.

The European Accessibility Act is Directive 2019/882. Ireland brought it in with S.I. No. 636/2023. We’ll call them the EAA rules.

All three are online in full: the public-sector rules (S.I. No. 358/2020), the Web Accessibility Directive (Directive 2016/2102) and the EAA rules (S.I. No. 636/2023).

People sometimes shorten these to WAD vs EAA. The table below sets them side by side.

Side by side

QuestionWeb Accessibility Directive (S.I. No. 358/2020)European Accessibility Act (S.I. No. 636/2023)
Who it applies toPublic bodies: the State, councils and other bodies run for the public good with public money or oversight (Reg 2). Not public service broadcasters, and not most charities (Reg 3(2))Businesses providing certain services to consumers (Reg 3(2)). Microenterprises providing services are exempt (Reg 5(4))
What it coversWebsites and mobile apps (Reg 3(1)), with some content left out (Reg 3(3))Specific products and services, including e-commerce (Reg 2, Reg 3), with some content left out (Reg 3(4))
Since whenWebsites by 23 September 2020, apps from 23 June 2021 (Reg 3(1))28 June 2025 (Reg 1, Reg 3)
The standardEN 301 549 v3.2.1, which uses WCAG 2.1 AA (Reg 5)None cited yet. EN 301 549 v4.1.1 (WCAG 2.2 AA) was published on 2 September 2026 (Reg 16 applies once one is cited)
Accessibility statementRequired, using the EU model statement (Reg 7)Required, in writing and orally, with no EU template (Reg 14, Schedule 3)
Who checksThe National Disability Authority (NDA) monitors (Reg 8)The CCPC and five sector regulators (Reg 4). The NDA advises them (Reg 4(4))
If you don’t complyNo offences or fines. Complaints go through the Equal Status Act 2000 and the Disability Act 2005 (Reg 7(4))Warnings, directions and court orders (Regs 27 to 30), and offences with fines (Reg 32)

The rest of this guide goes through each row.

The Web Accessibility Directive: what public bodies have to do

Who’s covered

The public-sector rules cover “public sector bodies” (Regulation 2 of S.I. No. 358/2020). That means the State, regional and local authorities, and bodies governed by public law.

A body governed by public law is one set up to meet needs in the general interest, not to run a business. It is also mostly funded, supervised or appointed by the State (Regulation 2).

Two groups are left out (Regulation 3(2)). Public service broadcasters are one. The other is charities and other non-governmental organisations, unless they provide services that are essential to the public, or services for disabled people.

What they have to do

Public bodies have had to meet the rules for their websites since 23 September 2020 at the latest (Regulation 3(1)(b)). Mobile apps followed on 23 June 2021 (Regulation 3(1)(c)). Some content is left out, such as old PDFs, live video and archives (Regulation 3(3)).

Their websites and apps must be “perceivable, operable, understandable and robust” (Regulation 4). Those are the same four principles as WCAG, the international guidelines for accessible websites.

A site that meets the harmonised standard is presumed to meet those requirements (Regulation 5). A harmonised standard is one the EU has formally named. Here that’s EN 301 549 v3.2.1, which uses WCAG 2.1 AA, under Decision 2021/1339.

Disproportionate burden

A public body can skip a requirement if it would be a disproportionate burden, meaning too costly or hard for that body (Regulation 6). But it has to do an assessment first. Then it has to explain in its accessibility statement what it couldn’t do, and offer another way where it can.

The accessibility statement

Every public body needs an accessibility statement for each website and app (Regulation 7). It must:

  • be in an accessible format
  • use the EU’s model accessibility statement (Decision 2018/1523)
  • be published on the website
  • say what isn’t accessible, and why
  • describe and link to a way for people to report a problem or ask for content
  • link to the complaint routes under the Equal Status Act 2000 and the Disability Act 2005

When someone reports a problem, the body has to give an adequate response within a reasonable time (Regulation 7(5)).

Who checks, and what happens

The National Disability Authority checks public-sector websites and apps (Regulation 8). It uses an EU method for this, set out in Decision 2018/1524, and reports to the Minister every three years.

The NDA’s own pages explain what the requirements are and how it checks public bodies.

There are no offences or fines in S.I. No. 358/2020. That’s the key difference from the EAA. If someone can’t use a public body’s website, they complain through the Equal Status Act 2000 or the Disability Act 2005.

The European Accessibility Act: what covered businesses have to do

Who’s covered

The EAA rules cover a list of products and services from 28 June 2025 (Regulation 3 of S.I. No. 636/2023). The one most businesses care about is e-commerce: selling to consumers through a website or app (Regulation 2).

If customers can buy from you, or book and pay, on your website, the rules likely apply to you. A brochure website with your phone number probably doesn’t count. It depends on the facts of your business.

Microenterprises providing services are exempt (Regulation 5(4)). That’s fewer than 10 people, and turnover or balance sheet of €2 million or less. Our guide to the microenterprise exemption helps you check.

What a covered website has to do

It has to meet the same four principles: perceivable, operable, understandable and robust. You also have to publish information on how your service meets the rules, in writing and orally (Regulation 14 and Schedule 3). There’s no EU model statement for this one. Our guide to accessibility statements has a template.

No harmonised standard has been cited under the EAA yet. EN 301 549 v4.1.1, which uses WCAG 2.2 AA, was published on 2 September 2026. Its citation is expected around the end of November 2026. Most businesses work to WCAG 2.1 AA for now. Our explainer on EN 301 549 and WCAG covers where that stands.

Disproportionate burden

The EAA rules have their own version of this (Regulation 15). A requirement doesn’t apply if meeting it would fundamentally change your service, or be a disproportionate burden. But you have to do an assessment first, using the criteria in Schedule 4.

Unless you’re a microenterprise, you have to keep a written record of it for 5 years and tell the regulator you’re relying on it (Regulation 15(4) and (9)). Not doing either is an offence (Regulation 32(1)).

Who checks, and what happens

The CCPC checks online shops (Regulation 4). Five other regulators check banking, phone and internet, TV, air travel, and bus, rail and ferry services. The NDA advises them but doesn’t enforce (Regulation 4(4)).

Unlike the public-sector rules, the EAA rules have teeth:

  • A regulator has to write to you and give you 14 days to respond before giving you a direction, which is a formal order to fix something (Regulation 27). You can appeal to the District Court (Regulation 28).
  • A regulator, or a customer, can ask the Circuit Court for an order making you comply (Regulations 29 and 30).
  • On summary conviction, the penalty is a class A fine (up to €5,000) or up to 6 months in prison, or both. On indictment, it’s up to €60,000 or up to 18 months, or both (Regulation 32(6)).

Our guide to EAA penalties in Ireland takes you through each step. The CCPC also has a clear page on what the Act means for businesses.

Where they overlap

Some public bodies provide services the EAA covers. Public transport is the clearest case.

The EAA rules cover bus, rail and ferry websites, apps and e-tickets (Regulation 3(2)(c)). The National Transport Authority checks those services (Regulation 4(2)(d)). So a public body selling tickets online is likely under both laws: the public-sector rules for its website as a whole, and the EAA rules for the ticketing service.

If that’s you, check with the NDA and the relevant regulator, as each law has its own statement rules.

If neither applies

Being outside both laws doesn’t mean disability law stops at your door.

Under section 4 of the Equal Status Act 2000, a service provider must do all that’s reasonable to meet the needs of a person with a disability, if without that they couldn’t use the service or it would be unduly difficult. A provider doesn’t have to if it would cost more than a nominal amount.

That law is about your service as a whole, not your website in particular. A fair example: someone can’t use your online booking. Offering another way to book, by phone or email, is the kind of thing that law expects.

Accessibility statements: public bodies vs businesses

The NDA’s automated checks use axe-core, the same testing engine as our free scan.

In its 2025 monitoring report, the NDA looked closely at 22 public-sector websites. Six of them (27%) had no accessibility statement. Only one had a statement that met all the requirements.

Businesses have a long way to go. In our study of Irish business websites, only 4% of 6,576 linked to an accessibility statement from their homepage.

The two figures aren’t measured the same way. The NDA checked a small sample of sites by hand. We checked homepages only, with automated tools, and only counted statements linked from the homepage. But the gap is wide. Public bodies have had a statement rule since 2020. For most businesses, it’s new.

What to do next

  1. Work out whether the EAA applies to you. Start with our guide to the microenterprise exemption.
  2. Check your website. Run our free scan to see what fails on your website. Automated checks find roughly a third of problems, so it’s a starting point.
  3. Publish an accessibility statement if you’re covered. Our accessibility statement template follows the EAA rules, not the public-sector model.

This isn’t legal advice. For exactly how the rules apply to your business, talk to a solicitor or the relevant regulator.

Check your own website for free

We'll scan your homepage and a few key pages and email you a plain-English report in minutes.

Free Report by email in minutes Privacy