EAA Compliance Specialists: A Complete Guide to European Accessibility Act Requirements

Who Actually Qualifies as an EAA Compliance Specialist—and Why That Distinction Matters Now

The European Accessibility Act (EAA) imposes legally binding accessibility obligations on businesses operating in EU markets, with enforcement beginning June 28, 2025. Organizations that treat compliance as a checkbox exercise—rather than engaging specialists with verifiable technical and legal depth—face market exclusion, regulatory fines, and document libraries that fail assistive technology at scale. An EAA compliance specialist is not simply a WCAG auditor or a UX consultant: the role demands command of EU Directive 2019/882, EN 301 549 V3.2.1 (March 2021), WCAG 2.1 Level AA, PDF/UA-1 (ISO 14289-1:2014), and the procurement and remediation workflows that translate those standards into defensible, auditable outputs.

This guide defines the role precisely, breaks down every compliance dimension specialists must master, provides an actionable EAA compliance checklist, and answers the most operationally consequential questions compliance directors and IT leads are asking right now.

Answer Block — What Does an EAA Compliance Specialist Do?
An EAA compliance specialist assesses digital products and documents against the requirements of EU Directive 2019/882 and its technical reference standard, EN 301 549 V3.2.1, which incorporates WCAG 2.1 Level AA as its web and document accessibility baseline. The specialist conducts structured audits using automated scanning and manual assistive-technology testing, produces gap analysis reports mapped to specific success criteria, remediates or oversees remediation of non-conformant assets (including PDFs, forms, and e-documents), drafts conforming accessibility statements, and establishes ongoing monitoring workflows. For document-heavy organizations, that remediation work includes tag-tree correction, reading-order repair, semantic structure enforcement, and PDF/UA-1 validation—work that automated checkers cannot fully perform. The output is a documented compliance posture that withstands regulatory scrutiny and market-surveillance audits under member-state enforcement mechanisms. Organizations using RemeDocs benefit from a structured remediation pipeline that maps directly to these specialist deliverables.

What is EAA compliance?

EAA compliance is conformance with EU Directive 2019/882—the European Accessibility Act—which requires that specified products and services be accessible to persons with disabilities. The Directive entered into force in 2019; member states transposed it into national law by June 28, 2022; and the compliance deadline for most in-scope businesses is June 28, 2025. A transitional period extends to June 28, 2030 for some service contracts predating 2025, but new products and services entering the market after the enforcement date must conform from day one.

Scope: Which Organizations and Products Are Covered

The EAA applies to any economic operator—manufacturer, importer, distributor, or service provider—placing in-scope products or services on the EU market, regardless of where the organization is headquartered. Covered product and service categories include:

• Consumer hardware with digital interfaces — computers, smartphones, payment terminals, ATMs, ticketing and check-in machines
• Operating systems with general-purpose computing interfaces
• E-commerce websites and mobile applications used to sell any product or service
• Electronic communications services including real-time text and video relay
• Audio-visual media services and their access features
• E-books, e-readers, and associated software
• Banking and financial services — online banking interfaces, contract documents, and service information
• Passenger transport services — websites, apps, ticketing, and real-time travel information

Micro-enterprises — defined as fewer than 10 employees and annual turnover or balance sheet not exceeding €2 million — are exempt from EAA service requirements, though product obligations still apply to manufacturers at any scale.

Technical Standard: EN 301 549 and WCAG 2.1 Level AA

The EAA does not enumerate specific technical criteria directly; it delegates to harmonized standards. EN 301 549 V3.2.1 (March 2021) is the operative technical standard for ICT accessibility in EU law. Its web and non-web document requirements incorporate WCAG 2.1 Level AA — a W3C Recommendation published June 5, 2018 — as the functional baseline. Compliance teams must assess against WCAG 2.1 AA success criteria organized under the four principles: Perceivable, Operable, Understandable, and Robust.

EAA vs. WCAG: Understanding the Relationship

WCAG is a technical specification; the EAA is a legal instrument. WCAG 2.1 Level AA defines what accessibility means technically. The EAA defines who must achieve it, by when, and with what legal consequences for failure. EN 301 549 is the bridge: it references WCAG 2.1 AA and extends requirements to non-web software, documents, hardware, and support services. An organization that achieves WCAG 2.1 AA conformance on its web content has addressed one dimension of EAA compliance; it must separately address document accessibility, software interfaces, and procedural requirements such as the accessibility statement and feedback mechanism.

