On 30 July 2026 the European Central Bank published something unusual for a central bank: a list of accessibility features it intends to build into a payment app, written in the plain vocabulary that people who use screen readers and switch devices already know. The digital euro app does not exist yet. It is a proposal, shared with banks and consumer groups, and it will not be tested with real users until a pilot the ECB has scheduled for 2027. Nothing has shipped.
The promise is still worth reading closely, because it names, one by one, the things a banking app should do so that a person with a disability can move money without help. And you do not have to wait for a European app to hold your own bank to that list. The features the ECB named are testable today, in the app on your phone.
What the ECB actually committed to
The ECB says the proposed design “includes best-in-class accessibility features that go beyond the requirements of the European Accessibility Act and related standard EN 301 549.” The European Accessibility Act is European Union law, and EN 301 549 is the technical standard for accessible information and communication technology that sits underneath it. Both set a baseline. The ECB’s claim is that its app aims higher than that baseline.
The specifics are where it becomes useful. The bank says the design “applies the highest level of accessibility requirements under the Web Content Accessibility Guidelines adapted to mobile payment applications, covering perception, operability and cognitive accessibility.” It then lists the features it expects: “enhanced visual design, full keyboard navigation, screen reader support, time-out warnings, simplified language, error prevention and reduced motion settings.”
That last cluster is the interesting part. Keyboard navigation and screen reader support are the features most accessibility rules already require. Time-out warnings, simplified language, error prevention and reduced motion settings speak to cognitive and motor barriers that payment apps routinely ignore. A session that logs you out mid-transfer, a screen that punishes one wrong tap, an animation that makes you queasy, wording no one can parse under stress: these are the barriers that keep people locked out of their own accounts, and they are the ones the ECB has put in writing.
“Like cash, the digital euro will be a public good and, in the digital age, every European should be able to access it on equal terms,” said ECB Executive Board member Piero Cipollone, who chairs the bank’s task force on the project.
The checklist to run against your own banking app
You can test each of these against the app you already use. Open it and try the following.
- Move through it without touching the screen. Turn on your device screen reader (VoiceOver on iPhone, TalkBack on Android) or pair an external keyboard, and see whether you can reach every button, field and confirmation. If a step traps you, or a button has no spoken label, that step is closed to a lot of people.
- Read every label out loud in your head. Does the app tell you what a field wants before you fill it, or only after you get it wrong? Are amounts, dates and payees announced clearly? Screen reader support is not just “the app talks”; it is the app saying the right thing at the right moment.
- Slow down on purpose. Start a transfer, then wait. Does the app warn you before it times out, or does it silently drop you and make you begin again? A time-out warning, with a way to extend the session, is the difference between a delay and a lockout for anyone who reads slowly or types with difficulty.
- Look for plain language. Can you understand what a screen is asking without banking jargon? Simplified language is an accessibility feature, not a courtesy, and it helps people with cognitive and learning disabilities, people in a second language, and anyone who is tired or rushed.
- Try to make a mistake. Enter the wrong amount or an incomplete field on purpose. Does the app catch it, explain it in words, and let you fix it, or does it let the error through? Error prevention that stops a costly slip before it happens is one of the quietest and most important safeguards an app can carry.
- Turn on your device’s reduce-motion setting and open the app again. Do the animations and transitions calm down, or does the screen still slide and bounce? Reduced motion matters for people with vestibular disorders, migraine and motion sensitivity.
- Change your text size and contrast. Does the app respect your system settings, or does the layout break when text gets bigger? Enhanced visual design means the app bends to your eyes, not the other way around.
If your bank’s app fails several of these, that is worth knowing, and it is worth saying to your bank.
What Canada requires of your bank right now
Canadian banks are federally regulated, which puts them under the Accessible Canada Act. The Act’s stated purpose is “to make Canada barrier-free by January 1, 2040,” and it names “information and communication technologies” as one of its priority areas. So a banking app is squarely inside its scope.
We have written before about what this wave of accessibility law actually gets you. What the Act requires today is process, not a specific feature list. Banks must “prepare and publish accessibility plans,” update them at least every three years, “consult people with disabilities” when they do, run “a feedback process” for accessibility, and publish progress reports. The Accessibility Commissioner enforces these duties for banks and can issue notices of violation carrying penalties of up to $250,000. The Act also created a federal body, Accessibility Standards Canada, to develop accessibility standards, but standards are voluntary unless the government turns them into regulations, and there is no mandatory technical standard prescribing app features the way the ECB’s proposal does.
The practical takeaway is the feedback process. Every federally regulated bank must have a published way to receive accessibility feedback. If the checklist above turned up a barrier, that channel is where a specific, named problem goes, and the Act requires the bank to describe in its next progress report how it handled the feedback it received.
The catch, said plainly
The digital euro app is a proposal for a European system, not a product you can download, and not something coming to a Canadian bank. Its features will be validated during a 2027 pilot with testers from the ONCE Foundation for Cooperation and Social Inclusion of People with Disabilities and staff of the ECB and 19 national central banks. It is also only one of several ways Europeans would reach the digital euro; the ECB says people would still be able to use their own bank’s channels instead.
None of that changes what the document is good for here. It is a public, central-bank statement of what an accessible payment app looks like, feature by feature. That list belongs to anyone. You can hold it up against the app in your hand today, and you can ask your own bank why the answer is different.
Frequently asked questions
What accessibility features has the European Central Bank promised in the digital euro app?
The published design lists enhanced visual design, full keyboard navigation, screen reader support, time-out warnings, simplified language, error prevention and reduced motion settings. The bank says the design includes best-in-class accessibility features that go beyond the requirements of the European Accessibility Act and related standard EN 301 549, and that it applies the highest level of accessibility requirements under the Web Content Accessibility Guidelines adapted to mobile payment applications.
Can I download the digital euro app?
No. It is a proposal published on 30 July 2026 and shared with banks and consumer groups, and nothing has shipped. Its features will be validated during a pilot the European Central Bank has scheduled for 2027, with testers from the ONCE Foundation for Cooperation and Social Inclusion of People with Disabilities and staff of the bank and 19 national central banks. It is a European system and is not coming to a Canadian bank.
How can I test my own banking app for accessibility?
Seven checks are set out here. Move through the app without touching the screen, using your device screen reader or an external keyboard. Check whether labels tell you what a field wants before you get it wrong. Start a transfer and wait, to see whether the app warns you before it times out. Look for plain language. Enter a wrong amount on purpose and see whether the error is caught and explained. Turn on your device reduce-motion setting and reopen the app. Change your text size and contrast and see whether the layout holds.
What does Canadian law require of a bank’s app right now?
Canadian banks are federally regulated, which puts them under the Accessible Canada Act, and the Act names information and communication technologies as one of its priority areas. What it requires today is process rather than a specific feature list: banks must prepare and publish accessibility plans, update them at least every three years, consult people with disabilities when they do, run a feedback process for accessibility, and publish progress reports. The Accessibility Commissioner enforces these duties and can issue notices of violation carrying penalties of up to $250,000.
Where do I report an accessibility barrier in my bank’s app?
Every federally regulated bank must have a published way to receive accessibility feedback, and that channel is where a specific, named problem goes. The Act requires the bank to describe in its next progress report how it handled the feedback it received.
Sources
- European Central Bank, “Digital euro app to incorporate highest accessibility standards,” press release, 30 July 2026. https://www.ecb.europa.eu/press/pr/date/2026/html/ecb.pr260730~3b3bfbb565.en.html
- Employment and Social Development Canada, “Summary of the Accessible Canada Act,” Canada.ca. https://www.canada.ca/en/employment-social-development/programs/accessible-canada/act-summary.html
