E-Transfers, If You Can See Them: The Accessibility Gap at Canada's Top Bank — and Across the Big Five - Donna J. Jodhan World-Renowned Blind Advocate

When An Everyday Task Requires A Sighted Helper, Independence Is Already Lost

For more than a year I have tried to complete a simple e-Transfer on the personal banking page of Canada’s top bank. Promises were made; nothing changed. I have now filed a complaint with the Canadian Human Rights Commission. This is not a glitch or a one-off annoyance, it is a warning that accessible banking in Canada still lives too much on paper and not enough in code and customer journeys. Research by IPSOS from March of 2025 reinforces what many of us experience: automated scans catch only part of the problem; banks must test with real users of assistive technology and fix the exact journeys we rely on every day.

Canada led the world in accessible banking hardware. Think of talking ATMs and tactile controls, but we are now lagging in consistent, usable, accessible digital flows. The gap shows up most painfully when blind and low-vision customers try to send or accept e-Transfers. When a task that should take two minutes requires a sighted spouse, a trusted friend, or a trip to the branch, privacy and independence are the first casualties.

This article has four objectives. First, to show the gap between policy and practice through lived examples and current research. Second, to benchmark progress across the Big Five without sugarcoating the pain points. Third, to set out a practical, time-bound fix list that reflects both the research and Canadian realities. And fourth, to call on banks and regulators to publish remediation timelines and test results, not just promises.

I begin here because stakes matter. A single broken flow can decide who controls their own money and who must hand that control over to someone else. My complaint to the Canadian Human Rights Commission (CHRC) signals the seriousness and sets the tone: this is about rights, not convenience. Pairing personal experience with research turns frustration into a roadmap, one that bank leaders, regulators, and customers can follow to measurable results.

From World Firsts To Web Frustrations: Canada’s Promise And Today’s Gap

Canada truly led. In 1997, after a human-rights complaint, the first talking ATM appeared in Ottawa with private audio guidance through headphones, a blanked screen for privacy, and tactile controls. By 2010, voice guidance had become standard across branch ATMs, and peers followed with layouts that respected height and reach, tactile keypads, and high-contrast displays. Those were concrete, measurable changes that made independent banking possible for thousands of us.

Then came the digital pivot. Banks now publish accessibility policies, provide alternate formats like braille and large print, and train staff. Some branches go further with wayfinding technology; for example, hundreds of RBC locations are equipped with BlindSquare beacons to help blind customers navigate. Yet when we move from the lobby to the login, too many of us still have to lean on a sighted spouse, friend, or a trip to the branch just to complete an e-Transfer.

Current research explains why this keeps happening. Inclusive testing across mainstream banking sites, covering blind and low-vision customers, Deaf and hard-of-hearing users, people with mobility disabilities, and neurodivergent customers, shows recurring barriers that map directly to today’s web standards. Automated scans only catch part of the picture; banks have to observe real people using assistive technology and fix the tasks we actually perform, step by step.

That’s why today’s failures feel like backsliding. We proved decades ago that Canadian banks can lead when they decide to; the hardware era shows it. There is no excuse for the online experience to trail behind. When a single e-Transfer flow collapses, all the policy goodwill in the world can’t restore the privacy and independence it takes away.

What Blind And Low-Vision Customers Face Online, Step By Step

Here is what keeps tripping us up, over and over. Tasks are stretched across too many clicks and screens, so assistive-tech workflows break before we reach the finish line. Controls behave in non-standard ways and “more info” links lack clear labels, so we can’t trust what we’re activating or comparing. Pages are cluttered, promotions crowd out the task, creating nonstop “screen reader chatter.” Contrast is weak, customization controls are hard to find, and the basics go missing: proper headings, useful alt-text, and buttons that expose their roles and states.

E-Transfers are where these problems turn from irritating to disabling. A flow breaks the moment a button isn’t announced, a field lacks an exposed label or instruction, or an error message isn’t tied to the exact input that needs fixing. And it’s not just the “send” side; “accept” is often the orphan step, overlooked, under-tested, and out of reach for the very people who need it most.

