The European Accessibility Act has moved from countdown to compliance. For banks, insurers, and other financial services firms operating in or serving the EU, accessibility has shifted from a best-practice aspiration to a legal requirement baked into day-to-day engineering and QA.
The practical implication is unambiguous: accessibility must be designed, built, and validated into every customer-facing journey, and it must be evidenced through testing artefacts that stand up to regulatory scrutiny.
For legal context, Fredericka Argent, special counsel in the technology regulatory group at Covington in London, set out the scope.
“The EAA imposes various obligations on technology and online service providers… to ensure that the products and services that they offer in the EU are made accessible to consumers with disabilities,” she explained.
Argent added that providers’ “websites and mobile apps [must be] accessible, as well as [providing] accessible information via any support services they may offer.”
Argent also pointed to the role of harmonised standards: EN 301 549, incorporating WCAG, remains the technical backbone that test plans can anchor to while the market aligns on updates.
She noted: “Even if an organisation covered by the EAA cannot or chooses not to fully comply with this standard, it is a useful guide for identifying the technical requirements for achieving accessibility of products and services covered by the legislation.”
“The obligations contain a number of ambiguities regarding how compliance is to be achieved in practice.”
– Fredericka Argent
From a testing-operations standpoint, the EAA is already forcing QA to broaden scope beyond screen-reader checks at release time.
It extends into customer-support flows, documentation, and ticketing systems; it also aligns with EU product-safety-style expectations around traceability, meaning defect management, evidence capture, and release controls need to show a clean line from requirement to test to remediation.
For teams working under change-management pressure, this is not a one-off audit; it is a method. That “method over moment” theme recurs across engineering guidance.
Eric Portis, senior developer experience engineer at Cloudinary, warns that visual content is where many apps will either pass or fail.
“While the EAA impacts many areas of accessibility, visual content presents unique testing challenges and opportunities,” he said. “From images and icons to videos and layout, ensuring visual accessibility is essential, not just for compliance, but for inclusive digital experiences.”
His advice to QA is operational: “With the EAA’s deadline approaching, QA teams need to operationalise accessibility testing,” while broadening the principle: “QA teams play a vital role in creating digital experiences that truly work for everyone.”
Portis went deeper on practice. Image alt-text must be complete and consistent at scale; video players must meet accessibility needs across captions, audio descriptions, and keyboard navigation; colour and contrast require systematic, cross-device verification.
He underlined that automation should be integrated into CI/CD, but not at the expense of real users and assistive technologies: “Accessibility shouldn’t be treated as a one-off audit right before launch. It needs to live in QA workflows, right alongside functional, performance, and security testing.”
Challenges
Resourcing remains a pain point now that the law is live. Rob Mason, chief technology officer at Applause, reported progress in awareness and ownership, but stressed gaps where it matters most.
“Sixty-eight percent of respondents reported lacking the expertise or resources needed to test for accessibility independently or on an ongoing basis,” Mason said.
He added: “Forty-eight percent of respondents don’t have or don’t know if they have processes in place to stop a product release with inaccessible features from going into production.”
Mason’s takeaway for banks leaning on tooling: “Automated and AI testing solutions can support internal efforts, but added investment in external expertise and user feedback, particularly from PWD, is essential.”
Those survey findings align with earlier front-line warnings from Applause’s Paul Hoffman as the deadline neared. “There is a disconnect between prioritisation and delivery,” he said, noting that organisations still lean too heavily on automation that “finds too many false positives,” misses blockers, or over-indexes on low-severity issues.
Yet, many teams still aren’t directly engaging people with disabilities in design and test. “Developing any digital experience, particularly new AI-based features, requires the same level of input from persons with disabilities.”
For banks, the strategic lens matters as much as the sprint plan. Russell Webb, vice president for Europe at Level Access, argued that treating the EAA as a checkbox misses the upside.
“Creating accessible digital experiences is fast becoming a priority for financial organisations,” he stressed, adding that “with 1.3 billion individuals living with disabilities worldwide, ensuring that digital interaction is available to all should be common business sense.”
“Added investment in external expertise and user feedback is essential.”
– Rob Mason
Webb warned that “a surprisingly large number of companies… have not even begun the process,” and set out a testing model built on “manual testing by experienced accessibility professionals” that “should include people with disabilities,” with “live monitoring of user experiences of new software and websites” to sustain compliance post-release.
What should a financial-services QA leader do next? First, assume enforcement and customer expectations are here, not pending.
The legal framing is explicit, and national implementations add layers, from annual accessibility action plans in some jurisdictions to market-withdrawal remedies for non-conformance, so your evidence trail must be audit-ready.
Second, embed accessibility at backlog, design, and code-review phases, then prove it in pipelines where automated checks run continuously and exploratory testing with users of assistive tech is scheduled, repeatable, and funded.
Third, expand your definition of “done” to include visual clarity, keyboard navigation, alternative representations, and support-journey accessibility; treat accessibility defects like broken functionality, because they now carry similar risk.
Finally, financial firms should view compliance as a catalyst, not a constraint. Teams that build accessibility into their QA system of work report cleaner UX for everyone and faster, cheaper fixes upstream.
As Portis put it, the EAA “is a call to design with empathy,” and as Webb emphasised, accessibility is also “a business advantage.” With law and leadership now aligned, the opportunity for QA in banking is to institutionalise accessibility and let the evidence speak for itself in every release.
QA FINANCIAL PODCASTS
Listen to Sudeepta Guchhait on Nasdaq’s new Mimic AI testing platform
QA Financial sits down with Sudeepta Guchhait, Senior Director of Product Framework & Quality Engineering at Nasdaq
——–
Listen to Wesley Scheffel and Robin Rain on Schroders’ DevOps strategy
We catch up with Wesley Scheffel, Head of Cloud Platform and Product Engineering at Schroders, and Robin Rain, Head of Cloud Platform Architecture
——–
Listen to Citi’s Jason Morris on Lightspeed and the future of continuous delivery
Jason Morris, Head of Developer Pipelines for Securities Markets and Banking at Citi, talks about Lightspeed
NEXT MONTH
Why not become a QA Financial subscriber?
It’s entirely FREE
* Receive our weekly newsletter every Wednesday * Get priority invitations to our Forum events *
REGULATION & COMPLIANCE
Looking for more news on regulations and compliance requirements driving developments in software quality engineering at financial firms? Visit our dedicated Regulation & Compliance page here.
READ MORE
- Inside Rabobank: Engineering resilience by design
- Can AI agents finally automate data testing?
- Continuous testing drives DORA compliance
- Why software testing may face a major rethink
- Buy or build? AI rewrites software testing for banks
WATCH NOW