WCAG 2.2 — a W3C Recommendation published October 5, 2023 — adds nine new success criteria, including improvements to focus appearance and target size. EN 301 549 has not yet been updated to reference WCAG 2.2, so WCAG 2.1 AA remains the current legal baseline under the EAA. Organizations targeting future-proofing should audit against WCAG 2.2 AA as a voluntary enhancement.

The Four Pillars of WCAG: What EAA Specialists Must Test Against

WCAG 2.1 Level AA is organized under four foundational principles — Perceivable, Operable, Understandable, Robust — each containing guidelines and measurable success criteria. EAA compliance specialists must test against all 50 Level A and AA success criteria. The following breakdown identifies the highest-risk criteria in each pillar for enterprise document and web compliance programs.

Perceivable

Content must be presentable to users in ways they can perceive. For digital documents and web interfaces, this pillar generates the highest volume of failures in automated audits:

• Text alternatives (1.1.1) — Every non-text element, including images, charts, and decorative graphics in PDFs, requires a programmatic text alternative or must be marked as artifact. Missing alt text on figures embedded in PDFs is among the most common PDF/UA-1 failures RemeDocs' remediation pipeline identifies.
• Captions and audio description (1.2.x criteria) — Pre-recorded video requires synchronized captions and, where video carries visual-only information, audio description tracks.
• Adaptable content (1.3.x criteria) — Information conveyed through visual structure—reading order, section hierarchy, table relationships—must be determinable programmatically. In PDFs, this requires a correctly ordered tag tree with appropriate semantic tags: <H1> through <H6>, <P>, <Table>, <TR>, <TH>, <TD>.
• Color contrast (1.4.3) — Normal text must achieve a minimum 4.5:1 contrast ratio against its background; large text (18pt or 14pt bold) requires 3:1.

Operable

Interface components and navigation must be operable without a mouse. The operability pillar is primarily a web and software concern, but it applies to interactive PDF forms and digital documents with navigation elements:

• Keyboard accessibility (2.1.1, 2.1.2) — All functionality, including form fields, interactive elements, and custom controls, must be operable via keyboard alone with no keyboard traps.
• Timing (2.2.x criteria) — Time limits must be adjustable or extendable; session timeouts in authenticated web applications must provide warning and extension mechanisms.
• Seizure safety (2.3.1) — Content must not flash more than three times per second.
• Navigable (2.4.x criteria) — Pages and documents require skip navigation, descriptive page titles, visible focus indicators, and link purpose determinable from context.

Understandable

Information and UI operation must be understandable. This pillar covers language identification — critical for PDF/UA conformance — and error handling in forms:

• Language of page (3.1.1) — The document or page language must be set programmatically. In PDFs, the Lang entry in the document catalog is mandatory for PDF/UA-1 conformance.
• Language of parts (3.1.2) — Passages in a secondary language must have their language identified at the element level.
• Error identification and suggestion (3.3.1, 3.3.3) — Forms that detect input errors must identify the item in error and, where possible, suggest correction.

Robust

Content must be robust enough for interpretation by current and future assistive technologies. This pillar is the technical foundation of PDF/UA-1 and ARIA compliance:

• Parsing (4.1.1) — Markup must have no duplicate IDs, properly nested elements, and complete start/end tags. In PDFs, this maps to structurally valid tag trees without orphaned or duplicate elements.
• Name, role, value (4.1.2) — Every UI component must expose its name, role, and state to assistive technology. In PDFs, form fields require a TU (tooltip/alternative text) entry and correct field-type classification.
• Status messages (4.1.3) — Status messages presented without focus change must be determinable programmatically via ARIA live regions or equivalent mechanisms.

Specialists conducting EAA-aligned audits use this four-pillar structure as the audit taxonomy, mapping each finding to the applicable success criterion, conformance level, and affected asset type before prioritizing remediation.

How to be EAA compliant?

Achieving EAA compliance requires executing a structured program across five work streams: scoping, auditing, remediation, procedural documentation, and ongoing monitoring. Organizations that attempt to compress this into a single-phase website scan consistently underestimate the scope and create liability exposure on the document and software dimensions of the Directive.

