EN 301 549 vs WCAG: which accessibility standard applies in Ireland now
Published · Updated
EN 301 549 vs WCAG comes down to this: WCAG is the set of guidelines for accessible websites, and EN 301 549 is the European accessibility standard that points to it. Right now, EN 301 549 points to WCAG 2.1 AA, and a newer version based on WCAG 2.2 AA has been published.
Read anything about the European Accessibility Act and you’ll see two versions of the same rulebook: WCAG 2.1 and WCAG 2.2. And a third name, EN 301 549. That’s the standard EU law cites, for now only under the Web Accessibility Directive for public sector websites. Nothing is cited under the European Accessibility Act yet. This guide explains where EN 301 549 and WCAG 2.2 stand right now, and what it means for your website.
The short answer
Right now, everyone works to WCAG 2.1 AA, through EN 301 549 v3.2.1. A new version based on WCAG 2.2 AA has been published. It’s expected to be formally cited under the European Accessibility Act around the end of November 2026.
So fix the WCAG 2.1 basics first. Build anything new to WCAG 2.2.
What WCAG is
WCAG stands for Web Content Accessibility Guidelines. It’s the set of guidelines for accessible websites published by the W3C, the body that sets standards for the web.
Version 2.2 came out in October 2023. It builds on 2.1. Everything in 2.1 is still there, apart from one removed check, and there are a handful of new ones.
Each guideline has a level: A, AA or AAA. When laws and standards refer to WCAG, they mean levels A and AA together.
What EN 301 549 is, and why it matters
EN 301 549 is the European accessibility standard. For websites, it points to WCAG.
In Irish law, the European Accessibility Act is brought in by S.I. No. 636/2023. Regulation 16 covers harmonised standards that are cited in the Official Journal of the EU. If a product or service meets one, it’s presumed to meet the accessibility requirements that standard covers.
In plain terms: once a version is cited under the Act, meeting it means you’re presumed to meet the rules. That’s why the citation matters.
Where things stand
- EN 301 549 v3.2.1 (2021) uses WCAG 2.1 AA. It’s the version everyone works to right now. It’s also the version cited for public-sector websites, in Commission Implementing Decision (EU) 2018/2048 as updated in 2021.
- No version has been formally cited under the European Accessibility Act yet. So there’s no presumption route under the Act at the moment.
- EN 301 549 v4.1.1 moves to WCAG 2.2 AA. It was published on 2 September 2026, according to Deque’s summary of what changed in v4.1.1.
v4.1.1 is expected to be the first version cited under the Act. Deque expects that around the end of November 2026. Once it’s cited, meeting it gives a legal presumption that you meet the Act, under Regulation 16. AccessibleEU’s news on the updated standard covers the change too.
We’ll update this page when the citation happens.
What’s new in WCAG 2.2
These are the new checks at level A or AA, in plain English. The W3C’s page on what’s new in WCAG 2.2 has the full details.
- The thing you’re tabbing to isn’t completely hidden behind a sticky header, cookie bar or chat bubble (2.4.11).
- Anything you drag has a simpler option, such as tapping, for people who can’t drag (2.5.7).
- Tap targets are big enough: at least 24 by 24 pixels, or spaced out enough to hit easily (2.5.8).
- Help is in the same place on every page, such as your phone number or contact link (3.2.6).
- You’re not asked for the same details twice in the same process, such as typing your address again at checkout (3.3.7).
- Logging in doesn’t depend on memory tests or puzzles, such as remembering a password with no way to paste it (3.3.8).
One old check was removed: 4.1.1 Parsing, which was about tidy code. The W3C now treats it as out of date.
Why our studies use WCAG 2.1 AA
Our research uses WCAG 2.1 AA because it’s the version everyone works to today. Each study’s method section explains this: Ireland 2026, local services, online shops, Shopify, hotels and financial services.
Our free scan uses the same standard, and our page about our research scanner explains how the studies run. We’ll add the WCAG 2.2 checks once v4.1.1 is cited under the Act.
What to do now
Fix the WCAG 2.1 basics first
Nearly every failure in our data is a WCAG 2.1 problem. These six account for most of it, and each has a plain-English guide:
- Hard-to-read text: fixing colour contrast
- Links that say nothing: fixing empty links
- Images with no description: writing alt text
- Zoom turned off: letting people pinch to zoom
- Buttons that say nothing: fixing buttons with no name
- Maps and videos with no title: fixing embedded content
Fixing these helps your customers today, whichever version ends up applying.
Build anything new to WCAG 2.2
Redesigning your website, changing theme or adding a new booking or checkout system? Ask for WCAG 2.2 AA from the start. It costs far less to build it in than to fix it later.
Most of the new checks are good sense anyway. Bigger buttons on phones and not typing your address twice help everyone.
A word on automated checks
Automated checks, including ours, find roughly a third of accessibility problems. They can’t tell whether your alt text makes sense or whether your checkout works with a keyboard. Use them as a starting point, not a certificate.
This isn’t legal advice. For exactly how the rules apply to your business, talk to a solicitor or the relevant regulator.