≈15%fewer support contacts after the Lightyear help centre
Why accessibility stopped being optional.
The legal floor moved in 2025, and most products are still below it.
01 · IN ENFORCEMENT
The deadline already passed.
Level Access's EAA compliance overview is blunt: enforcement began on 28 June 2025, and banking, credit, payments and e-money services are all in scope. If your product takes money from EU consumers, accessibility stopped being optional a year ago.
02 · QUIET FAILURE
Most products fail without knowing it.
WebAIM's Million study found detectable WCAG 2 failures on 95.9% of the top million homepages. These are not exotic bugs. They are contrast, labels and structure: the basics of clear design, missed.
03 · RETROFIT TRAP
Overlays and reports don't fix flows.
A widget can't repair a confusing payment journey, and a findings report is a list of symptoms. Accessibility problems are design problems: focus order, error copy, form structure. They get fixed where they were made, in the product.
What the work can deliver
A design review of your key journeys, onboarding, payments and account servicing, checked against WCAG 2.1 AA criteria.
Contrast, type and colour fixed at the token level in your design system, so every screen inherits the fix.
Form, error and validation patterns that stay clear with a screen reader, a keyboard or a shaking hand.
Focus order, touch targets and reading sequence specified so engineers build it right the first time.
Plain-language passes on money screens: fees, terms and errors people can actually act on.
A prioritised, sequenced backlog your team ships alongside the roadmap, not instead of it.
Selected work
Accessibility holds up when it is part of the product design, not a patch at the end.
Kaspar has an excellent talent, he has a clear vision of what and how to do, and then he makes a perfect use of all the available ways to achieve the goal.
Related notes
Accessibility as product quality, not a patch at the end.
No. I practise accessibility-aware product design: I design and repair the flows themselves against WCAG 2.1 AA, which Level Access notes EN 301 549 incorporates in full for EAA compliance. For formal certification, pair me with an audit firm. Design supports their review.
What happens if we ignore the EAA?
Fines vary by member state. Level Access's overview lists penalties up to roughly EUR 900,000 in Sweden and EUR 75,000 per violation in France. The quieter cost is a product that loses customers who can't read, tap or finish your flows.
Where should I start?
Download my free EAA fintech checklist, or take the five-question bad-day audit on the fintech page. Prefer paper? The bad-day audit is also a free PDF. Fifteen minutes tells you whether you have a problem.
Pricing
Three clear ways to start.
€300Live product teardown: one critical flow reviewed live, with the main issues and next steps identified together.
from €2,500Focused product project: one journey, launch, audit or product question with a defined outcome and scope.
€5,000 per monthEmbedded design support: ongoing senior product design inside your product and engineering team.
Fifteen minutes, no deck, no discovery workshop to book afterwards.
01 · Before
You send a link and a sentence.
I look at your product before we talk, so the call opens on specifics instead of background.
02 · The 15 minutes
You describe what feels stuck.
I tell you what I would look at first, and say plainly whether this is work I am the right person for.
03 · After
A short written summary.
The approach, the scope and the fee if it makes sense to continue. No obligation either way.
See where you stand.
Start with the free EAA fintech checklist. If your journeys need work, accessible fintech design is what I do: read how I work on the fintech page, then write to me.