European Accessibility Act
EAA PDF Compliance: What Organisations Need to Know
The European Accessibility Act has been in force since 28 June 2025. For regulated organisations publishing PDFs, compliance is no longer optional. This page explains what the EAA requires, which organisations are affected, and what it means for your documents.
The regulatory requirement
What the EAA requires for PDF documents
The European Accessibility Act establishes a legal requirement for organisations in scope to make their digital products and services accessible to people with disabilities. For organisations that publish PDFs as part of a regulated service, including banks, insurers, and other financial services providers, this means those documents must meet EN 301 549, the European accessibility standard for ICT. EN 301 549 incorporates WCAG 2.1 Level AA and PDF/UA as the applicable technical requirements for PDF files.​
​
-
The EAA applies to private sector organisations providing services in the EU, including financial services, banking, insurance, and utilities
-
PDFs published as part of a regulated service, such as account statements, policy documents, annual reports, and terms and conditions, must be accessible
-
EN 301 549 is the technical standard organisations must meet to demonstrate EAA compliance for digital content including PDFs
-
Non-compliance with the EAA can result in penalties, which vary by member state but can reach up to 100,000 EUR or 4% of annual revenue depending on jurisdiction
-
The EAA deadline was 28 June 2025, meaning organisations subject to the Act are already required to comply
Who Is Affected
The EAA applies across financial services, banking, insurance, and utilities
The EAA covers a wide range of private sector organisations providing services to consumers in the EU. Financial services firms are among the most directly affected, as they routinely publish high volumes of PDFs as part of their regulated services. Banks must ensure account statements and product information are accessible. Insurers must make policy documents and terms accessible. Fund managers and investment firms must address fund factsheets, reports, and disclosures. Utilities providers must make bills, contracts, and customer communications accessible. Organisations that rely on legacy document production workflows are likely to face the greatest remediation challenge.
The compliance requirements
Three things EAA PDF compliance requires in practice
Demonstrating EAA compliance for PDF documents is not a single action. It requires organisations to address the technical quality of their documents, the processes that produce them, and their ability to evidence conformance when required.
Accessible Document Output
Every in-scope PDF must meet the technical requirements of EN 301 549, which means conforming to WCAG 2.1 Level AA and PDF/UA. Documents must be correctly tagged, have logical reading order, include alternative text for images, and carry the required metadata. This applies to new documents and, depending on interpretation, to documents already in circulation.
.png){kind=small}
Repeatable Remediation Processes
One-off remediation of existing documents is not sufficient for ongoing compliance. Organisations need processes that ensure every new document produced meets accessibility standards at the point of publication. For organisations producing high volumes of PDFs this requires automated remediation tooling integrated into existing document workflows.
.png){kind=small}
The Ability to Evidence Compliance
Regulators and national enforcement bodies may require organisations to demonstrate that their documents meet the required standards. This means being able to produce conformance records, audit trails, and evidence of the remediation process applied to specific documents. Organisations should ensure their remediation workflow generates this evidence as a matter of course.
How to approach compliance
A practical path to EAA PDF compliance
Audit your current document estate
Identify which PDFs are in scope under the EAA and assess their current accessibility status. This means testing a representative sample against EN 301 549 requirements to understand the scale of remediation needed. Many organisations find that the majority of their existing PDFs fail basic accessibility requirements.
Remediate existing documents
Train staff and integrate your systems
Address the backlog of non-compliant PDFs by applying the tagging, reading order, alternative text, and metadata required by PDF/UA and WCAG 2.1 Level AA. For large document volumes, automated remediation tooling is essential. All remediated documents should be reviewed by a human before being published or redistributed.
Fix the production process
Ensure that newly created documents meet accessibility standards before they are published. This requires integrating accessibility checks and remediation into the document production workflow so that non-compliant documents cannot reach customers. A reactive remediation approach will not sustain compliance at volume.
Maintain evidence of conformance
Keep records of which documents have been remediated, when, and against which standard. This creates an audit trail that can be used to demonstrate compliance to regulators or enforcement bodies if required.