EAA Compliance Experts: How to Achieve and Maintain European Accessibility Act Conformance

Is Your Organization Ready for the EAA Deadline—or Operating on Assumptions?

June 28, 2025 is the enforcement date for the European Accessibility Act (EAA), Directive 2019/882/EU. Organizations selling digital products and services in the EU market—whether based in Berlin, Boston, or Bangkok—face binding accessibility obligations that carry legal, financial, and reputational consequences for non-conformance. Many compliance directors are discovering, too late, that internal audits conducted against outdated checklists or incomplete WCAG mappings have left significant gaps.

This guide addresses the precise questions EAA compliance experts are asking right now: what the standard actually requires, how it differs from WCAG, who enforces it, and what a defensible compliance posture looks like in practice.

EAA Compliance Answer Block

The European Accessibility Act requires that digital products and services—including websites, mobile applications, e-commerce platforms, e-books, and PDFs—conform to WCAG 2.1 Level AA as the operative technical standard. Compliance is mandatory for private-sector companies operating in EU member states, with a general deadline of June 28, 2025. Each EU member state designates its own national enforcement authority; non-conformance can result in market withdrawal orders, fines, and civil liability. Organizations must publish an EAA accessibility statement documenting conformance status, known barriers, and remediation timelines. Document types—including PDFs, Word files, and spreadsheets used in service delivery—fall within scope if they are integral to accessing a covered service. Achieving compliance requires a structured audit against WCAG 2.1 AA success criteria, semantic remediation of all in-scope documents, assistive technology testing, and ongoing monitoring. RemeDocs' PDF remediation process maps directly to these requirements, producing tagged, structured documents that satisfy both EAA and PDF/UA-1 (ISO 14289-1:2014) obligations simultaneously.

What Is the EAA and Which Organizations Are In Scope?

The European Accessibility Act (EAA), formally Directive 2019/882/EU, is EU-wide legislation that harmonizes accessibility requirements across member states for a defined set of products and services. Unlike the EU Web Accessibility Directive (2016/2102/EU), which applies exclusively to public-sector bodies, the EAA targets private-sector economic operators—manufacturers, importers, distributors, and service providers.

Covered Products and Services

The EAA scope is product- and service-specific, not sector-wide. In-scope categories include:

• Consumer electronics with interactive computing capability (smartphones, tablets, set-top boxes)
• Self-service terminals: ATMs, ticketing machines, check-in kiosks
• E-commerce services: websites and apps used for selling goods or services to consumers
• Electronic communications services: messaging, video calling platforms
• Banking services accessed digitally by consumers
• E-books and dedicated reading software
• Audiovisual media services and their access software
• Transportation services with passenger-facing digital touchpoints

Who Must Comply

Any private-sector organization that places covered products on the EU market or provides covered services to EU consumers is subject to the EAA—regardless of where the organization is headquartered. A US-based SaaS provider with EU customers offering in-scope services falls within scope. Micro-enterprises—defined as businesses with fewer than 10 employees and annual turnover or balance sheet total not exceeding €2 million—are exempt from EAA service requirements, though not product requirements.

The Disproportionate Burden Exemption

Service providers may invoke a disproportionate burden exemption if conformance would require a change that fundamentally alters the nature of the service or imposes costs that are disproportionate given the organization's size and resources. This exemption is not self-executing: it requires documented assessment, periodic review, and notification to the relevant national authority. Organizations relying on this exemption without documentation face significant enforcement risk.

How to Be EAA Compliant?

EAA compliance requires conformance to WCAG 2.1 Level AA across all in-scope digital touchpoints, supported by documented processes, an accessibility statement, and a functioning feedback mechanism. The following framework reflects the implementation path used by organizations that have achieved defensible conformance.

Step 1: Scope Determination

Identify every digital product and service your organization places in the EU market. Map each against the EAA's product and service categories. Include digital documents—PDFs, e-books, downloadable forms—if they are integral to service delivery. A scoping error at this stage is the most common source of compliance gaps discovered during enforcement audits.

Step 2: Baseline Audit Against WCAG 2.1 AA