When there’s no sighted spouse or friend to lean on, the fallback is a trek to the branch for what should be a two-minute task. My very own mini-investigation confirmed this pattern: many of us either hand control over to a sighted helper, or give up independence and privacy at the counter. I rely heavily on my branch and a trusted friend, and accepting e-Transfers has still been a problem. That is not what equal service looks like.

This is why I keep saying scanners aren’t enough. Automated audits surface only part of the picture, often 20 to 40 percent, and they don’t reveal how multi-step tasks actually behave with screen readers, magnifiers, or voice control. Banks need to pair code fixes with inclusive research and manual testing, watching real users complete the exact journeys we depend on, end to end.

The Big Five, Fairly Assessed: Progress, Gaps, Next Steps

Canada’s top bank, the Royal Bank of Canada, is the very institution that helped set the global standard with the first talking ATM in 1997, full voice enablement by 2010, hundreds of branches outfitted with BlindSquare beacons, and on-demand in-branch video interpretation, including ASL. That is genuine leadership. Yet today, its personal banking e-Transfer experience remains inaccessible to me. Leadership in one era does not excuse failures in another; the same resolve that delivered accessible hardware must now be applied to core digital tasks.

TD and CIBC. The Toronto-Dominion Bank (TD) (often “TD Bank Group”) TD deserves credit for a dedicated Video Relay Service hotline with trained agents, continued branch retrofits, and a public Accessibility Adapter to help low-vision and cognitive users online. The Canadian Imperial Bank of Commerce (CIBC) provides braille and large-print statements, free braille/large-print card sleeves so customers can identify cards by touch, and MagnusCards to guide common tasks. These are meaningful supports, but they do not replace the need for clean, consistent online journeys, especially for sending and accepting e-Transfers, where clear labels, predictable controls, and reduced clutter determine whether a task is possible without sighted help.

BMO, Scotiabank, and National Bank. Bank of Montreal (BMO) (often “BMO Financial Group”) has invested in CSA-aligned ATM upgrades, lowered heights, high-contrast screens, illuminated keys, and publishes accessibility plans. The Bank of Nova Scotia (often “Scotiabank”) and The National Bank of Canada align to AODA and the Accessible Canada Act, offer multiple feedback channels, and report on progress. The branch and policy foundations are solid; the unfinished work is in the web and app flows that customers use daily, where small defects, missing labels, inconsistent buttons, weak contrast, still compound into full-blown barriers.

What comes next? Across the Big Five, the mandate is the same: fix the e-Transfer send and accept journeys from end-to-end, publish remediation timelines, and test every release with blind and low-vision users who rely on screen readers, magnification, and keyboard navigation. Standardize interaction patterns, surface the task ahead of promotions, and ensure every control exposes its name, role, and state. Keep a human safety net in place, clearly labeled, easy to reach, until the code is right. That is how promises become outcomes.

Rights, Rules, And Remedies: The Framework That Should Make This Simple

This shouldn’t be complicated. Ontario’s AODA requires accessible customer service and communications. Federally, the Accessible Canada Act covers banks and requires published accessibility plans and updates. ATMs are expected to meet CSA barrier-free standards, and websites and apps should actually meet WCAG success criteria in practice, not just on paper. If a customer can’t complete an e-Transfer without sighted help, the standard isn’t met where it matters most: in the real task.

When internal channels fail, there are clear escalation paths. Customers can pursue the bank’s complaint process under FCAC oversight, and when the barrier amounts to discrimination, they can go to the Canadian Human Rights Commission. Some disputes have reached the courts, including Morand v. Scotiabank, which was sent back for reconsideration. In other words: “we’ll look into it” is not a remedy; timelines and fixes are.

Internationally, the direction of travel is unmistakable. In the United States, the ADA helped cement voice guidance on ATMs and drove a steady stream of web settlements that pushed digital accessibility forward. Europe’s European Accessibility Act adds teeth in 2025 with meaningful fines, reinforcing that accessibility is a requirement, not an optional feature. The business case echoes what research already shows: when digital journeys work for everyone, banks reduce risk and earn trust and growth.

The Messy Middle: Counterarguments, Constraints, And Why They Don’t Absolve Anyone

