{"id":382017,"date":"2026-04-16T06:11:19","date_gmt":"2026-04-16T06:11:19","guid":{"rendered":"https:\/\/www.newsbeep.com\/nz\/382017\/"},"modified":"2026-04-16T06:11:19","modified_gmt":"2026-04-16T06:11:19","slug":"eaa-compliance-from-deadline-to-qa-discipline","status":"publish","type":"post","link":"https:\/\/www.newsbeep.com\/nz\/382017\/","title":{"rendered":"EAA compliance: From deadline to QA discipline"},"content":{"rendered":"

\"\"<\/p>\n

What began as a countdown to the European Accessibility Act\u2019s June 28, 2025 enforcement date is now turning into a broader compliance and governance story for QA and software testing teams across banking and financial services. <\/p>\n

As firms serving EU customers move from preparation to implementation, accessibility is no longer being treated as a peripheral UX issue or a final-stage check. <\/p>\n

It is becoming a documented, testable, auditable control point that increasingly sits alongside performance, security, and resilience within the software delivery lifecycle.<\/p>\n

A growing push around global accessibility reporting, including the use of Voluntary Product Accessibility Templates (VPATs), is reinforcing that shift. <\/p>\n

A VPAT is a standardised document used to report how accessible a software product is against standards such as WCAG and EN 301 549, effectively turning QA testing outcomes into formal compliance evidence.<\/p>\n

In addition, there are the Accessibility Conformance Reports, which are pushing firms to demonstrate not just intent, but evidence. <\/p>\n

\"\"Fredericka Argent<\/p>\n

For QA leaders, the message is becoming clearer: if accessibility cannot be traced, tested and documented, it may not stand up under regulatory or procurement scrutiny.<\/p>\n

The legal backdrop is explicit. Fredericka Argent, special counsel in the technology regulatory group at Covington in London, explained in a legal analysis that \u201cthe EAA imposes various obligations on technology and online service providers\u2026 to ensure that the products and services that they offer in the EU are made accessible to consumers with disabilities.\u201d <\/p>\n

She pointed out that providers\u2019 \u201cwebsites and mobile apps [must be] accessible, as well as [providing] accessible information via any support services they may offer.\u201d<\/p>\n

For banking and insurance QA teams, that means the scope of accessibility testing extends well beyond a mobile app interface or a website front end. It reaches into support journeys, documentation, ticketing systems, and any digital channel used to deliver services. <\/p>\n

Accessibility must now be designed, built, and validated into every customer-facing journey, and it must be evidenced through testing artefacts that stand up to regulatory scrutiny.<\/p>\n

Traceable accessibility testing<\/p>\n

For all the discussion around regulation, the practical backbone remains technical. EN 301 549, which incorporates WCAG, has emerged as the key benchmark around which teams are being told to organise test plans and evidence trails.<\/p>\n

Argent noted that \u201cthe Commission determined that EN 301 549 should be updated to bring it into alignment with the requirements of the EAA, rather than drafting a new standard from scratch.\u201d <\/p>\n

Even amid uncertainty over implementation, she said that \u201ceven 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.\u201d<\/p>\n

That is important for QA teams because the EAA is not simply asking firms to say they care about inclusive design. It is demanding a repeatable method for proving that accessibility has been addressed. <\/p>\n

The regulation\u2019s structure, in fact, mirrors aspects of EU product safety law. Argent warned that \u201centities in the product supply chain must\u2026 ensure that products placed on the EU market remain in conformity with the EAA.\u201d<\/p>\n

She added: \u201cWhere non-conformance is identified, these entities must ensure that \u2018corrective measures\u2019 are taken\u2026 or report the non-conformance to \u2018competent national authorities\u2019.\u201d<\/p>\n

\u201cAccessibility is more than a regulatory imperative, it\u2019s a business advantage.\u201d<\/p>\n

\u2013 Russell Webb<\/p>\n

For testing teams in banks, insurers and fintechs, that raises the bar on traceability, release controls, and defect management. <\/p>\n

Accessibility defects can no longer sit outside mainstream QA governance. They have to be tracked from requirement to remediation, with evidence capable of supporting internal reporting, client due diligence and, increasingly, formal accessibility disclosures.<\/p>\n

That is where the growing focus on VPATs becomes relevant. As more firms look to standardise global accessibility reporting, QA teams are finding themselves closer to the centre of compliance documentation. <\/p>\n

A VPAT may be framed as a reporting document, but in practice it rests on the underlying quality of the testing evidence behind it. In regulated sectors such as financial services, that turns accessibility reporting into a QA issue as much as a legal or procurement one.<\/p>\n

Urgent compliance landscape<\/p>\n

One complicating factor for internationally active banks and financial services firms is that EAA compliance is not entirely uniform across Europe. <\/p>\n

Russell Webb, vice president for Europe at Level Access, pointed out that \u201ceach of the 27 EU Member States has implemented the EAA through its national legislation, which may include additional requirements or specific penalties.\u201d<\/p>\n

Meanwhile, Derrin Evers, senior solution consultant at Deque Europe, made a similar point. \u201cSome countries, like Ireland, have already established their own regulations, while others, such as Belgium, have made slower progress,\u201d he said. <\/p>\n

\"\"Russell Webb<\/p>\n

\u201cThis inconsistency means financial services providers need to track regulatory changes in each country to avoid potential penalties.\u201d<\/p>\n

That cross-border complexity matters for firms with multiple digital platforms, shared engineering teams, and regionally distributed customer bases. <\/p>\n

Evers stressed that \u201cthe EAA doesn\u2019t only affect EU-based businesses. It applies to non-EU companies providing financial services to customers in the EU.\u201d <\/p>\n

For financial institutions, he added, \u201cthe compliance process involves more than just ticking boxes,\u201d and requires them to be \u201ctransparent about how their digital services comply with the EAA\u2019s accessibility requirements, providing clear documentation and evidence of their adherence.\u201d<\/p>\n

His warning on enforcement was blunt: \u201cThe EAA requires that penalties be \u2018effective, proportionate, and dissuasive\u2019,\u201d as he added that \u201cthe stakes are high, and financial institutions must act quickly to ensure compliance.\u201d<\/p>\n

Webb, meanwhile, cautioned that many firms were still behind as the deadline approached. \u201cWe are aware of a surprisingly large number of companies that have not even begun the process of taking action to ensure compliance,\u201d he said.<\/p>\n

Accessibility moves left <\/p>\n

If the legal picture is sharpening, the operational response is also becoming more defined. One of the clearest themes across the accessibility debate is that QA teams are being pushed to move earlier and think more broadly.<\/p>\n

The EAA, as one explainer put it, means software testing must now \u201cprioritize accessibility at every stage of the software development lifecycle.\u201d <\/p>\n

That has practical implications for how banking and insurance teams define readiness, risk and release quality.<\/p>\n

Test cases are expanding to include visual impairments, like colour blindness and low vision, auditory disabilities, motor impairments, cognitive disabilities, and seizure risks, while teams are being told to incorporate screen readers like NVDA or JAWS, magnification software, speech-to-text tools, and keyboard-only navigation testing.<\/p>\n

\"\"Eric Portis<\/p>\n

Eric Portis, senior developer experience engineer at Cloudinary,framed the shift in especially practical terms. \u201cWith the EAA\u2019s deadline approaching, QA teams need to operationalise accessibility testing,\u201d he said. <\/p>\n

He also pushed for accessibility to be handled as a first-class engineering concern: \u201cAccessibility shouldn\u2019t be treated as a one-off audit right before launch. It needs to live in QA workflows, right alongside functional, performance, and security testing.\u201d<\/p>\n

That message lands clearly in financial services, where release processes are already tightly bound to evidencing controls. <\/p>\n

If accessibility now belongs in the same operational category as other release-critical requirements, then defects tied to keyboard navigation, screen reader compatibility, captions or contrast can no longer be sidelined as cosmetic issues.<\/p>\n

Portis argued that this wider lens is especially important for visual media. \u201cWhile the EAA impacts many areas of accessibility, visual content presents unique testing challenges and opportunities,\u201d he said. <\/p>\n

\u201cFrom images and icons to videos and layout, ensuring visual accessibility is essential, not just for compliance, but for inclusive digital experiences.\u201d<\/p>\n

He added that \u201cQA teams should ensure cross-device compatibility, verifying that players function smoothly across desktops, tablets, and mobile devices while supporting assistive tools like screen readers and page zoom.\u201d <\/p>\n

And while automation can help, he stressed that \u201cmost importantly, accessibility features should be tested not just with automated tools but with real users who rely on assistive technologies. This is where the most meaningful insights are found.\u201d<\/p>\n

Over-reliance becomes a risk<\/p>\n

That balance between automation and human-led testing has become one of the most important fault lines in the accessibility discussion.<\/p>\n

Automation is clearly gaining ground. Earlier analysis noted that frameworks such as AXE, Wave, or Lighthouse are becoming more embedded in CI\/CD pipelines, while Portis said AI tools can \u201cautomate and streamline the process\u201d of auditing media for accessibility gaps and even help generate \u201cfirst-pass descriptions for review.\u201d<\/p>\n

But across the sector, concerns remain that firms are leaning too heavily on tooling without the right expertise, user feedback loops, or escalation processes around accessibility defects.<\/p>\n

Paul Hoffman, senior manager at Applause, said the data showed a clear gap: \u201cThere is a disconnect between prioritisation and delivery.\u201d He added that although accessibility is often treated as a high priority, many companies remain underprepared, and only a small minority report having plentiful internal expertise and resources.<\/p>\n

\"\"Rob Mason<\/p>\n

He was particularly critical of the limits of current automation approaches. \u201cTool finds too many false positives,\u201d he said, quoting the most common complaint among users dissatisfied with automated accessibility tools. Other concerns included: \u201cTool finds too many low severity issues,\u201d and \u201cTool isn\u2019t finding blockers.\u201d<\/p>\n

Rob Mason, chief technology officer at Applause, pointed to the same problem from a resourcing angle. \u201cSixty-eight percent of respondents reported lacking the expertise or resources needed to test for accessibility independently or on an ongoing basis,\u201d he said. <\/p>\n

Mason added: \u201cForty-eight percent of respondents don\u2019t have or don\u2019t know if they have processes in place to stop a product release with inaccessible features from going into production.\u201d<\/p>\n

His conclusion was that \u201cautomated and AI testing solutions can support internal efforts, but added investment in external expertise and user feedback, particularly from PWD, is essential.\u201d<\/p>\n

That matters especially in banking, where teams often assume governance is stronger than it really is. If organisations cannot confidently block inaccessible releases, then accessibility remains a stated priority rather than an embedded control.<\/p>\n

User-centred testing <\/p>\n

Another recurring weakness is the failure to involve people with disabilities directly in design and testing. That gap has become harder to defend as accessibility expectations mature.<\/p>\n

Hoffman warned that \u201cnearly a fifth of those who state that their organization practices inclusive design report that they do not directly engage with people with disabilities.\u201d <\/p>\n

\"\"Paul Hoffman<\/p>\n

He added: \u201cDeveloping any digital experience, particularly new AI-based features, requires the same level of input from persons with disabilities.\u201d <\/p>\n

His broader conclusion was that \u201corganisations must invest in ensuring that diverse input is integrated across the entire product development lifecycle.\u201d<\/p>\n

Webb took a similar line on the testing model itself. \u201cA comprehensive audit involves manual testing by experienced accessibility professionals. Ideally, this team of testers should include people with disabilities,\u201d he said.<\/p>\n

Portis also made the case that real-world validation is where accessibility efforts either hold up or fall short. \u201cQA teams play a vital role in creating digital experiences that truly work for everyone,\u201d he said, adding that \u201cthe EAA is a call to design with empathy.\u201d<\/p>\n

For financial institutions, that points to a wider evolution in QA practice. Accessibility testing is becoming more user-centred, more scenario-based, and more closely tied to lived experience rather than static checklist completion. <\/p>\n

In sectors where customer trust and regulatory scrutiny are both high, that makes the quality of the testing approach just as important as the quality of the final product.<\/p>\n

\u201cThe EAA is a call to design with empathy.\u201d<\/p>\n

\u2013 Eric Portis<\/p>\n

For all the focus on fines, market bans and compliance deadlines, many of the strongest advocates are now trying to shift the discussion away from narrow legalism.<\/p>\n

Webb said \u201ccreating accessible digital experiences is fast becoming a priority for organisations,\u201d and added that \u201cwith 1.3 billion individuals living with disabilities worldwide, ensuring that digital interaction is available to all should be common business sense.\u201d <\/p>\n

He concluded that \u201caccessibility is more than a regulatory imperative, it\u2019s a business advantage.\u201d<\/p>\n

Portis pushed the point further. \u201cPrioritising accessibility across design, development, and QA isn\u2019t just about meeting legal requirements,\u201d he said. <\/p>\n

\"\"<\/a><\/p>\n

The EAA, in his view, \u201cis about extending reach to more audiences, building brand trust and driving revenue. Ultimately, it\u2019s about honouring the web\u2019s core promise as a space where everyone can communicate, learn, and do business together.\u201d<\/p>\n

That broader framing is likely to resonate with financial services leaders trying to connect regulatory demands with commercial outcomes. <\/p>\n

Better accessibility can reduce friction in onboarding, improve usability in digital channels, and strengthen trust among customers who increasingly expect inclusive design as standard. <\/p>\n

For QA teams, though, the immediate implication is more operational: accessibility is moving from principle to proof.<\/p>\n

As the EAA beds in and firms look to formalise how they communicate accessibility posture through mechanisms such as VPATs and conformance reporting, industry insiders agree the job of QA becomes more central, not less. <\/p>\n

Accessibility must be continuously tested, documented, monitored and defended. In banking and insurance, that means the era of treating it as an optional extra is over. Or, as one insider put it, accessibility testing is now \u201ca legal responsibility, not a discretionary feature.\u201d<\/p>\n

\"\"<\/p>\n

\"\"<\/p>\n

Why not become a QA Financial subscriber? <\/p>\n

It\u2019s entirely FREE<\/p>\n

* Receive our weekly newsletter every Wednesday * Get priority invitations to our Forum events *<\/p>\n

REGISTER HERE TODAY<\/a><\/p>\n

REGULATION & COMPLIANCE<\/p>\n

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<\/a>.<\/p>\n

READ MORE<\/p>\n

WATCH NOW<\/p>\n

\"\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

QA FINANCIAL PODCASTS<\/p>\n

\"\"<\/p>\n

\"\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"What began as a countdown to the European Accessibility Act\u2019s June 28, 2025 enforcement date is now turning…\n","protected":false},"author":2,"featured_media":382018,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[111,139,69,145],"class_list":{"0":"post-382017","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-technology","8":"tag-new-zealand","9":"tag-newzealand","10":"tag-nz","11":"tag-technology"},"_links":{"self":[{"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/posts\/382017","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/comments?post=382017"}],"version-history":[{"count":0,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/posts\/382017\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/media\/382018"}],"wp:attachment":[{"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/media?parent=382017"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/categories?post=382017"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/tags?post=382017"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}