AccessivePath

guide

EAA for finance & banking: requirements, priorities, and audit checklist

EAA compliance for financial services requires applying European Accessibility Act to the specific failure points typical of the finance & banking industry — including mfa flows incompatible with screen readers, statement and tax-document pdfs not tagged, charts and graphs without text alternatives.

Kai Schmidt · IAAP CPACC · Document accessibility specialist (PDF/UA-1)3 min readPublished · Updated

Does EAA apply to financial services?

The European Accessibility Act (Directive (EU) 2019/882) is the EU's prescriptive accessibility law that takes effect 28 June 2025, requiring covered products and services — banking, e-commerce, transport, audiovisual media, ebooks and computer hardware — to meet harmonised accessibility requirements derived from EN 301 549 and WCAG 2.1 AA.

Finance & Banking accessibility — the lay of the land

Banking and insurance are explicitly in EAA scope (Article 2(2)(b) and (e)) with strict 2025 enforcement. In the US, banks have been ADA targets for over a decade; the OCC, Federal Reserve and CFPB have all issued guidance on web accessibility. Multi-factor authentication, statement PDFs, and complex transactional flows are the standard failure points.

Where EAA bites hardest in financial services

• MFA flows incompatible with screen readers

• Statement and tax-document PDFs not tagged

• Charts and graphs without text alternatives

• CAPTCHA blocking screen-reader users

• Inaccessible IVR fallback when web fails

Remediation priorities

• Authentication and account access

• Transaction history and statements

• Payment and transfer flows

• Loan, credit, and insurance applications

• Customer-service chat and IVR

How to comply with EAA on a Finance & Banking site

1. Confirm in-scope status: Determine whether your product/service falls under EAA scope and whether you sell into the EU. Confirm whether micro-enterprise exemption applies.

2. Map requirements to EN 301 549: The harmonised standard EN 301 549 incorporates WCAG 2.1 AA for web/mobile and adds requirements for hardware, software, documentation, and support.

3. Audit and remediate: Run combined automated + manual audit. Remediate at source. Prioritise authentication, payment, search and core transaction flows.

4. Publish an EAA accessibility statement: Per Article 13. Disclose conformance, exceptions claimed (disproportionate burden, fundamental alteration), and contact for complaints. Sample templates available from national bodies.

5. Maintain market surveillance readiness: Keep technical documentation, conformity assessments, and ACR/VPAT current. Be prepared for member-state authority requests.

Sources

FAQ

Frequently asked questions

Cited answers. Sourced. Updated as standards and case law change.

  • Does EAA apply to finance & banking websites?

    The European Accessibility Act (Directive (EU) 2019/882) is the EU's prescriptive accessibility law that takes effect 28 June 2025, requiring covered products and services — banking, e-commerce, transport, audiovisual media, ebooks and computer hardware — to meet harmonised accessibility requirements derived from EN 301 549 and WCAG 2.1 AA.

  • What are the most common EAA failures in financial services?

    MFA flows incompatible with screen readers Statement and tax-document PDFs not tagged Charts and graphs without text alternatives

  • What conformance level should a finance & banking site target?

    WCAG 2.2 Level AA is the consensus target for legal compliance and the level referenced by virtually every national accessibility law.

  • Is banking in scope of the EAA?

    Yes — consumer banking services are explicitly in EAA scope under Article 2(2). All EU-facing consumer banking websites and apps must meet EAA accessibility requirements as of 28 June 2025 (services contracts existing on that date enjoy a transition to 28 June 2030).

  • How do US banks handle ADA web accessibility?

    US banks have been ADA Title III defendants for years. Most large banks now publish accessibility statements, maintain VPATs, and integrate accessibility into product release gates. Federal Reserve and OCC have issued advisory guidance.

  • Can a bank use an accessibility overlay widget?

    No. Beyond the general WCAG-at-source argument, banking-data privacy laws (GLBA in the US, PSD2/GDPR in the EU) preclude third-party widget vendors processing customer-facing data.

Stop guessing. Get the audit a Fortune 500 a11y team would have written.

Free audit on your live URL. No sign-up. IAAP-format report. Ready in hours.

founders@accessivepath.com · +977 9851094056