Let’s address the familiar deflection: “it’s the vendor.” Yes, some failures live in third-party stacks, merchant POS terminals, e-Transfer intermediaries, kiosk software. But banks choose those systems, certify them, and renew those contracts. Procurement is leverage. If a device can’t be operated privately and independently by a blind or low-vision customer, it shouldn’t pass certification. Payments Canada has already documented persistent POS barriers for low-vision Canadians; pretending this sits outside the bank’s responsibility ignores how choices are made.

Awareness gaps create their own barriers. Staff are not always trained to offer alternate formats or to escalate accessibility problems quickly. And we still see painful regressions: new touch-only devices rolling out without audio or tactile alternatives. That is not innovation; it is exclusion packaged as progress. Every time a “modern” interface removes the basic cues and controls we rely on, another customer is pushed back to a counter or a sighted helper.

So what do we do? Bake accessibility into the contract: require WCAG conformance and assistive-tech testing before purchase, with penalties for regression. Publish regression-prevention checklists for every release and rollout. Expose a clearly labeled, accessible path to a human on every critical flow, send, accept, pay, apply, exactly as recent research recommends. Keep ASL/LSQ, relay, and trained agents in the loop as a safety net until the code is right.

None of this is optional if a bank wants to claim equal service. Vendor constraints are real, but they are not a shield against accountability. Choose accessible tools, verify them with real users, and fix what breaks. That’s how we move from excuses to outcomes.

A Practical Roadmap: Fixes In 30 Days, 90 Days, And One Year

In 30 days: Stabilize the journey. Publish a clear remediation timeline for the e-Transfer send and accept pages so customers know what will change and when. Add a visible “Get accessible help now” link on every step that routes to trained agents, relay, ASL/LSQ, and phone, so no one is stranded mid-task. Ship hotfixes for the basics: expose missing labels, correct the focus order, tie error messages to the exact fields that need attention, and remove modal traps. Stand up weekly inclusive testing with blind and low-vision users, including screen-reader power-users, so fixes are co-created, not demoed after the fact.

In 90 days: Reduce cognitive load and standardize patterns. Rework page hierarchy to put the task first and promotions last. Adopt uniform behaviors for buttons and links across the entire flow so keyboard and voice users can predict outcomes. Provide user-controlled contrast and text-size options that respect device settings, no overlays that fight assistive tech or override personal configurations. The goal is a calm, consistent path that a customer can complete once and then repeat with confidence.

In one year: Build it into the culture. Train product and engineering teams in accessible code and content so useful alt-text for data, semantic layouts, and correct roles and states are non-negotiable. Bake assistive features directly into the apps instead of bolting them on later. Publish quarterly accessibility scorecards that report real user outcomes, completion rates for send and accept, drop-offs, time-to-resolution with human support, so progress is visible and accountable.

This phased plan gives executives dates and owners, protects customers now, and prevents tomorrow’s regressions. Thirty days buys safety and dignity; ninety days replaces clutter and surprise with clarity and consistency; one year turns accessibility from a project into standard practice. That is how promises become outcomes, and how independence is restored to the people who need it most.

Access Is Not A Favour: It’s The Starting Point

Canada can still lead, but leadership has to show up on the screens we use every day. We proved what’s possible with talking ATMs and thoughtful branch design; now the work is to deliver the same independence online. The gap is clear: policies look good, but key digital journeys, especially sending and accepting e-Transfers, still trip up blind and low-vision customers. Research backs what lived experience shows: accessibility must be built into the task, not just declared.

The Big Five have the track record and the resources. What’s needed now is discipline: turn policies into working journeys, standardize patterns, remove clutter, and make every control speak its name, role, and state. The research referenced as the basis for this article offers a practical playbook; customers offer proof and partnership; regulators provide guardrails. My ask is simple and measurable: publish your timelines, fix the journeys, test with us, and keep a human safety net in place until the code is right.

For banks, assign accountable executives, publish quarterly updates, and make end-to-end e-Transfer remediation a priority across web and app. For regulators and ombuds: require public remediation plans for critical flows and track progress against clear dates. For customers and advocates: keep reporting barriers and escalate when needed, our voices have closed gaps before and will again. Frustrated, yes; defeatist, never.

Donna J. Jodhan, LLB, ACSP, MBA
Global Leader In Disability Rights, Digital Accessibility, And Inclusive Policy Reform
Turning policy into progress for people with disabilities.