guide
WAD for finance & banking: requirements, priorities, and audit checklist
WAD compliance for financial services requires applying EU Web Accessibility Directive 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.
Does WAD apply to financial services?
The EU Web Accessibility Directive (Directive (EU) 2016/2102) requires public-sector bodies in all EU member states to make their websites and mobile apps accessible per EN 301 549, with mandatory accessibility statements and a complaints mechanism — operative since September 2018 for new sites and September 2020 for all sites.
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 WAD 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 WAD on a Finance & Banking site
1. Conform to EN 301 549: Which incorporates WCAG 2.1 AA.
2. Publish an accessibility statement: Per Article 7. Templated wording specified.
3. Provide a feedback mechanism: Allow users to flag issues.
4. Cooperate with national monitoring: Each member state samples and audits.
Sources
- Directive (EU) 2016/2102 — European Union
- EAA Directive 2019/882 — European Union
FAQ
Frequently asked questions
Cited answers. Sourced. Updated as standards and case law change.
Does WAD apply to finance & banking websites?
The EU Web Accessibility Directive (Directive (EU) 2016/2102) requires public-sector bodies in all EU member states to make their websites and mobile apps accessible per EN 301 549, with mandatory accessibility statements and a complaints mechanism — operative since September 2018 for new sites and September 2020 for all sites.
What are the most common WAD 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