accessibility act

EN 301 549 v4.1.1: 6 Must-Fix WCAG 2.2 Changes Before Official Journal Citation

EN 301 549 v4.1.1: 6 Must-Fix WCAG 2.2 Changes Before Official Journal Citation

get in touch

Know where you stand. Know what to work on next.

Tell us what you’re working on and where you need support. Our accessibility specialists can help with audits, remediation, VPAT/ACR, accessible development, and ongoing compliance.

Free 30-minute consultation (opens in new tab)

Free 30-minute call: talk through where you stand, scope a project or get a quote.

Need technical answers now? Book the $100 one-hour consultation to walk through an audit, talk with a developer or review your site live.

Let’s find the barriers before your users do

Indicates a required field.


Your information is kept private and never shared with third parties.

EN 301 549 v4.1.1 is the September 2026 update to Europe’s harmonised ICT accessibility standard. It moves the web, document and software baseline from WCAG 2.1 to WCAG 2.2 Level AA, revises real-time text requirements, and adds mapping annexes for the European Accessibility Act (EAA) and the Web Accessibility Directive. It is published, but it is not yet the Official Journal citation that confers presumption of conformity — so teams should prepare now without pretending the legal safe harbour has already flipped.

That timeline became concrete in early September 2026. According to the ETSI work-item record, EN 301 549 V4.1.1 was published on 2 September 2026. The official ETSI PDF records adoption on 24 August 2026, with national announcement by 30 November 2026 and endorsement by 31 May 2027. AccessibleEU and Ireland’s National Disability Authority both stress the same point: until the European Commission cites the new version in the Official Journal of the European Union, EN 301 549 v3.2.1 (2021) remains the cited reference for presumption of conformity.

This founder-led guide is written by accessibility testers (CPACC, WAS, CPWA, DHS Trusted Tester, 10+ years) who audit websites, apps, documents and ICT products for EU-facing organisations. It is not legal advice. It covers what changed in EN 301 549 v4.1.1, the six WCAG 2.2 Level A/AA criteria that dominate gap analyses, and a practical readiness plan. Prefer the free 30-minute call below if you are still scoping; use the $100 technical hour when you already have findings to walk through.

EN 301 549 v4.1.1 At A Glance

Choose Your Next Step

Want a free one-page check first? AccessibilityScore.in (opens in a new tab) is a free WCAG scan powered by axe-core; it is a starting point that complements a manual EN 301 549 / WCAG 2.2 audit, not a replacement. For a full manual audit of up to 25 templates, see the $2,000 Complete Audit on our pricing page. Our European Accessibility Act guide covers who the EAA reaches.

Free 30-Minute Call

Best for: first conversations, scoping and quotes

Tell us whether you need an EAA gap analysis, a WCAG 2.2 uplift, PDF work or a VPAT/ACR refresh. We outline the right package and send a quote. No technical prep needed.

Book a free 30-minute call (opens in a new tab)

EU Accessibility Compliance Audit (Quote)

Best for: teams that need an EN 301 549 / EAA evidence backlog

Manual WCAG 2.2 AA testing mapped to EN 301 549 clauses, with a prioritised remediation backlog and clear notes on what still awaits Official Journal citation.

Get an EU audit quote

$100 Technical Consultation

Best for: teams that already have findings or a developer on the call

A one-hour hands-on session to walk through EN 301 549 / WCAG 2.2 findings, talk with your developer, or review site issues live. Pick this when you need technical answers now.

Book a $100 technical hour

What EN 301 549 Is — and Why Version Numbers Matter

EN 301 549 is the European technical standard for accessibility requirements for ICT products and services. It is broader than WCAG alone: it covers web content, non-web documents, software, hardware and related ICT services. Public-sector rules under the Web Accessibility Directive (Directive (EU) 2016/2102) and private-sector obligations under the European Accessibility Act (Directive (EU) 2019/882) both point to it as the technical reference for demonstrating conformity.

For who the EAA covers, see our European Accessibility Act guide and European Accessibility Act compliance article. For how EN 301 549 sits next to ADA, Section 508 and VPAT work, see which accessibility framework actually matters.

