Skip to main content

Compliance guide · EAA and EN 301 549

EN 301 549 and EAA compliance. The European standard for digital accessibility.

EN 301 549 defines the technical accessibility requirements for ICT products and services, so organizations can meet the European Accessibility Act (EAA). Aligning with it is the practical way to show EAA compliance across the EU.

  • EN 301 549The European standard for ICT
  • EAAThe EU law it supports
  • Web, apps, softwarePlus documents, multimedia and hardware UI
  • WCAG 2.2 AAYour day-to-day checklist

What is EN 301 549 and how does it relate to the EAA?

EN 301 549 is the European standard for digital accessibility. It defines technical requirements for ICT products and services so organizations can meet the European Accessibility Act (EAA).

The standard applies to websites, mobile apps, software, documents, multimedia and hardware UI. Aligning with EN 301 549 is the practical way to show EAA compliance across the EU.

Play video Play the video: EN 301 549 explained in simple terms

Video explainer · 2 min

EN 301 549 explained in simple terms

This short video breaks down how EN 301 549 supports the European Accessibility Act (EAA). In two minutes, learn the key standards for digital accessibility and how they align with WCAG 2.2 AA.

By the tabnav team · October 19, 2025

Who must comply with EN 301 549 requirements?

Compliance is required for public sector bodies and for companies that provide digital products or services to EU users or governments. If you sell, procure or operate ICT in the EU, this applies.

  • Government agencies and public sector websites and apps
  • Vendors and contractors in public procurement
  • Private companies offering consumer digital services in EAA scope
  • Education, transport, banking and telecom providers where relevant

How does EN 301 549 compare to WCAG 2.2 AA and other accessibility laws?

EN 301 549 references WCAG. Meeting WCAG 2.2 AA for web and mobile content typically satisfies the core accessibility expectations in EN 301 549.

  • EN

    EN 301 549

    The EU technical standard covering ICT and procurement.

  • AA

    WCAG 2.2 AA

    Web and app content requirements used inside EN 301 549. Read the WCAG guide.

  • US

    ADA and Section 508

    US laws with similar goals. WCAG conformance supports cross-market compliance.

Use WCAG 2.2 AA as your day-to-day checklist. Map any extra EN 301 549 clauses for software, documents and hardware UI.

What are the main requirements of EN 301 549?

Your digital content and tools must be perceivable, operable, understandable and robust across browsers, devices and assistive technologies.

  • 01

    Web and apps

    Text alternatives, captions, keyboard support, focus visibility, clear headings, forms with labels, error help, reflow and zoom.

  • 02

    Documents and PDFs

    Tags, reading order, headings, alt text, table headers, bookmarks and language metadata.

  • 03

    Software

    Programmatic names and roles, accessibility API exposure, keyboard access and status notifications.

  • 04

    Multimedia

    Captions, transcripts and audio description where required.

  • 05

    Hardware UI

    Tactile or auditory cues, and operability without fine motor skills where in scope.

How to achieve EAA and EN 301 549 compliance step by step

Follow a simple path to reach and maintain compliance.

  1. Audit. Run WCAG 2.2 AA checks on web, apps and documents. Identify EN 301 549 items beyond WCAG.

  2. Remediate. Fix high-impact issues first. Improve templates, components and authoring workflows.

  3. Test. Validate with assistive technologies such as NVDA, JAWS and VoiceOver, and with the keyboard only.

  4. Document. Keep test results and conformance notes for procurement and vendor requests.

  5. Monitor. Schedule regression scans, review new releases and train content editors.

This process aligns teams to EN 301 549, supports EAA obligations and improves user experience for everyone.

How tabnav helps you stay compliant

Staying compliant with EN 301 549 is easier with the right tools. tabnav combines AI-driven accessibility monitoring with expert remediation guidance to help you stay aligned with the EAA and WCAG 2.2 AA.

Before you start, run a free test of your website’s accessibility status with the tabnav Free Accessibility Checker. It’s the quickest way to identify key accessibility gaps and track improvements over time.

Keep learning

How tabnav helps

Stay aligned with the EAA with tabnav. AI-driven monitoring with expert remediation guidance.

Free accessibility checker

Is your website ready for the EAA?

Enter your website address and get a free report on WCAG 2.2 AA and EAA issues, with code-level findings and a clear explanation of each one.

Free. The scan can take a few minutes.

FAQ

EAA and EN 301 549 questions, answered.

What is EN 301 549 and how does it relate to the EAA?

EN 301 549 is the European technical standard that supports the European Accessibility Act (EAA). It defines accessibility requirements for ICT products and services, including websites, apps, software, documents, and hardware, to ensure equal access for people with disabilities.

Who must comply with EN 301 549 requirements?

EN 301 549 compliance applies to public sector bodies, government suppliers, and private companies providing digital products or services within the EU. Any organization selling or maintaining ICT content for public use in Europe must meet these accessibility requirements.

How does EN 301 549 compare to WCAG 2.2 AA and other accessibility laws?

EN 301 549 aligns closely with WCAG 2.2 Level AA, which defines web and app accessibility standards. Meeting WCAG 2.2 AA typically ensures EN 301 549 compliance and supports cross-compliance with other laws such as the ADA and Section 508 in the United States.

What are the main requirements of EN 301 549?

The standard follows four key principles (perceivable, operable, understandable, and robust), ensuring accessibility across websites, mobile apps, software, and digital documents. This includes text alternatives, captions, keyboard navigation, color contrast, and compatibility with assistive technologies.

How to achieve EAA and EN 301 549 compliance step by step?

Start by auditing your website or digital assets against WCAG 2.2 AA, fix non-compliant areas, test with assistive technologies, and set up continuous monitoring. Maintaining accessibility over time ensures full EN 301 549 and EAA compliance while improving usability for all users.

Need help with EAA compliance?

Our accessibility specialists audit, fix and document your website, apps and documents, with conformance notes ready for procurement.

EN 301 549 explained in simple terms