Conduct a structured conformance audit of all in-scope interfaces and documents against WCAG 2.1 Level AA success criteria. Automated scanning tools (axe-core, WAVE, Deque WorldSpace) can surface approximately 30–40% of detectable issues; the remainder require manual inspection and assistive technology testing. Audit outputs must document each failure with: the affected URL or document, the violated success criterion, the severity, and the remediation approach.

Step 3: Document Accessibility Remediation

PDFs and other document formats within scope require semantic remediation—not surface-level tagging. Compliant PDFs must include: a complete, accurate tag tree; correct reading order; tagged figures with meaningful alternative text; properly structured headings (H1–H6), lists, and tables; document language and title metadata; and bookmarks for documents exceeding 20 pages. PDF/UA-1 (ISO 14289-1:2014) provides the technical specification for accessible PDFs; EAA-compliant document remediation should satisfy both WCAG 2.1 AA and PDF/UA-1 simultaneously.

RemeDocs' PDF remediation process applies full semantic tagging, reading order correction, and PDF/UA-1 validation to produce documents that satisfy EAA document requirements. For organizations with large document libraries, RemeDocs provides volume remediation workflows that integrate into existing content management pipelines.

Step 4: Publish an EAA Accessibility Statement

The EAA requires service providers to make their accessibility conformance status publicly available. An EAA accessibility statement must include:

• The WCAG 2.1 AA success criteria against which conformance is assessed
• Known barriers and the affected user groups
• Remediation timeline for each known barrier
• A contact mechanism for users to report accessibility issues or request accessible alternatives
• Information on the applicable national enforcement authority and how to escalate complaints

Step 5: Establish Ongoing Monitoring

Accessibility conformance degrades over time as content is updated and new features are deployed. Sustainable compliance requires: regression testing integrated into development pipelines, periodic full audits (minimum annually), a triaged process for handling user-reported barriers, and accessibility requirements embedded in procurement contracts for third-party components.

EAA Compliance Checklist Summary

• Scope mapping completed and documented
• WCAG 2.1 AA audit conducted with manual and automated testing
• All in-scope PDFs remediated to PDF/UA-1 and WCAG 2.1 AA
• Accessibility statement published with conformance status and known exceptions
• User feedback mechanism operational and monitored
• Disproportionate burden assessments documented where applicable
• Accessibility requirements embedded in procurement and development processes
• Annual re-audit scheduled

What Is the Difference Between EAA and WCAG?

The EAA and WCAG operate at different layers of the accessibility framework: WCAG 2.1 is a technical specification produced by the W3C; the EAA is binding EU law. Understanding this distinction is essential for scoping compliance programs and avoiding the common mistake of treating WCAG conformance as equivalent to EAA compliance.

WCAG 2.1: A Technical Standard

WCAG 2.1—W3C Recommendation, June 5, 2018—provides testable success criteria for making web content perceivable, operable, understandable, and robust (the POUR principles). It defines three conformance levels: A, AA, and AAA. WCAG 2.1 has no enforcement mechanism of its own; it becomes legally binding only when adopted by reference in legislation or regulation. WCAG 2.2—W3C Recommendation, October 5, 2023—adds nine new success criteria, primarily addressing mobile and cognitive accessibility, but the EAA explicitly references WCAG 2.1 AA as the required standard.

The EAA: A Legal Mandate That Incorporates WCAG

The EAA adopts WCAG 2.1 Level AA as its operative technical standard via EN 301 549 V3.2.1 (March 2021), the harmonized European standard for ICT accessibility. EN 301 549 incorporates WCAG 2.1 AA by reference and extends it with additional requirements for non-web documents, software, hardware, and telecommunications. This layered structure means EAA compliance requires satisfying WCAG 2.1 AA plus the additional EN 301 549 clauses applicable to your product or service type.

Key Structural Differences

• Enforcement: WCAG has none; the EAA has designated national market surveillance authorities with powers to order market withdrawal and impose fines.
• Scope: WCAG addresses web and software content; the EAA covers physical products, hardware, and service ecosystems in addition to digital interfaces.
• Documentation obligations: WCAG conformance claims are voluntary self-declarations; EAA requires formal accessibility statements, CE-marking processes for products, and technical documentation.
• Legal liability: WCAG non-conformance carries no direct legal penalty; EAA non-conformance can result in enforcement action, fines, and civil claims under member state implementing legislation.
• Temporal obligation: WCAG is a point-in-time standard; the EAA creates a continuing legal obligation to maintain conformance.

