Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

EN 301 549 V4.1.1 is the newest edition of Europe’s accessibility standard for ICT products and services, published in September 2026. For website teams, its most visible change is that its web requirements align with WCAG 2.2. But publication does not make this edition the current harmonised legal reference: the European Commission’s current information identifies V3.2.1 as the harmonised version while citation of V4.1.1 in the Official Journal is pending. Teams can prepare for the updated technical direction now while tracking which edition is currently relevant to their legal obligations.

What EN 301 549 V4.1.1 covers

EN 301 549 is a broad accessibility standard for information and communications technology (ICT), not a checklist limited to websites. ETSI, CEN and CENELEC’s V4.1.1 covers areas including functional performance, hardware, real-time communications, video, web content, non-web documents, non-web software, product and service information, and access to relay and emergency services. It sets requirements alongside test procedures and evaluation methods. The standard is intended for people involved in designing, developing, evaluating, procuring and overseeing accessible ICT.

Its scope is not every assistive technology: the standard says it is not intended to apply to assistive technologies designed specifically for use by people with disabilities, apart from a particular requirement concerning assistive technologies that use documented platform accessibility services. See the EN 301 549 V4.1.1 text for the defined requirements and scope.

What changes for website planning

V4.1.1 updates clauses 9, 10 and 11 to align with WCAG 2.2. Those clauses address web content, non-web documents and non-web software, respectively. This is a reason to plan for WCAG 2.2, but it does not make a WCAG checklist a complete EN 301 549 evaluation: the standard includes requirements beyond those web criteria, and its annexes map requirements to relevant EU directives.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
#1 Best Overall

Keep the types of material in your digital service distinct when planning work:

  • Web pages and web applications: assess the web content requirements and identify the pages, states and user journeys in scope.
  • Documents: include downloadable or otherwise distributed non-web documents, such as PDFs, rather than assuming that checking the surrounding web page covers them.
  • Software and other ICT: determine whether non-web software, embedded media, devices or communications features are part of the product or service and which clauses apply.

Do not assume that every clause applies to every website or service. The applicable requirements depend on the ICT involved and the relevant directive mapping; use the standard’s annexes and the relevant legal context to determine scope.

Is V4.1.1 legally required now?

Publication and harmonisation are different events. ETSI published V4.1.1 in September 2026, but the European Commission’s standards information still lists EN 301 549 V3.2.1 as the latest harmonised version for the Web Accessibility Directive (WAD). AccessibleEU’s update of 7 September 2026 says formal citation of V4.1.1 in the EU Official Journal is pending and identifies V3.2.1 as the current reference for demonstrating conformity with the European Accessibility Act (EAA) and WAD.

The standard describes V4.1.1 as one voluntary means of conformity with the EAA; the presumption of conformity associated with a harmonised standard applies once it is cited in the Official Journal, within that standard’s scope. Do not claim that V4.1.1 already provides that presumption. Citation status can change, so check the Commission’s WAD standards and harmonisation page before making a legal-conformity claim. Which obligations apply to a particular organisation or website depends on its circumstances; this standards overview is not legal advice.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How to prepare without confusing readiness with legal status

AccessibleEU recommends that organisations prepare by reviewing websites and digital documents against WCAG 2.2, updating testing processes and audit checklists, and reviewing procurement and supplier requirements. It also notes that publication of V4.1.1 does not itself create a new compliance deadline. A practical plan is to keep technical readiness and the current harmonised reference on separate tracks.

  1. Inventory the experience. List the relevant pages, application journeys, mobile experiences, documents, embedded media and software. Identify which content is maintained by your team and which is supplied by a third party.
  2. Map scope before assigning fixes. For each part of the inventory, determine which standard clauses and directive mappings are relevant. Avoid treating one website-wide WCAG score as an answer for every ICT component.
  3. Use WCAG 2.2 as a preparation target. Review web content and relevant documents and software against the updated direction in V4.1.1, while recording separately which harmonised edition currently applies to your conformity assessment.
  4. Update evaluation practices. Revise audit checklists and evaluation methods to reflect the relevant requirements. Combine automated checks with human evaluation, and record what was evaluated, how, and what evidence supports each finding.
  5. Review procurement and supplier evidence. Check that contracts, accessibility statements and supplier documentation address the parts of the service your organisation relies on, including third-party content and services.
  6. Recheck the legal reference. Before stating that a product or service conforms, verify the Commission’s current Official Journal citation status and the requirements relevant to your case.

AccessibleEU’s preparation advice is available in its 7 September 2026 update.

Rank #4
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Use screenshots as review evidence, not as an accessibility verdict

A screenshot can help a team discuss a particular page state or document a visual issue, but it cannot establish accessibility conformance by itself. A static image does not show whether content works with a keyboard, how it is exposed to assistive technology, or whether interactive states and error handling are usable. Treat captured images as supporting review artifacts alongside appropriate manual and automated evaluation, not as a substitute for it.

For teams that want clean visual captures of pages to include in a review workflow, ScreenshotNeo is a website screenshot API and MCP server. It is not an EN 301 549 evaluator and does not determine whether a page conforms.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Or skip the browser setup

One GET request can return a screenshot; this cURL example captures a representative page as WebP. See the ScreenshotNeo API documentation for request options.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webp

Before capture, ScreenshotNeo accepts the cookie or consent banner as a visitor and removes more than 60 known consent platforms, newsletter popups and chat widgets; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server gives AI agents tools to take screenshots, get page information and capture PDFs. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. These captures can support visual review, but they do not replace accessibility testing.

Sign up for 1,000 free screenshots a month, with no card required.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.