European Accessibility Act Guidelines: A Complete Technical and Compliance Guide

What the European Accessibility Act Requires—and Why It Matters Now

An estimated 87 million people in the European Union live with a disability, yet the majority of digital products and services launched before June 28, 2025 were built without legally enforceable accessibility requirements. That gap closed when the European Accessibility Act (Directive (EU) 2019/882) entered into force for new products and services placed on the EU market on or after June 28, 2025. The EAA is not a future obligation—it is an active legal framework that compliance teams must treat as a live enforcement environment today.

The Legal Architecture: What the EAA Regulates and Who It Covers

The EAA is a harmonization directive—it sets binding minimum requirements that each EU Member State transposes into national law. The directive targets economic operators: manufacturers, importers, distributors, and service providers operating in the EU market regardless of where they are headquartered.

Covered Products

• Consumer hardware with computing capability: general-purpose computers, smartphones, tablets
• Payment terminals and self-service kiosks: ATMs, ticketing machines, check-in kiosks
• E-readers: dedicated devices and associated software
• Television equipment: as it relates to digital interactive services

Covered Services

• Electronic communications services including real-time text and video relay
• Audiovisual media services and their websites and mobile apps
• Passenger transport services (air, rail, bus, waterborne) — websites, apps, e-ticketing, real-time travel information
• Banking and financial services — consumer-facing websites, mobile apps, electronic statements
• E-commerce services — any website or app used to sell products or services to consumers
• E-books and dedicated software

Who Is Exempt

Microenterprises—defined as businesses with fewer than 10 employees and annual turnover or balance sheet total not exceeding €2 million—are exempt from EAA requirements for services. This exemption does not apply to product manufacturers. Additionally, where conformance would impose a disproportionate burden, operators may claim a documented exception, but that claim must be substantiated and documented formally.

Purpose of the EAA

The directive's stated purpose is twofold: to ensure persons with disabilities have equivalent access to products and services across all EU Member States, and to eliminate the market fragmentation caused by divergent national accessibility laws. A single harmonized standard reduces compliance complexity for cross-border operators and creates a level playing field—but it also removes the ambiguity that previously allowed non-conformance to go unchallenged.

The Technical Standard: EN 301 549 and WCAG 2.1 Level AA

EN 301 549 V3.2.1 (March 2021) is the harmonized European standard that provides the technical specifications for EAA conformance. It incorporates WCAG 2.1 in full, making WCAG 2.1 Level AA the operative accessibility benchmark for digital products and services under the EAA.

Is WCAG Legally Required Under the EAA?

Yes—indirectly but binding. The EAA mandates functional accessibility requirements; EN 301 549 is the harmonized standard that demonstrates conformance with those requirements. EN 301 549 V3.2.1 incorporates WCAG 2.1 Level AA as its web content and document accessibility criteria. Meeting WCAG 2.1 AA therefore constitutes the primary evidence of EAA conformance for web and document-based outputs. WCAG 2.1 became a W3C Recommendation on June 5, 2018, and remains the operative version under EN 301 549—WCAG 2.2 (W3C Recommendation October 5, 2023) has not yet been incorporated into EN 301 549.

WCAG 2.1 AA: The Four Principles

WCAG 2.1 is organized around four principles—Perceivable, Operable, Understandable, Robust (POUR):

• Perceivable: Content must be presentable in ways users can perceive. This includes text alternatives for non-text content, captions for time-based media, and sufficient color contrast (minimum 4.5:1 for normal text).
• Operable: Interface components and navigation must be operable via keyboard alone, with no keyboard traps, and sufficient time limits.
• Understandable: Information and interface operation must be understandable, including readable language declarations, predictable navigation, and accessible error identification.
• Robust: Content must be interpreted reliably by current and future assistive technologies—valid markup, name/role/value semantics, and status messages programmatically determined.

EAA vs. WCAG: Clarifying the Relationship

WCAG is a technical specification; the EAA is a legal directive. The EAA creates the legal obligation; EN 301 549 maps that obligation to WCAG 2.1 AA criteria. Conformance with WCAG 2.1 AA is necessary but not the entirety of EAA compliance—EN 301 549 also covers non-web ICT (information and communications technology) such as hardware, closed functionality, biometric systems, and real-time two-way voice communication, which extend beyond WCAG's scope. For digital documents—particularly PDFs distributed as part of a covered service—the applicable standard is PDF/UA-1 (ISO 14289-1:2014), which defines the structural and tagging requirements for assistive technology compatibility.

PDF Documents Under the EAA