EAA Accessibility Guidelines vs. WCAG: Practical Implications

For digital-only service providers—websites, mobile apps, SaaS platforms—the practical difference between EAA and WCAG 2.1 AA compliance is primarily one of documentation, process, and legal standing rather than technical criteria. The success criteria you are auditing against are WCAG 2.1 AA. What the EAA adds is: the legal obligation to conform, the requirement to publish an accessibility statement, the obligation to provide a feedback mechanism, and exposure to enforcement if you do not. Organizations that have achieved WCAG 2.1 AA conformance and documented it properly are substantively positioned for EAA compliance—but the documentation and procedural layer is non-trivial and is frequently underdeveloped.

Who Enforces the EAA?

EAA enforcement is decentralized: each EU member state designates its own national market surveillance authority (MSA) responsible for monitoring compliance and taking corrective action. There is no single EU-level EAA enforcement body. This structure has direct implications for how organizations with multi-market EU presence must manage their compliance obligations.

National Market Surveillance Authorities

Member states were required to designate their MSAs under their national transpositions of the EAA. Examples include:

• Germany: The Federal Competence Centre for Accessible IT (BIK BITV-Test framework) informs monitoring; market surveillance responsibilities are distributed across Länder-level authorities depending on product category.
• France: ARCOM (Autorité de régulation de la communication audiovisuelle et numérique) and sector-specific regulators share oversight depending on service type.
• Ireland: The National Disability Authority and the Competition and Consumer Protection Commission share relevant oversight roles.

Each MSA has authority to: investigate complaints from users or competitors; conduct proactive market surveillance audits; issue corrective orders requiring organizations to remediate non-conformances within defined timeframes; impose fines under national implementing legislation; and in severe cases, order withdrawal of non-compliant products from the EU market.

Complaint-Driven and Proactive Enforcement

EAA enforcement operates on two tracks. The first is complaint-driven: any person or organization—including disability advocacy groups, competitors, or individual users—can file a complaint with the relevant MSA. The second is proactive: MSAs are empowered to conduct market surveillance audits without a triggering complaint. Organizations in high-visibility sectors (banking, e-commerce, transport) should assume proactive scrutiny rather than treating enforcement as a reactive risk.

The Role of the EAA Accessibility Statement in Enforcement

The accessibility statement is not merely a best-practice declaration—it is a legal document. An MSA reviewing a complaint will examine the accessibility statement first. A statement that overstates conformance, omits known barriers, or lacks a functional feedback mechanism creates immediate evidentiary problems. Conversely, a statement that accurately documents conformance status, known exceptions with remediation timelines, and operational feedback channels demonstrates good faith and materially affects enforcement outcomes.

European Accessibility Act Certification

The EAA does not establish a formal third-party certification scheme for websites or digital services in the way that, for example, ISO standards operate. Conformance is self-declared, supported by technical documentation. However, several member states have developed national accreditation frameworks, and third-party conformance assessments by qualified accessibility auditors provide evidentiary weight in enforcement proceedings. A documented audit trail—scope, methodology, findings, remediation actions—functions as de facto certification in MSA investigations.

EAA Accessibility Statement Requirements: What Must Be Disclosed

The EAA accessibility statement is a mandatory public disclosure document, not an optional transparency measure. Its contents and structure are defined by the EAA and elaborated in member state implementing legislation. Organizations that publish incomplete or inaccurate statements face elevated enforcement risk, since the statement is the first document an MSA examines when processing a complaint.

Required Elements of an EAA Accessibility Statement

A compliant EAA accessibility statement for a digital service must include:

• Conformance status: A clear declaration of whether the service is fully conformant, partially conformant, or non-conformant with WCAG 2.1 Level AA, with the basis for that determination (e.g., self-assessment, third-party audit)
• Non-accessible content: An enumeration of known barriers, organized by affected content area or user journey, with the specific WCAG 2.1 AA success criterion not met
• Remediation timeline: Specific dates by which known barriers will be addressed—not open-ended commitments
• Alternatives: Where barriers exist that cannot be immediately remediated, accessible alternatives for obtaining the same information or completing the same task
• Feedback mechanism: A named contact (role or email address) for users to report barriers or request accessible alternatives, with a defined response time
• Enforcement escalation: Information on the relevant national market surveillance authority and the process for filing a complaint if the service provider's response is inadequate

