Resources · Sector

Banking & financial services: where blind customers get stuck

From 2023 to 2026 I worked as an Accessibility Analyst at TD Bank, testing a major bank’s own digital services with JAWS and NVDA. The barriers below are the ones that surface again and again across financial services — and every one of them locks a customer out of their own money.

Sign-in and verification

Everything starts here, and it is where the worst barriers live: one-time codes that expire before a screen-reader user can hear and type them; image CAPTCHAs with no workable alternative; app approval prompts that a screen reader announces late, or not at all. A blind customer who cannot sign in does not experience your bank as “mostly accessible” — they experience it as closed.

Statements and documents

Monthly statements delivered as image-only PDFs — pictures of text that a screen reader cannot read. Letters that arrive the same way. Forms that cannot be completed by keyboard. Documents are the quiet barrier in financial services: nobody complains about a statement they cannot open; they just stop trusting the channel. (More in Accessible PDFs: the mistakes everyone makes.)

Finding one transaction

Transaction tables without proper headers, so an amount arrives with no idea what it belongs to. Filters that reset silently. Endless scrolling with no keyboard route to older entries. A sighted customer scans; a blind customer needs structure — and structure is a choice the build either made or didn’t.

Timeouts, errors and recovery

Session-expiry warnings a screen reader never announces, so the customer is logged out mid-task with their work gone. Error messages shown only in colour, or summarised at the top of the page with no path back to the field that needs fixing. Banking involves real consequences for losing your place — recovery has to be designed, not assumed.

Phone trees and card services

The telephone channel is the fallback for every digital barrier — and it has its own: voice menus that rush, options that assume you can see a keypad prompt, activation flows that require reading numbers from the physical card. For a blind customer, the phone channel has to work completely, not eventually.

Apps versus web

The app gets fixed; the website is forgotten — or the reverse. Customers do not experience “channels”; they experience their bank. Parity between app and web is not a launch feature, it is a testing habit.

What good looks like

Blind users testing real tasks — signing in, paying a bill, finding a transaction — at working speed, before release and after fixes. Findings written in business terms: service quality, complaint risk, regulatory exposure, and what to fix first. And fixes that are verified by retesting, not assumed. That is the standard I worked to inside a bank, and the standard I test to now.

More resources · Services