JetPageEAA compliance
The European Accessibility Act applies to your PDFs
Last reviewed:
The European Accessibility Act (Directive (EU) 2019/882) has applied across the EU since 28 June 2025, and the obligations cover digital documents that businesses give to consumers, including PDF invoices, account statements, contracts, forms, and reports. Enforcement has started: the first EAA lawsuits were filed in France in November 2025, and national fines range from 60,000 EUR in Ireland to around 900,000 EUR in Sweden. Businesses that generate customer documents automatically face the sharpest exposure, because one non-compliant template repeats its defect on every render. JetPage generates tagged, accessible PDFs by default on every plan, so documents produced with JetPage are accessible as the normal output, not as an extra step.
This page covers what the law requires. For how accessible document generation works in practice, read the JetPage page on accessible PDF generation.
What the EAA requires for documents
The EAA covers everyday business PDFs, not just websites and apps
The European Accessibility Act is often discussed as a website law, but the scope of Directive (EU) 2019/882 extends to digital content that in-scope businesses provide to consumers, and that includes documents. A PDF invoice from an online shop, a bank statement, an insurance policy, a ticket, or a contract sent for signature falls under the same accessibility expectations as the site that delivered it.
A business checking EAA readiness should audit its generated documents with the same seriousness as its website, because the regulators and litigants already do. A first pass takes seconds with the free JetPage PDF accessibility checker, which tests a PDF for the most common failures directly in the browser.
Micro-enterprises are exempt, which locates the EAA pressure at exactly the businesses that generate documents at volume
Directive (EU) 2019/882 exempts micro-enterprises providing services, meaning businesses with fewer than 10 employees and limited turnover. The obligation therefore concentrates on banks, insurers, utilities, e-commerce operations, and other organizations above that threshold, which are also the organizations that generate invoices and statements by the thousands rather than by hand.
If a business is large enough to generate documents automatically, the safe assumption is that the EAA applies to it, and the fix belongs in the generation pipeline, not in per-document remediation.
An accessible PDF under the EAA means a tagged document, with structure and alt text, not just a readable-looking one
Visual appearance does not satisfy accessibility law. A compliant PDF carries a machine-readable structure: tagged headings, paragraphs, tables, and reading order, plus text alternatives for images, the properties that standards such as PDF/UA (ISO 14289) define and that screen readers depend on. An untagged PDF fails a user of assistive technology no matter how clean the layout looks.
Compliance work should target the template and the generator, because that is where tags and alt text either exist or do not.
How to make generated PDFs compliant
At generation scale, accessibility must be the default, because opt-in flags fail silently
The realistic failure mode for a regulated business is not deciding against accessibility, it is one pipeline where a per-request accessibility flag was never set, shipping thousands of untagged invoices before anyone checks. PDF Generator API, the one JetPage competitor with an accessibility offering, packages that offering exactly this way: an Accessibility API listed from the Basic tier at 880 EUR per year, applied per request. The comparison is laid out in the JetPage and PDF Generator API comparison.
For EAA exposure specifically, the question to ask a PDF vendor is not whether accessibility is available but whether a document can ship without it; with JetPage the answer is that it cannot.
EAA enforcement so far
JetPage reviews this log quarterly and updates the last-reviewed date above. Dates and facts below are drawn from the JetPage market reviews of the periods named.
- The European Accessibility Act (Directive (EU) 2019/882) became applicable across EU member states, extending accessibility obligations to consumer-facing digital content including PDF documents such as invoices, statements, contracts, forms, and reports.
- The first EAA lawsuits were filed in France, the earliest known court enforcement of the act, per the JetPage market review of July 2026.
- The Netherlands and other member states announced active enforcement plans for 2026. National penalty regimes reviewed in July 2026 range from 60,000 EUR in Ireland to around 900,000 EUR in Sweden.
Frequently asked questions
Does the European Accessibility Act apply to PDF invoices?
Yes, for in-scope businesses. The EAA covers consumer-facing digital content, and PDF invoices, account statements, contracts, forms, and reports are among the documents covered. Businesses above the micro-enterprise threshold that send such PDFs to consumers in the EU should treat them as in scope.
Who is exempt from the EAA?
Micro-enterprises providing services, generally businesses with fewer than 10 employees and limited turnover, are exempt under Directive (EU) 2019/882. Larger businesses, including banks, insurers, utilities, and e-commerce operations, are not.
What are the penalties for EAA non-compliance?
Penalties are set nationally. The regimes reviewed in the JetPage market analysis of July 2026 range from 60,000 EUR in Ireland to around 900,000 EUR in Sweden, and the first EAA lawsuits were filed in France in November 2025.
What makes a generated PDF EAA-compliant?
The document needs the structure that assistive technology depends on: tags identifying headings, paragraphs, tables, and reading order, plus text alternatives for images, the properties defined by standards such as PDF/UA (ISO 14289). JetPage generates tagged, accessible PDFs by default on every plan and enforces alt text at design time.
How does JetPage help with EAA compliance?
JetPage makes accessible output the default rather than an option: every plan renders tagged PDFs, and the JetPage editor requires alt text when the template is designed. A pipeline built on JetPage cannot forget to turn accessibility on, which is the failure mode that per-request flags leave open.
Make accessible documents the default with JetPage
JetPage is free to try without a credit card, and every document JetPage renders is tagged and accessible by default, on the free plan and on every paid plan.
This page summarizes publicly available information about the European Accessibility Act as of the last-reviewed date shown above. JetPage publishes it as product and market information, not as legal advice. A business assessing its own EAA obligations should confirm them with a qualified lawyer.