Step 1: Define Scope and Inventory In-Scope Assets

Map every customer-facing digital touchpoint against the EAA's covered categories. For a financial services organization, this includes the public website, authenticated banking portal, mobile app, PDF account statements, terms and conditions documents, contract forms, and any third-party embedded services (payment processors, identity verification widgets). Document the asset inventory with version control; EAA enforcement is ongoing, not a one-time audit event.

Step 2: Conduct a Baseline Conformance Audit

A defensible EAA audit combines automated scanning with manual assistive-technology testing. Automated tools — including axe-core, WAVE, and platform-native accessibility APIs — reliably detect approximately 30–40% of WCAG 2.1 AA failures. The remaining failures require human testers using screen readers (NVDA, JAWS, VoiceOver), keyboard-only navigation, and magnification tools. For PDFs and office documents, audit against PDF/UA-1 (ISO 14289-1:2014) using validators such as PAC 3 or Matterhorn Protocol checks, supplemented by screen-reader testing to verify reading order and semantic structure in practice.

Step 3: Remediate Web, Software, and Document Assets

Remediation priority should follow risk exposure: highest-traffic and transactional assets first. For web content, this means correcting heading hierarchy, adding programmatic labels to form controls, fixing color contrast, and implementing skip navigation. For PDFs — which represent a disproportionate share of EAA failures in regulated industries — remediation requires rebuilding the tag tree, correcting reading order, adding alternative text to figures, setting document language, and validating table structure. RemeDocs' PDF remediation process handles these operations at scale, with each remediated document validated against PDF/UA-1 before delivery. Organizations relying solely on automated PDF repair tools (including Adobe Acrobat's built-in accessibility checker) will produce documents that pass automated checks but fail screen-reader testing on reading order and semantic tagging.

Step 4: Draft and Publish an EAA Accessibility Statement

The EAA requires organizations to provide clear, accurate information about the accessibility of their products and services. The EAA accessibility statement must specify: the standard applied (EN 301 549 / WCAG 2.1 AA), the scope of assessment, any known non-conformances with planned remediation dates, accessible alternatives for non-conformant content, and a contact mechanism for users to report accessibility barriers or request accessible alternatives. This statement is a legally required procedural document, not a marketing page — its accuracy is subject to regulatory audit.

Step 5: Establish Continuous Monitoring and Release-Gate Testing

EAA compliance is not a project state; it is an operational requirement. New content, product releases, and third-party integrations introduce regressions. Compliance programs must integrate accessibility testing into CI/CD pipelines, enforce document accessibility standards in content authoring workflows, and conduct periodic manual audits — at minimum annually and after major product releases. Specialist teams using tools like the Level Access platform or RemeDocs' document remediation pipeline establish these continuous monitoring workflows as part of their engagement model.

How much does ADA compliance cost?

ADA compliance costs vary by organization size, asset volume, and existing conformance baseline — but the cost of non-compliance consistently exceeds the cost of proactive remediation. In the U.S. context, ADA Title II now mandates WCAG 2.1 Level AA conformance for state and local government entities, with the compliance deadline of April 24, 2026 for jurisdictions with 50,000 or more in population. While this is a U.S. regulation, the cost benchmarks are directly applicable to EAA compliance planning because the technical work — auditing, remediation, monitoring — is substantially identical.

Cost Ranges by Organization Type

• Initial web accessibility audit — $3,000–$30,000 depending on site complexity, number of templates, and whether the audit includes manual assistive-technology testing. Automated-only audits cost less but produce incomplete findings.
• Web remediation (development labor) — $15,000–$150,000+ for organizations with legacy codebases, custom components, or large content management systems. Organizations with modern component libraries and clean semantic markup typically fall in the lower range.
• PDF and document remediation — $5–$50 per document for professional remediation services, depending on document complexity, page count, table density, and image volume. An organization with 500 complex regulatory PDFs faces a remediation investment in the $10,000–$25,000 range. RemeDocs provides per-document pricing that scales with volume, making budget forecasting straightforward.
• Ongoing monitoring and annual audit — $8,000–$40,000 annually for organizations maintaining a continuous compliance program with quarterly audits and regression testing integrated into release workflows.
• EAA accessibility statement and procedural documentation — $2,000–$8,000 if drafted by legal and accessibility specialists to ensure regulatory accuracy.

