Users trust

European Accessibility Act and WCAG: what fintech must meet

From compliance to quality: the case for accessibility in fintech, in the EU and the US.

Hero Image
AccessibilityWCAGEUUSA
Pavel Chelyuskin photo

Pavel Chelyuskin

Founder

The European Accessibility Act does not name WCAG. It points to the harmonised standard EN 301 549, which for websites and mobile apps means WCAG 2.1 Level AA — the level a fintech product serving EU consumers has had to meet since 28 June 2025. In the US the same bar comes from ADA case law and, for federal vendors, Section 508.

WCAG 2.0 (Web Content Accessibility Guidelines) was first released in late 2008 and introduced the POUR principles: Perceivable, Operable, Understandable, Robust. Today, meeting WCAG is no longer just “nice to have” UX hygiene—it is a regulatory requirement in many markets.

EU and US at a glance

European Accessibility ActADA Title IIISection 508
Who it coversProviders of consumer financial services in the EU — banking platforms, mobile apps, payment services. Microenterprises are exemptPrivate businesses open to the public in the US, banks included; websites and apps are covered through case law and federal guidanceUS federal agencies and the vendors selling to them, fintech included
StandardEN 301 549 → WCAG 2.1 Level AANo named standard; WCAG 2.1 AA is the working baselineWCAG 2.0 AA at minimum; 2.1 AA in practice
Since28 June 2025In force; web and app coverage established by case lawIn force
How it is enforcedNational market surveillance, fines and sanctions set per member statePrivate lawsuits — more than 2,000 filed in a single year by 2025, most settled out of courtProcurement requirements and federal oversight

The European Accessibility Act: which WCAG level, who it covers

The European Accessibility Act (EAA, Directive (EU) 2019/882), which applies in full from 28 June 2025, requires digital accessibility for financial services, including banking platforms, mobile apps, and payment services. The directive does not name WCAG explicitly: it requires services to follow the POUR principles and refers to the harmonised standard EN 301 549, whose web and mobile requirements are aligned with WCAG 2.1 Level AA. WCAG 2.2 is the current W3C recommendation, but the legal reference in the EU stays at 2.1 AA until EN 301 549 is updated. Microenterprises — fewer than ten staff and turnover or balance sheet under €2 million — are exempt from the service obligations (Art. 4(5)). How this lands on a real onboarding screen is one of the cards in our MiCA compliance checklist.

Lawsuits in the EU

Legal cases are still relatively rare, but they are already happening. For example, airline Vueling has reportedly been fined 90,000 euros and lost access to state subsidies for six months over accessibility issues. With the EAA now fully in force, enforcement activity and case statistics are expected to grow in the coming years.

The United States: ADA and Section 508

Title III of the Americans with Disabilities Act (ADA) requires private businesses—such as banks, restaurants, shops, hotels, cinemas, and medical offices—to provide equal access to goods, services, and premises for people with disabilities. While the ADA originally focused on physical accessibility (ramps, parking, etc.), federal guidance and case law now make it clear that banking and fintech websites and apps must also be accessible and are expected to follow WCAG.

Section 508 of the Rehabilitation Act requires federal agencies and their vendors, including fintech providers selling into the federal space, to meet WCAG 2.0 AA at minimum. In practice, many organizations now treat WCAG 2.1 AA as the current baseline.

Lawsuits in the US

Earlier cases often ended without monetary penalties and focused on requiring companies to fix their websites and apps and then report on WCAG compliance. Examples include:

  • Peapod (online grocery), 2014
  • Winn-Dixie (supermarket chain), 2017
  • Domino’s Pizza, 2021
  • Hy‑Vee (COVID‑19 vaccination scheduling site), 2021

Litigation has accelerated. By 2025, more than 2,000 web accessibility lawsuits had already been filed in a single year in the US, with many cases ending in out-of-court settlements.

What teams should do

In real projects, most hands-on accessibility work typically lands with frontend engineers. However, designers and product managers have a lot of influence and should actively steer this work.

Key areas to control in design and product:

  • Readable text with sufficient contrast and proper scaling
  • Sensible use of color, avoiding color-only encoding and pairing statuses with text or icons
  • Thought-through states (hover, focus, active, disabled) that are visible and consistent
  • Clear content structure with headings, lists, and logical hierarchy
  • Descriptive copy for interactive elements, navigation, and error messages

A very helpful resource is Ardvark’s WCAG in Plain English, which explains each WCAG criterion in clear language and lets you filter by role (design, code, content) and other dimensions. This is a good starting point for teams that find the official W3C text too dense.

Figma plugins for accessibility

While designing interfaces in Figma, it is useful to integrate automated accessibility checks into the workflow. In practice, most plugins do not go much further than color contrast checks—but even that is already a meaningful improvement in everyday work.

Popular plugins include:

A common issue with many plugins is that they do not always correctly detect which colors are used for text and backgrounds, which leads to false positives or missed failures. In our agency work, BrowserStack’s toolkit has proven to be the most reliable among the popular options, with fewer detection errors overall.

Bottom line

Accessibility is a competitive advantage. Regulatory pressure is increasing across markets, but the main benefit remains product quality and conversion. Accessible interfaces tend to convert better, especially because people with reduced mobility and older adults often represent between 15% and 30% of the user base, depending on the market.

If you want to know where your product stands on this before someone else tells you, that is what our product health check is for.

Further reading

WCAG

European Union

United States

Figma plugins

FAQ

The EAA itself names no WCAG version. Compliance is presumed when a service meets the harmonised standard EN 301 549, and for websites and mobile apps that standard is aligned with WCAG 2.1 Level AA. That is the level to design and test against in the EU today.

Yes. Consumer banking services, payment services and the websites and mobile apps through which they are delivered are in scope, and the obligations have applied since 28 June 2025. Microenterprises — fewer than ten staff and under €2 million in turnover or balance sheet — are exempt from the service requirements.

Not yet. WCAG 2.2 is the current W3C recommendation and a sensible target for new work, but the EU's legal reference is EN 301 549, which still points to WCAG 2.1 AA. Until the standard is updated, 2.1 AA is what conformity is measured against; the 2.2 criteria are additive, so meeting them does not put 2.1 conformance at risk.

The EAA is a directive with a named technical standard, a fixed application date and enforcement by national authorities. ADA Title III names no standard: the expectation that banking and fintech websites and apps follow WCAG comes from federal guidance and case law, and enforcement runs mostly through private lawsuits — more than 2,000 in a single year by 2025. Section 508 adds a WCAG 2.0 AA minimum for anyone selling to federal agencies.