Accessibility Statement vs. WCAG Conformance Claim

A WCAG conformance claim—a voluntary declaration formatted according to W3C guidance—is not equivalent to an EAA accessibility statement. The conformance claim addresses technical criteria; the EAA statement addresses legal obligations, known gaps, user recourse, and regulatory escalation paths. Organizations often have the former and lack the latter, creating a compliance documentation gap that is straightforward to close but frequently overlooked.

Maintenance Cadence

The accessibility statement must be kept current. When new barriers are identified—through user feedback, audit findings, or content updates—the statement must be updated within a reasonable timeframe. MSAs treat outdated statements as evidence of inadequate compliance monitoring, which compounds enforcement exposure on the underlying accessibility failures.

EAA vs. Section 508 and ADA Title II: Cross-Jurisdictional Compliance

Organizations operating in both the US and EU markets face overlapping but non-identical accessibility legal frameworks. Understanding where these frameworks align and diverge is essential for designing a compliance program that satisfies both without duplicating effort.

Section 508 and the EAA

Section 508 of the Rehabilitation Act, refreshed effective January 18, 2018, applies to US federal agencies and federally funded entities. Its technical baseline is WCAG 2.0 Level AA. The EAA's technical baseline is WCAG 2.1 Level AA via EN 301 549 V3.2.1 (March 2021). WCAG 2.1 AA is a superset of WCAG 2.0 AA—it adds 17 new success criteria addressing mobile accessibility, low vision, and cognitive accessibility. An organization conforming to WCAG 2.1 AA for EAA purposes automatically satisfies WCAG 2.0 AA for Section 508 purposes; the reverse is not true. Building to the higher standard (WCAG 2.1 AA) satisfies both frameworks simultaneously.

ADA Title II and the EAA

Under the ADA Title II final rule, state and local government entities in the US with populations of 50,000 or more must conform to WCAG 2.1 Level AA by April 24, 2026. This is the same technical standard as the EAA. For private-sector organizations, ADA Title III accessibility obligations are enforced through litigation rather than a final rule mandating WCAG, but WCAG 2.1 AA is the de facto standard applied by courts and the DOJ.

Strategic Implication

Organizations that build their accessibility program around WCAG 2.1 AA—the EAA's standard—position themselves optimally across all three frameworks: EAA, ADA Title II (for relevant entities), and Section 508. Document accessibility, including PDF remediation to PDF/UA-1 and WCAG 2.1 AA, satisfies document requirements under all three. This convergence reduces compliance program cost and complexity for multi-jurisdictional organizations.

Building an Internal EAA Compliance Program: Roles and Processes

Sustained EAA compliance is a program management challenge as much as a technical one. Organizations that achieve durable conformance do so through defined ownership, embedded processes, and clear escalation paths—not through one-time audits.

Required Roles

• Accessibility Lead / EAA Compliance Owner: Accountable for maintaining the EAA compliance program, coordinating audits, managing the accessibility statement, and serving as the MSA contact point. This role requires understanding of WCAG 2.1 AA, EN 301 549, and the organization's service scope under the EAA.
• Development and QA Teams: Responsible for integrating accessibility requirements into sprint acceptance criteria, conducting component-level testing, and running automated accessibility checks in CI/CD pipelines.
• Content and Document Teams: Responsible for producing accessible content natively—structured headings, meaningful link text, alternative text for images—and for routing documents requiring remediation through an established process. RemeDocs integrates directly into document production workflows for teams generating PDFs at volume.
• Legal / Compliance: Responsible for monitoring member state implementing legislation, managing the disproportionate burden assessment process, and coordinating responses to MSA inquiries.

Process Integration Points