The Cost of Non-Compliance

EAA enforcement mechanisms vary by member state, but the Directive requires national market-surveillance authorities to impose proportionate penalties. In the U.S., ADA web accessibility lawsuits exceeded 4,600 federal filings in 2023 alone, with settlement costs ranging from $25,000 to over $1 million for larger organizations when legal fees, remediation under consent decree, and monitoring costs are included. EU enforcement under the EAA adds the risk of market exclusion — a consequence that has no direct U.S. analogue — meaning non-conformant products and services can be required to be withdrawn from EU member-state markets. For organizations with significant EU revenue, that exposure dwarfs the cost of a structured compliance program.

EAA Compliance Checklist: Operational Requirements for Specialists

The following checklist is structured by work stream. Each item represents a distinct deliverable or verified state — not a process step. Specialists should use this as an audit-readiness verification tool, not a project plan.

Scoping and Inventory

• Complete asset inventory documented: all public-facing web properties, mobile applications, PDF and office document libraries, interactive forms, and third-party embedded services
• Micro-enterprise exemption eligibility verified and documented (if applicable)
• Pre-2025 service contracts identified and transitional period applicability assessed
• Data subjects (customers, beneficiaries) in EU member states confirmed for jurisdictional applicability

Technical Conformance — Web and Software

• Automated scan completed against WCAG 2.1 AA using a current rule set (axe-core 4.x or equivalent)
• Manual keyboard-only navigation test completed across all critical user flows
• Screen-reader testing completed with at least two assistive technologies (e.g., NVDA + JAWS on Windows, VoiceOver on macOS/iOS)
• Color contrast ratios verified for all text: 4.5:1 for normal text, 3:1 for large text
• All interactive controls have programmatic labels (not placeholder-only)
• Page language set programmatically on every web page and document
• Focus order is logical and visible focus indicator meets minimum contrast requirements
• All video content has synchronized captions; informational video has audio description
• No keyboard traps identified in any interactive component
• Time-limited sessions have warning and extension mechanisms

Document Accessibility — PDF and Office Formats

• All PDFs validated against PDF/UA-1 (ISO 14289-1:2014) using PAC 3 or Matterhorn Protocol
• Tag tree present and complete — no untagged content outside artifact designation
• Reading order matches visual presentation when traversed by screen reader
• All images have alt text or are marked as artifacts (decorative)
• Tables have header cells tagged as <TH> with scope attributes; complex tables have associated header IDs
• Document language set in catalog Lang entry; language changes marked at element level
• Form fields have TU tooltip entries providing descriptive labels
• Document title set in XMP metadata and Document Information Dictionary
• Bookmarks present for documents exceeding 9 pages
• No security settings that block assistive technology access

Procedural and Legal Requirements

• EAA accessibility statement published and publicly accessible (not behind authentication)
• Statement identifies applicable standard (EN 301 549 V3.2.1 / WCAG 2.1 AA), scope, known non-conformances, and remediation timeline
• User feedback and complaint mechanism operational and monitored
• Accessible alternative contact method provided for any non-conformant service
• Internal accessibility policy and procurement requirements updated to include EAA criteria

Monitoring and Governance

• Accessibility testing integrated into software release pipeline
• Document authoring guidelines published for content teams
• Annual comprehensive audit scheduled
• Vendor and third-party accessibility conformance requirements specified in contracts
• Designated accessibility lead or specialist accountable for ongoing compliance posture

Frequently Asked Questions: EAA Compliance for Specialists and Organizations

What is the difference between EAA and WCAG?

The EAA (EU Directive 2019/882) is a binding legal instrument establishing accessibility obligations for products and services in EU markets. WCAG 2.1 Level AA is a technical specification — a W3C Recommendation published June 5, 2018 — that defines measurable accessibility success criteria. The EAA does not directly enumerate technical requirements; instead, it references EN 301 549 V3.2.1 (March 2021) as the harmonized standard, and EN 301 549 incorporates WCAG 2.1 AA for web and document content. Achieving WCAG 2.1 AA conformance addresses the technical accessibility dimension of EAA compliance but does not satisfy all EAA obligations, which also include accessibility statements, feedback mechanisms, and product documentation requirements.

Does the EAA apply to organizations outside the EU?