PDFs delivered as part of a covered e-commerce, banking, or transport service are in scope. A PDF used to deliver a bank statement, e-ticket, insurance policy, or product specification must meet both WCAG 2.1 AA (for any embedded interactive content) and PDF/UA-1 structural requirements: a complete and accurate tag tree—the hierarchical structure that assistive technologies traverse—correct reading order, tagged figures with meaningful alternative text, logical heading structure, and document language declaration. Untagged or improperly tagged PDFs distributed through covered services represent a direct EAA conformance failure. RemeDocs' PDF remediation process addresses these structural deficiencies systematically, producing PDF/UA-1-conformant documents verified against EN 301 549 criteria.

EAA Compliance Requirements: What Must Change in Your Digital Outputs

EAA compliance is not a single audit event—it is an operational discipline applied across the product and content lifecycle. The following breakdown covers the specific technical and procedural requirements economic operators must implement.

Website and Web Application Requirements

• Semantic HTML structure: Headings, landmarks, lists, and tables must be marked up correctly so screen readers can convey structure to users.
• Keyboard accessibility: All interactive elements—forms, menus, modals, carousels—must be fully operable without a mouse.
• Color contrast: Text must meet minimum contrast ratios: 4.5:1 for normal text, 3:1 for large text (18pt or 14pt bold) and UI component boundaries.
• Focus indicators: Visible focus states are mandatory; WCAG 2.1 AA requires focus to be visible, with enhanced criteria under WCAG 2.2.
• Alternative text: All non-decorative images require descriptive alt attributes; decorative images require alt="" with the attribute present.
• Form labels: Every input field requires a programmatically associated label; placeholder text is not a substitute.
• Error identification: Form errors must be identified in text and described specifically, not only by color.
• Language declaration: The lang attribute must be set on the <html> element and on any passage in a different language.

Mobile Application Requirements

• Support for platform accessibility APIs (UIAccessibility on iOS, AccessibilityNodeInfo on Android)
• Touch target sizes sufficient for users with motor impairments (WCAG 2.5.5 recommends 44×44 CSS pixels)
• Compatibility with screen readers (VoiceOver, TalkBack) and switch access devices
• No reliance on motion, gesture, or orientation as the sole means of interaction

Document Accessibility Requirements

• All PDFs must carry a complete tag tree with proper reading order
• Document title set in the document properties; language declared at document and passage level
• Tables must have column and row headers tagged; data cells associated with headers
• Figures require tagged Alt text entries; purely decorative figures must be marked as artifacts
• Hyperlinks require meaningful link text—not bare URLs or generic labels such as click here
• Form fields in PDFs must carry tooltip text that functions as a programmatic label for assistive technology

EAA Accessibility Statement Requirements

Service providers covered by the EAA must publish an accessibility statement—a formal declaration of conformance status, known limitations, and contact mechanisms for users to report barriers. This requirement mirrors the EU Web Accessibility Directive's statement obligation and is now extended to the broader set of EAA-covered services.

Required Elements of an EAA Accessibility Statement

• Conformance status: Whether the service is fully conformant, partially conformant, or non-conformant with EN 301 549 / WCAG 2.1 AA, with specific non-conformances listed
• Known limitations: Each identified barrier described with its location, impact, and the alternative means of access provided
• Technical environment: The browsers, assistive technologies, and operating systems against which the service was tested
• Testing methodology: Whether conformance was assessed by self-evaluation, third-party audit, or automated tooling—and the date of the most recent assessment
• Feedback and contact mechanism: A named contact point or form through which users can report accessibility barriers and request accessible alternatives
• Enforcement body: Reference to the competent national authority to which users may escalate unresolved complaints

Accessibility statements must be kept current. A statement dated more than 12 months prior without an updated assessment record is a compliance risk under Member State enforcement frameworks. When using RemeDocs to remediate document libraries, the remediation completion date and PDF/UA-1 conformance status can be incorporated directly into the statement's known-limitations log.

EAA Compliance Checklist

Key compliance checkpoint: The EAA has been in force since June 28, 2025. The checklist below reflects the minimum operational requirements for economic operators subject to the directive.

Scope and Applicability

• Confirm whether your organization qualifies as a microenterprise (fewer than 10 employees, under €2 million turnover); if not, full EAA obligations apply to services
• Identify all products and services placed on the EU market on or after June 28, 2025
• Map each covered offering to its applicable EN 301 549 functional requirements

Technical Conformance

• Conduct a WCAG 2.1 AA audit of all covered websites and web applications
• Audit mobile applications against EN 301 549 non-web ICT criteria
• Remediate all PDFs distributed through covered services to PDF/UA-1 (ISO 14289-1:2014) standard
• Verify reading order, tag tree integrity, heading structure, and alternative text on all remediated documents
• Test with at least two screen readers (e.g., NVDA + Firefox, JAWS + Chrome, VoiceOver + Safari) and keyboard-only navigation