• Accessibility acceptance criteria in product backlog and definition of done
• Automated accessibility testing (axe-core or equivalent) in CI/CD pipeline with blocking failure thresholds
• Pre-publication accessibility review for all new document types entering service delivery workflows
• Quarterly review of accessibility statement currency against known barrier inventory
• Annual full conformance audit against WCAG 2.1 AA with third-party validation
• Vendor and third-party component procurement requiring VPAT (Voluntary Product Accessibility Template) or equivalent EAA conformance documentation

The Cost of Deferred Compliance

Organizations that delay EAA compliance until enforcement action is initiated face remediation costs that are 3–5 times higher than proactive compliance programs, based on industry benchmarks from web accessibility remediation projects. Retroactive remediation of large legacy document libraries without a structured process—using RemeDocs or equivalent enterprise-grade tooling—consistently produces the largest cost overruns. The earlier document remediation is scoped and resourced, the more controllable the cost curve.

EAA Compliance Experts: What to Look for When Engaging External Support

Most organizations require external expertise at some phase of EAA compliance—audit, remediation, legal analysis, or program design. The quality and specificity of that expertise varies significantly, and selecting the wrong partner creates false confidence without reducing actual compliance risk.

Audit Expertise

A credible EAA compliance auditor must demonstrate: certification in web accessibility (CPACC, WAS, or equivalent IAAP credentials); documented methodology for manual testing with assistive technology (NVDA, JAWS, VoiceOver, TalkBack); experience with EN 301 549 clause mapping beyond WCAG web criteria; and a deliverable format that maps findings to specific WCAG 2.1 AA success criteria with remediation guidance. Automated-only audits are not sufficient and should not be accepted as conformance evidence in MSA proceedings.

Document Remediation Expertise

PDF and document remediation requires a different skill set from web accessibility. Evaluating a document remediation provider requires: demonstrated PDF/UA-1 validation capability (PAC testing, Matterhorn Protocol verification); evidence of reading order correction methodology; capacity to handle complex document types (multi-column layouts, scanned PDFs, tagged forms); and volume processing capability for organizations with large legacy libraries. RemeDocs specializes in this domain—producing PDF/UA-1 and WCAG 2.1 AA conformant documents at scale, with quality validation integrated into the delivery process.

Legal and Regulatory Expertise

EAA legal counsel must have current knowledge of member state implementing legislation—which varies in fine structures, complaint procedures, and enforcement timelines. General GDPR counsel is not a substitute for EAA-specific expertise. Engaging legal advisors who have reviewed multiple member state transpositions and have experience with MSA procedures is essential for organizations with significant EU market exposure.

Immediate Next Steps for EAA Compliance

Organizations that have not yet achieved documented WCAG 2.1 AA conformance across all in-scope digital touchpoints and documents are operating with quantifiable enforcement exposure. The following five steps represent the highest-priority actions available today.

1. Complete a scope inventory within 30 days. Document every digital product and service placed in the EU market. Classify each against EAA product and service categories. Identify all PDFs and digital documents integral to service delivery. This inventory drives every subsequent compliance decision and is the first item an MSA will request.
2. Commission a WCAG 2.1 AA conformance audit of highest-risk touchpoints. Prioritize primary consumer journeys—account creation, checkout, form submission, document download. Use a methodology that combines automated scanning with manual expert review and assistive technology testing. Receive findings mapped to specific success criteria with severity ratings.
3. Initiate document remediation for in-scope PDFs. Route all in-scope PDFs through a structured remediation process producing PDF/UA-1 and WCAG 2.1 AA conformant outputs. RemeDocs provides the technical depth and volume capacity required for enterprise document libraries. Prioritize documents used in primary service delivery workflows.
4. Publish a compliant EAA accessibility statement. Draft and publish an accessibility statement that accurately reflects current conformance status, lists known barriers with remediation timelines, provides an operational feedback mechanism, and identifies the relevant national market surveillance authority for complaint escalation. Do not publish a statement that overstates conformance—inaccurate statements are evidentiary liabilities.
5. Establish a continuous monitoring process. Integrate automated accessibility testing into your development pipeline, assign ownership of the accessibility statement to a named role, and schedule an annual full conformance audit. Organizations that treat EAA compliance as a one-time project rather than a continuous program will face recurring remediation cycles and persistent enforcement exposure.