Yes. Any organization placing in-scope products on the EU market or providing in-scope services to users in EU member states is subject to the EAA, regardless of the organization's country of incorporation or headquarters location. This applies to U.S.-based SaaS companies selling to EU customers, non-EU e-commerce retailers, and non-EU financial service providers operating in EU member states.

What is an EAA accessibility statement and what must it contain?

An EAA accessibility statement is a required public declaration of a service provider's accessibility conformance posture. Required content includes: the standard applied (EN 301 549 / WCAG 2.1 AA), scope of assessment, specific known non-conformances with planned resolution dates, a mechanism for users to submit accessibility complaints or requests, and contact information for accessible alternative assistance. The statement must be accurate — overstating conformance is a regulatory risk. It should be reviewed and updated whenever significant content or product changes occur.

What does PDF/UA-1 require that WCAG 2.1 does not explicitly address?

PDF/UA-1 (ISO 14289-1:2014) is a document-specific standard that operationalizes accessibility requirements for the PDF format. It requires a complete, valid tag tree (no untagged real content), correct semantic structure tags, document language declaration in the catalog, meaningful document title in metadata, bookmarks for documents over 9 pages, and no security settings that prevent assistive technology access. WCAG 2.1 addresses many equivalent outcomes (text alternatives, reading order, language) but does not prescribe PDF-specific implementation mechanisms. For EAA-compliant PDFs, both standards apply: WCAG 2.1 AA establishes the outcome requirements, and PDF/UA-1 establishes the PDF-specific implementation requirements.

How long does EAA compliance remediation take?

Timeline depends on asset volume, complexity, and existing conformance baseline. Web remediation for a mid-size organization with significant technical debt typically requires 3–9 months of development work. PDF and document remediation at scale — organizations with hundreds or thousands of documents — benefits from specialist services like RemeDocs that process documents in parallel. Procedural requirements (accessibility statement, feedback mechanism, internal policy) can be completed in 2–4 weeks with appropriate specialist support. Organizations beginning compliance work now for the June 28, 2025 enforcement deadline have limited margin; prioritization of highest-traffic and highest-risk assets is essential.

What is the European Accessibility Act text — where can it be found?

The full legislative text of EU Directive 2019/882 on the accessibility requirements for products and services is available in the Official Journal of the European Union. The Directive was published April 17, 2019. Each EU member state has enacted national transposition legislation; the specific national law applicable to a given organization depends on where it operates or where its products are sold. Compliance specialists should reference both the Directive and the relevant member-state transposition law when advising clients.

Immediate Next Steps for Organizations Beginning EAA Compliance Work

Organizations that have not yet initiated a structured EAA compliance program face compressing timelines against the June 28, 2025 enforcement date. The following steps are executable immediately and generate the audit evidence and remediation momentum required for a defensible compliance posture.

1. Complete an asset inventory and scope determination within two weeks. Identify every customer-facing digital product and service exposed to EU users. Classify each against the EAA's covered categories. This inventory becomes the scope document for your audit and the basis for your accessibility statement. Without it, you cannot prioritize or budget accurately.
2. Commission a combined automated-plus-manual audit on your highest-risk assets. Select your highest-traffic web properties and your most-distributed document types (standard contracts, account statements, regulatory disclosures) for immediate audit against WCAG 2.1 AA and PDF/UA-1. Use the findings to produce a prioritized remediation backlog with severity ratings and estimated effort.
3. Engage a PDF and document remediation specialist for your document library. Web remediation and document remediation require different technical competencies. RemeDocs handles PDF/UA-1 remediation at volume, with validated output and screen-reader verification — submit your highest-priority document set for remediation assessment now rather than after the web program is complete.
4. Draft and publish your EAA accessibility statement. Even an interim statement that accurately discloses known non-conformances and a remediation timeline is legally preferable to no statement. Regulators evaluate good-faith compliance effort; an accurate statement with a concrete remediation schedule demonstrates structured intent.
5. Integrate accessibility requirements into your vendor and procurement process. Third-party components, SaaS integrations, and embedded services are your accessibility liability. Update procurement contracts to require WCAG 2.1 AA conformance claims backed by Voluntary Product Accessibility Templates (VPATs) or equivalent conformance reports. Non-conformant third-party content does not exempt you from EAA obligations.