Documentation and Process

• Publish an accessibility statement for each covered service, listing conformance status and known limitations
• Establish a user feedback and complaint mechanism with a defined response SLA
• Document any disproportionate burden claims with a formal cost-benefit analysis
• Integrate accessibility requirements into procurement contracts for third-party digital components
• Schedule annual re-audits and update accessibility statements accordingly

Organizational Readiness

• Assign a named accessibility lead or team responsible for EAA compliance
• Train development, design, and content teams on WCAG 2.1 AA criteria relevant to their roles
• Establish a document remediation workflow—RemeDocs provides a structured pipeline for PDF/UA-1 conformance at scale

Frequently Asked Questions: EAA Guidelines

Does the EAA apply to companies outside the EU?

Yes. The EAA applies to any economic operator placing covered products or services on the EU market, regardless of where the organization is incorporated. A US-based e-commerce platform selling to EU consumers is subject to EAA requirements for those transactions.

What is the difference between the EAA and the EU Web Accessibility Directive?

The EU Web Accessibility Directive (Directive 2016/2102) applies exclusively to public sector bodies—government websites and mobile apps. The EAA applies to the private sector across a defined set of product and service categories. Both reference EN 301 549 as the harmonized technical standard, but the EAA's scope is substantially broader and its enforcement mechanisms operate through market surveillance rather than public sector oversight.

Is there an EAA guidelines PDF I can reference?

The authoritative source is the directive text itself: Directive (EU) 2019/882, available via EUR-Lex. The European Commission has also published supporting guidance documents. For technical implementation, EN 301 549 V3.2.1 is the operative standard—it is available from ETSI. WCAG 2.1 is published by the W3C at w3.org/TR/WCAG21/.

What does the EAA require for employees and internal systems?

The EAA's primary scope is consumer-facing products and services placed on the EU market. Internal HR systems, intranets, and employee-facing tools are not directly covered by the EAA. However, separate obligations—including national anti-discrimination law and, for public sector employers, the Web Accessibility Directive—may apply to internal digital tools. Organizations building EAA-compliant external products frequently extend the same WCAG 2.1 AA standard to internal systems as a risk management measure.

How does the EAA handle PDF documents?

PDFs distributed as part of a covered service—bank statements, e-tickets, insurance documents, product manuals—are in scope. The applicable document standard is PDF/UA-1 (ISO 14289-1:2014). A conformant PDF requires a complete tag tree, logical reading order, tagged headings and tables, alternative text for figures, and a document language declaration. RemeDocs remediates PDFs to PDF/UA-1 conformance, producing documents that satisfy EN 301 549 document accessibility criteria.

What penalties apply for EAA non-conformance?

Penalties are set by each Member State through national transposition legislation. Common enforcement mechanisms include market withdrawal orders (requiring a non-conformant product or service to be removed from the market), financial penalties scaled to the severity and duration of non-conformance, and mandatory corrective action plans. The directive requires Member States to establish effective, proportionate, and dissuasive penalties—meaning enforcement is expected to carry material financial consequence.

Is WCAG 2.2 required for EAA compliance?

No. WCAG 2.2 (W3C Recommendation October 5, 2023) has not been incorporated into EN 301 549 V3.2.1, which remains the harmonized standard under the EAA. WCAG 2.1 Level AA is the operative conformance baseline. Organizations may voluntarily implement WCAG 2.2 success criteria—particularly 2.4.11 Focus Appearance and 2.5.7 Dragging Movements—as a forward-looking measure, but WCAG 2.2 conformance is not currently required for EAA compliance.

Key Takeaways

The EAA is a live enforcement obligation, not a future deadline. Products and services placed on the EU market on or after June 28, 2025 must conform to EN 301 549 V3.2.1—which incorporates WCAG 2.1 Level AA—from market entry. Compliance teams should treat the directive as an active regulatory environment with financial and market-access consequences for non-conformance.

PDF documents distributed through covered services are in scope. Bank statements, e-tickets, insurance policies, and product documentation must meet PDF/UA-1 (ISO 14289-1:2014) structural requirements: a valid tag tree, correct reading order, tagged headings and tables, and alternative text for figures. Untagged PDFs in covered service workflows are a direct conformance failure. RemeDocs provides a structured remediation pipeline that brings document libraries into PDF/UA-1 conformance at scale.

WCAG 2.1 AA is the binding technical standard; WCAG 2.2 is not yet incorporated. EN 301 549 V3.2.1 references WCAG 2.1 in full. WCAG 2.2 (October 2023) remains outside the harmonized standard. Organizations should build conformance programs against WCAG 2.1 AA as the legal baseline while monitoring EN 301 549 revision cycles for future incorporation of WCAG 2.2 criteria.