Version numbers matter because presumption of conformity attaches to the version cited in the Official Journal, not the newest ETSI PDF. Until citation exists, quote AccessibleEU: prepare for WCAG 2.2, but do not claim EN 301 549 v4.1.1 is already the legal reference.

What Officially Changed in EN 301 549 v4.1.1

The ETSI/CEN/CENELEC PDF lists the significant changes since EN 301 549 V3.2.1 (March 2021). The ones that matter for most digital teams are:

  1. Clauses 9, 10 and 11 now align with WCAG 2.2 for web pages, non-web documents and software.
  2. Clause 6.2 Real-Time Text (RTT) is significantly revised and extended to include total conversation (voice, real-time text and video together).
  3. A new Annex ZA maps the standard to the Web Accessibility Directive.
  4. A new Annex ZB maps the standard to the essential requirements of the European Accessibility Act.
  5. A new clause A.2 supports evaluating specific ICT products and services against those EAA essential requirements.

AccessibleEU adds that the update adds six new WCAG 2.2 requirements, removes obsolete WCAG 4.1.1 Parsing, and expects sites and documents to better respect users’ accessibility preferences. Deque’s technical summary warns that WCAG 2.2 AA alone is not full EN 301 549 — especially if Clause 6 applies.

LayerWhat v4.1.1 changesWho feels it first
Web (clause 9)WCAG 2.2 Level AA baselineSites, portals, ecommerce, SaaS web apps
Non-web documents (clause 10)WCAG 2.2 alignmentPDFs, manuals, statements, invoices
Software (clause 11)WCAG 2.2 alignmentDesktop clients, some embedded UIs
Real-time communication (clause 6)Expanded RTT / total conversationTelecom, contact centres, messaging, video
Legal mapping (ZA / ZB, A.2)Clearer EAA and WAD pathsCompliance, legal, procurement

Timeline: Publication Is Not Official Journal Citation

Keep these dates distinct when you brief executives:

DateWhat it means
24 August 2026EN adopted (ETSI PDF)
2 September 2026EN published (ETSI work-item milestone)
30 November 2026Latest announcement date (doa) in the ETSI PDF
31 May 2027 / 31 May 2028National endorsement (dop/e) and withdrawal of conflicting standards (dow)
Official Journal citation (pending)NDA currently expects around 16 December 2026; earlier forecasts pointed to around 30 November 2026. Treat as targets — watch the Official Journal.

Until citation happens, V3.2.1 remains the cited presumption-of-conformity reference. That does not mean you should wait. The technical text is public, and the EAA has already been in force for in-scope products and services since 28 June 2025, as the NDA notes.

EN 301 549 v4.1.1 timeline road from August 2026 adoption and September 2026 publication to the November announcement and Official Journal citation

The 6 Must-Fix WCAG 2.2 Level A/AA Changes

WCAG 2.2, a W3C Recommendation since 5 October 2023, adds nine success criteria versus WCAG 2.1. Six are Level A or AA — the ones EN 301 549 v4.1.1 pulls into the practical target for web, documents and software. Details below follow W3C’s “What’s New in WCAG 2.2” page and the WCAG 2.2 Recommendation itself.

CriterionLevelWhere it failsHow to fix it
2.4.11 Focus Not Obscured (Minimum)AASticky headers, cookie banners or chat bubbles covering the focused controlKeep focused items visible; shrink or dismiss overlays during keyboard use. See our manual keyboard accessibility testing guide.
2.5.7 Dragging MovementsAAKanban boards, drag-only sliders, crop tools, reorder lists with no up/down controlsAdd buttons or steppers that achieve the same result; keep drag as an extra path, not the only one.
2.5.8 Target Size (Minimum)AAIcon-only toolbars, packed social icons, pagination chevrons, mobile filter chips under 24×24 CSS pxEnlarge hit areas in the design system, or space undersized targets so their 24-pixel circles do not intersect.
3.2.6 Consistent HelpAHelp links that jump from header to footer between templatesPut support entry points in one relative place across templates and keep that order stable.
3.3.7 Redundant EntryAMulti-step checkouts that force users to retype name, address or emailPersist earlier answers, offer select-from-previous controls, and avoid resetting forms on back steps.
3.3.8 Accessible Authentication (Minimum)AALogin walls that block paste, CAPTCHA-only challenges, “type the code” with no other pathAllow paste and password managers; offer magic-link or passkey options; provide an accessible alternative when a cognitive test remains.
Monitor with undersized 24px icon targets under a magnifier and a sticky bar hiding keyboard focus, the Target Size and Focus Not Obscured failures

