EAA and EN 301 549 — European Accessibility Requirements

In this tutorial, you will learn about EAA and EN 301 549. We cover key concepts, practical examples, and best practices to help you master this topic.

The European Accessibility Act (EAA) and EN 301 549 require digital products and services sold in the EU to meet accessibility standards including WCAG 2.1 Level AA, with enforcement beginning June 2025 and fines up to 5 percent of annual turnover.

What You'll Learn

You will learn the scope of the EAA, how EN 301 549 defines technical requirements, who must comply, deadlines, penalties, and how to prepare for European market Compliance.

Why It Matters

The EAA affects any company selling digital products or services in the European Union regardless of where the company is based. Non-compliance means losing access to the EU market.

Real-World Use

DodaTech completed EAA compliance preparations for Durga Antivirus Pro in 2024, ahead of the June 2025 enforcement date. The product's WCAG 2.2 AA compliance and EN 301 549 documentation opened the EU market.

flowchart TD
  A[European Accessibility Act] --> B[Scope]
  A --> C[Technical Standard]
  A --> D[Deadlines]
  A --> E[Penalties]
  B --> F[Digital products and services]
  B --> G[E-commerce, banking, telecom]
  B --> H[Software, apps, websites]
  C --> I[EN 301 549 v3.2.1]
  C --> J[WCAG 2.1 Level AA]
  D --> K[June 28, 2025]
  D --> L[Phased through 2030]
  E --> M[Up to 5% of turnover]
  E --> N[Market restriction]

The European Accessibility Act

The EAA (Directive 2019/882) requires products and services sold in the EU to be accessible. It covers computers, smartphones, ATMs, ticketing machines, e-books, e-commerce, banking services, and telecom services.

Key Dates

The EAA entered into force in 2019. EU member states must transpose it into national law by June 28, 2025. Products placed on the market after this date must comply. Microenterprises have until 2030.

EN 301 549

EN 301 549 is the European standard for ICT accessibility. Version 3.2.1 references WCAG 2.1 Level AA as the baseline for web and software accessibility.

What EN 301 549 Covers

Web content, mobile apps, software, hardware, documentation, and support services. It includes WCAG success criteria plus additional requirements for closed functionality, biometrics, and real-time text.

function assessEAARisk(product, targetMarket) {
  const risks = [];
  if (targetMarket === 'EU' || targetMarket === 'EEA') {
    if (product.category === 'e-commerce' || product.category === 'banking' ||
        product.category === 'telecom' || product.category === 'software') {
      risks.push('EAA applies to your product category');
    }
    if (!product.wcagCompliant) risks.push('WCAG compliance required');
    if (!product.en301549Documented) risks.push('EN 301 549 documentation needed');
    if (!product.hasAccessibilityStatement) risks.push('Accessibility statement required');
  }
  return risks;
}

const product = {
  category: 'software',
  wcagCompliant: true,
  en301549Documented: false,
  hasAccessibilityStatement: false
};

console.log(assessEAARisk(product, 'EU'));

Expected output:

['EAA applies to your product category', 'EN 301 549 documentation needed', 'Accessibility statement required']

Compliance Requirements

Product must meet EN 301 549 / WCAG 2.1 AA. Accessibility statement must be published. Feedback mechanism must be provided for users to report issues. Declaration of conformity must be available.

Penalties

Each EU member state sets its own penalties. Maximum penalties reach 5 percent of annual turnover in some countries. Market surveillance authorities can restrict or prohibit non-compliant products.

Common Mistakes

1. Assuming EAA Only Applies to EU Companies

The EAA applies to any company selling products or services in the EU regardless of where the company is based.

2. Targeting WCAG 2.0 Instead of 2.1

EN 301 549 references WCAG 2.1. Targeting WCAG 2.0 is insufficient for EAA compliance.

3. Forgetting the Accessibility Statement

The EAA requires a published accessibility statement. Without one, you are non-compliant regardless of technical accessibility.

4. Ignoring Microenterprise Exceptions

Microenterprises have until 2030. But if you plan to grow, comply early.

5. Not Documenting Conformance

A declaration of conformity is required. Without it, market surveillance authorities cannot verify compliance.

6. Treating EAA as a One-Time Requirement

Compliance is ongoing. Products placed on the market before the deadline may still need updates to maintain compliance.

7. Forgetting Hardware Requirements

The EAA covers hardware including computers, smartphones, and ATMs. Software-only compliance is insufficient for hardware products.

Practice Questions

1. When does the EAA take effect?

June 28, 2025. Microenterprises have until 2030.

2. What technical standard does the EAA reference?

EN 301 549 version 3.2.1, which references WCAG 2.1 Level AA.

3. What is the maximum penalty for EAA non-compliance?

Up to 5 percent of annual turnover in some EU member states.

4. Does the EAA apply to non-EU companies?

Yes. Any company selling digital products or services in the EU must comply.

5. Challenge: Determine whether your product falls under EAA scope. If it does, create an EAA compliance timeline with milestones.

FAQ

Mini Project

Create an EAA compliance checklist for your product. Include WCAG 2.1 AA compliance, EN 301 549 documentation, accessibility statement, feedback mechanism, and declaration of conformity.

What's Next

Learn about AODA requirements in Ontario, Canada. Then explore the Equality Act 2010 in the United Kingdom.