Login and strong authentication
One-time codes with short time limits, app approvals and blocked paste fields lock people out. We test every login and confirmation step you put in scope.
Applies to this website and is saved in your browser.
Good to know: this website is built to work well without these switches. They are personal preferences only: they do not change the code and do not replace accessibility, even though overlay widgets promise that. Why overlays do not help · Our accessibility statement
Tip: zoom (Ctrl/Cmd and +), contrast and read-aloud can also be set in your browser and operating system, then for every website.
Plain EnglishIndustry · Banking, insurance, fintech
Consumer banking services are explicitly covered by the European Accessibility Act. We test what your customers depend on: login, onboarding, payments and the account area behind the login, with a keyboard and a screen reader.
Banks and payment providers: consumer banking services are one of the service categories of Directive (EU) 2019/882. National laws have applied them since 28 June 2025. Annex I of the directive adds requirements specific to banking, for example on identification, security and how understandable your information is. Annex I, Section IV, point (e) requires that identification methods, electronic signatures, security and payment services are perceivable, operable, understandable and robust, and that information does not go beyond level B2 (upper intermediate) of the Common European Framework of Reference for Languages (Directive (EU) 2019/882, as of 10 November 2026).
Insurers: insurance is not listed as a separate service category. But e-commerce services are covered: services provided at a distance through websites and apps, at the individual request of a consumer, with a view to concluding a consumer contract (Article 3(30) of Directive (EU) 2019/882). If consumers can take out a policy with you online, that journey falls under this wording, from the quote calculator to the signature. Pages that only inform, pure B2B products and micro-enterprises that provide services are outside the scope. National laws transpose the definition; as of 10 November 2026.
Fintech: if consumers open accounts, pay or borrow through your app, assume you are in scope unless you are a micro-enterprise. The quick check gives a first indication.
Supervision often involves the financial regulator. In France the DGCCRF works with the Banque de France, the ACPR and the AMF; in the Netherlands the AFM covers financial service providers; in Ireland the Central Bank of Ireland covers its sector; in Sweden PTS supervises banking services.
Two questions, one answer
Your industry is already selected. Answer two questions and the EAA check shows an assessment, the reasons and next steps. You can change every answer there.
One-time codes with short time limits, app approvals and blocked paste fields lock people out. We test every login and confirmation step you put in scope.
Long application forms, document uploads and identity checks. Steps run by a third-party provider are tested as your customers see them and marked as such in the report.
Sessions that end without warning cost people their half-finished transfer. Users need a warning and a way to extend.
Transaction lists must be real tables. Charts need the same information in text, and amounts must stay readable at 200% zoom.
Account statements and pre-contractual documents are often PDFs. The reviewer checks the documents you put in scope. PDF checks
Every field needs a visible label and an instruction where the format matters, such as IBAN or date of birth.
For financial transactions, users must be able to check, correct or cancel before they commit. A summary page before “Pay” usually does it.
Session time-outs must warn users and let them extend the time, or be long enough for people who type slowly.
Login must not rely on remembering or transcribing codes without help. Allow paste, password managers and app approval.
Transaction lists, fee tables and account details must be marked up so that screen readers announce rows and column headers.
Many customers bank on a phone or with magnification. Content must work at 320 CSS pixels without scrolling sideways.
Custom controls such as account switchers and date pickers must expose their name, role and state to assistive technology.
We agree pages, journeys and app version. For logged-in areas you give us a test account in a test or staging environment with dummy data.
The scanner covers everything reachable without login. It never logs in, clicks or submits anything.
The reviewer goes through login, onboarding and a transfer or claim with keyboard and screen reader, and decides all 55 criteria.
Findings per criterion with locations, screenshots and fix hints. The certificate states exactly which scope and version was tested.
Yes, and we prefer it. Give us a test account in a test or staging environment with dummy data. Our scanner never logs in; the logged-in part is tested by the reviewer only.
Our audits cover websites and web apps in the browser against WCAG 2.2 AA. We do not currently test native iOS or Android apps and issue no certificate for them. If your app is a web app or shows content from your website, we can test that web content.
The certificate documents a test result for a defined scope and date. It is not a decision of any authority and does not confirm that you meet your legal obligations. It is useful evidence for your internal records and for the people you report to.
It depends on the scope: how many pages, journeys and roles are included. We agree the timeline with you before we start. The main factor is how quickly we get a working test account and test environment.
Dashboards, customer areas, SPAs
Forms, reports, downloads
Duties, deadlines, enforcement
EAA check in five questions