Beyond WCAG: Documents, Preferences and Real-Time Communication

If your EN 301 549 v4.1.1 programme stops at the six web criteria, you will under-scope.

Documents. Clause 10 alignment with WCAG 2.2 means PDFs and Office-style files need tagged structure, reading order and the new 2.2 criteria where they apply. AccessibleEU specifically recommends reviewing digital documents. See our PDF accessibility guide, document accessibility testing, and PDF document remediation.

User preferences. AccessibleEU notes websites and documents should better respect users’ accessibility preferences. Treat OS/browser settings (contrast, reduced motion, text size) as test conditions; confirm exact clauses in the ETSI text.

Real-time communication. If you ship calling, messaging, contact-centre or video products, Clause 6 matters. The ETSI PDF says RTT requirements in clause 6.2 were significantly revised and extended to include total conversation. Web-only retailers can usually park this; communications vendors cannot.

Mobile apps. Pair web remediation with mobile accessibility testing when an app is in scope for the EAA or public-sector WAD obligations.

A Practical EN 301 549 v4.1.1 Readiness Plan

StepWhat to do
1. Confirm legal scopeEAA, WAD, both, or neither — confirm with qualified counsel for your products and markets.
2. Inventory ICT in scopeWeb properties, apps, customer PDFs, portals, and any real-time communication products.
3. Run a WCAG 2.2 AA gap analysisCritical journeys including sticky UI, authentication and multi-step forms. Scans help; they do not replace keyboard and screen reader testing.
4. Expand to documents and softwareWhere clauses 10 and 11 apply.
5. Fix the design system firstTarget size, focus visibility, dragging alternatives and consistent help are component-level problems.
6. Update procurement languageAsk vendors for EN 301 549 / WCAG 2.2 evidence. The NDA points procurement teams to TR 101 551 V2.1.1 (2026-02).
7. Refresh VPAT / ACR drafts carefullyState which EN version and WCAG edition you evaluated; do not claim Official Journal presumption before citation. See VPAT/ACR documentation.
8. Train, remediate and re-testUse training workshops, remediation, an accessibility audit, or an EU accessibility compliance audit. See our sample audit report.
WCAG 2.2 issues moving on a conveyor into an EN 301 549 binder, illustrating an audit backlog mapped to EN 301 549

How This Fits US ADA Work (Without Mixing the Rules)

US private-sector website risk still runs mainly through ADA Title III litigation, not EN 301 549. Moving to WCAG 2.2 helps on both sides of the Atlantic, but EAA presumption of conformity is an EU mechanism. Keep the evidence packs separate even when the engineering work overlaps.

The standard also travels beyond the EU. Australia adopts it as AS EN 301 549, and the Australian Human Rights Commission says its requirements should be met for digital products, using WCAG 2.2 where the standard still references 2.1 (see our Australia website accessibility audit). In practice, public bodies and the SaaS vendors that sell to them are usually the first to be asked for EN 301 549 evidence; our government and public sector and SaaS accessibility pages cover what those buyers expect.

Start Your EN 301 549 v4.1.1 Gap Analysis

EN 301 549 v4.1.1 is adopted and published; the six WCAG 2.2 Level A/AA criteria are public; the EAA mapping annexes are in the text; and Official Journal citation is the next formal step. Teams that inventory scope, fix design-system issues, and evidence WCAG 2.2 AA now will spend far less time firefighting later.

If you want a prioritised backlog mapped to EN 301 549 and WCAG 2.2, start with a free 30-minute call to understand where you stand and get a quote, request an EU accessibility compliance audit, or book a $100 technical consultation when you already have findings or a developer on the call. A $500 Quick Audit fits smaller sites that need an expert check beyond a scanner.

Frequently Asked Questions

Is EN 301 549 v4.1.1 legally binding today?

Not as the Official Journal presumption-of-conformity benchmark. AccessibleEU and the National Disability Authority both state that until the European Commission cites EN 301 549 v4.1.1 in the Official Journal, EN 301 549 v3.2.1 (2021) remains the current reference; v3.2.1 is the version cited under the Web Accessibility Directive. The NDA notes that once v4.1.1 is cited, conformance with it will create a presumption of conformity with both the Web Accessibility Directive and the European Accessibility Act. The new text is published and organisations should prepare for it, but citation is the legal switch.

When will EN 301 549 v4.1.1 be cited in the Official Journal?

The ETSI PDF does not fix a citation date, and the Commission has not announced one. The NDA currently expects citation on 16 December 2026, in line with ETSI’s current project schedule. Earlier forecasts, including Deque’s, pointed to around 30 November 2026, which is the standard’s date of announcement and an earlier schedule target. Monitor the Official Journal rather than treating any forecast as final.

Does EN 301 549 v4.1.1 require WCAG 2.2 Level AA?

For the web, document and software requirements in clauses 9, 10 and 11, yes — the ETSI PDF states those clauses were updated to align with the WCAG 2.2 Recommendation, and AccessibleEU summarises the shift from WCAG 2.1 to WCAG 2.2 as the headline change. Full EN 301 549 conformance can still require more than WCAG alone, especially for real-time communication and other ICT clauses.

What are the six new WCAG 2.2 Level A/AA criteria?

They are 2.4.11 Focus Not Obscured (Minimum) (AA), 2.5.7 Dragging Movements (AA), 2.5.8 Target Size (Minimum) (AA), 3.2.6 Consistent Help (A), 3.3.7 Redundant Entry (A), and 3.3.8 Accessible Authentication (Minimum) (AA). WCAG 2.2 also adds three AAA criteria, which sit outside the usual AA target. Details are on the W3C “What’s New in WCAG 2.2” page.

Does meeting WCAG 2.2 mean we meet EN 301 549 v4.1.1?

No. WCAG 2.2 Level AA is the baseline for the web, document and software clauses, but EN 301 549 also covers other ICT requirements. Deque is explicit that testing only for WCAG 2.2 AA is not enough where regulation calls for EN 301 549 conformance — especially if Clause 6 real-time communication applies to your product.

Who needs to care if we are outside the EU?

The EAA can apply to companies outside the EU when they offer in-scope products or services to consumers in the EU, as the NDA notes. If you sell into the EU digital market, treat EN 301 549 as part of your product compliance evidence even if your headquarters is elsewhere. Confirm applicability with qualified counsel for your specific products and distribution model.

Should we update our VPAT or ACR now?

You can and often should refresh testing against WCAG 2.2 and document which EN 301 549 edition you evaluated. Be precise in the report: state the standard version, the WCAG edition and level, the scope, and whether Official Journal citation of v4.1.1 has occurred yet. Avoid implying presumption of conformity before citation exists. If you need a VPAT/ACR drafted or refreshed, start with a free 30-minute call to scope it, or book a $100 technical consultation when you already have findings to walk through.

Should I book the free 30-minute call or the $100 technical consultation?

Book the free 30-minute call when you want a first conversation about where you stand, which EN 301 549 / EAA package fits, or a quote. Book the $100 one-hour technical consultation when you need a hands-on session — walking through audit findings, talking with your developer, or reviewing site issues live.

Can a free automated scan tell me if I meet EN 301 549 v4.1.1?

No. A free one-page scan such as AccessibilityScore.in (powered by axe-core) is a useful starting point for common WCAG failures on a single public page, but it does not replace a manual EN 301 549 / WCAG 2.2 audit. Automated tools miss keyboard, screen reader and many Clause 6 / document issues. Use the scan to orient yourself, then plan a manual gap analysis.

Written by Shadab Saifi Published Last updated

Related Articles

View all