Accessibility & UX
Most websites exclude 16% of the world’s population by default. The law changed in June 2025. The business case was always there.
Key Takeaways
94.8% of the most visited websites fail WCAG. The EAA and BFSG made accessibility legally mandatory for most e-commerce businesses in June 2025. £17.1 billion in e-commerce revenue is abandoned each year because users with access needs can’t get through. Accessibility is not a compliance layer on top of UX – it is UX.
In this article
There is a version of the accessibility conversation that happens in most organisations. It comes up late in a project. Someone mentions WCAG. A developer checks a contrast ratio. A ticket gets filed. The feature ships.
That version misses what accessibility actually is: a measure of how many people can use what you built. Right now, across nearly the entire web, the answer is: not enough.
What WCAG Is
WCAG – Web Content Accessibility Guidelines – is the international standard for accessible digital content, published by the W3C. It organises requirements around four principles: Perceivable, Operable, Understandable, Robust. Known as POUR.
Each principle breaks into success criteria at three levels. Level A is the minimum – not meeting it means some users simply cannot access your content. Level AA is the practical target referenced in most legislation worldwide, including the EAA and BFSG. Level AAA is the highest level and is not required for entire sites.
In practice, WCAG covers: keyboard navigation for users who cannot use a mouse, sufficient colour contrast for users with low vision, text alternatives for images, logical page structure for screen readers, and accessible forms with correct labels and error feedback. The technical standard referenced in EU legislation is EN 301 549, which incorporates WCAG 2.1 AA.
What it does not cover: the quality of the experience. A site can pass every automated WCAG check and still be confusing and unusable for real people. Compliance is a floor, not a ceiling. That gap is where UX comes in.
94.8% of the top one million homepages have detectable WCAG failures. The average homepage has 51 accessibility errors.
Accessibility – The Numbers
94.8 %
71 %
86 %
~35 %
WebAIM Million · Click-Away Pound Survey · AudioEye 2026
The European Accessibility Act – and the German BFSG
The European Accessibility Act (Directive EU 2019/882) came into force across all 27 EU member states on 28 June 2025. Germany implemented it through the Barrierefreiheitsstärkungsgesetz (BFSG) on the same date. It is the most significant accessibility legislation to affect private-sector businesses in Europe to date.
E-commerce is explicitly in scope. Any service that lets consumers conclude contracts online – websites, apps, checkout flows, customer communications – must meet EN 301 549 / WCAG 2.1 AA. The regulation applies regardless of where the business is based. A US retailer selling to EU consumers must comply.
Who must comply: businesses with more than 10 employees or annual turnover above €2 million. Micro-enterprises providing services are exempt – but micro-enterprises manufacturing products are not.
There is no transition period for websites and online shops. Compliance was required from the date of enforcement.
Penalties: fines up to €100,000 per infringement. Market surveillance authorities can prohibit products or services from being offered. Competitors can issue cease-and-desist orders for non-compliance.
€100k
Maximum fine per infringement under the EAA and BFSG.
E-commerce is explicitly in scope. No transition period applies.
(European Accessibility Act, June 2025)
WCAG and UX
Accessibility and UX are not separate disciplines. The same principles that make a product accessible – clear structure, predictable navigation, readable text, unambiguous feedback – are the ones that make it good.
The mistake most teams make is treating accessibility as a QA task. Something to check at the end. This produces technically compliant interfaces that still fail real users – and misses the more important point: WCAG failures are usually a signal that something in the design needed to be clearer anyway.
Design for access from the start
Contrast, focus states, and touch targets belong in the first design pass – not the QA ticket. Figma has contrast checkers built in. There is no reason to discover these issues at handoff.
Use semantic heading structure
Correct heading hierarchy helps screen readers navigate, improves SEO, and benefits anyone who scans rather than reads. It costs nothing and is one of the most common WCAG failures.
Test with assistive technology
Automated tools catch around 30–40% of WCAG failures. The rest only surface with VoiceOver, NVDA, or keyboard-only navigation. Add at least one manual pass before release.
Publish an accessibility statement
Under both EAA and BFSG, an accessibility statement is a legal requirement – not optional. It should document the current conformance level, known gaps, and a contact for access needs.
+26%
Conversion rate increase within 90 days of accessibility improvements.
Checkout completion improved by +21.9% in the same period.
(Build Grow Scale, Case Study)
The Curb Cut Effect. Features built for users with disabilities consistently improve the experience for everyone. Larger touch targets help anyone tapping one-handed. High contrast helps anyone reading in direct sunlight. Clear error messages help anyone completing a form under time pressure. Closed captions were designed for d/Deaf users – they are now used by the majority of people watching video in public. What gets built for access needs rarely stays a niche feature.
The E-Commerce Opportunity
1.3 billion people globally have a significant disability – 16% of the world’s population (WHO). In Europe, approximately 87 million people. This is not a niche segment. It is the size of Germany and France combined.
The Click-Away Pound survey measures the commercial cost directly. Current estimate for the UK alone: £17.1 billion in annual e-commerce revenue abandoned because users with access needs encounter barriers and leave. 71% of users with disabilities leave a website they find difficult to use. 86% say they would spend more if there were fewer barriers.
These are not users who do not want to buy. They are users who cannot complete the purchase.
86%
of users with disabilities say they would spend more
if websites had fewer barriers.
(Click-Away Pound Survey)
£17.1bn
Annual e-commerce revenue abandoned in the UK alone
because users with access needs encounter barriers and leave.
(Click-Away Pound Survey)
The category of “disabled user” is wider than most teams assume. It includes permanent impairments – visual, motor, cognitive, auditory. It includes temporary situations: an arm in a cast, recovering from eye surgery. And it includes situational limitations: a parent holding a child, a commuter in a noisy environment, someone reading in direct sunlight. By some estimates, accessibility improvements affect closer to 40% of users at any given point.
The business case is concrete. Legal & General redesigned their website for accessibility. Online sales doubled within three months. ROI was 100% within the first year. Removing barriers for users with access needs removes friction for everyone.
If your competitors’ sites are inaccessible and yours is not, you serve a market they cannot reach.
94.8% of the top one million homepages fail WCAG. That means the opportunity is sitting there for businesses that take accessibility seriously before they are forced to.
Sources & Further Reading
These resources directly informed the thinking in this article:
- W3C Web Accessibility Initiative. WCAG 2 Overview. The authoritative overview of the Web Content Accessibility Guidelines, covering all versions, success criteria, and the POUR framework.
- European Commission. European Accessibility Act (EAA). Official overview of Directive EU 2019/882, scope, obligations, and implementation across member states.
- Bundesfachstelle Barrierefreiheit. Das Barrierefreiheitsstärkungsgesetz (BFSG). Official German federal guidance on the BFSG – scope, obligations, and enforcement.
- IHK Region Stuttgart. Barrierefreiheitsstärkungsgesetz (BFSG) tritt im Juni 2025 in Kraft. Practical guidance on BFSG obligations, thresholds, and what online shops must do.
- AudioEye. Web Accessibility Statistics 2026. Data on WCAG compliance rates, failure types, and the prevalence of accessibility errors across the web.
- Texthelp. The £17.1bn Click-Away Pound. The survey measuring lost e-commerce revenue due to inaccessible websites.
- TestParty. The $13 Trillion Disability Market. Overview of global disability spending power and the scale of the market being underserved.
- Level Access. The Curb Cut Effect: How Digital Accessibility Improves UX. How accessibility features consistently benefit a wider audience than they were designed for.
- UsableNet. EAA E-Commerce Requirements. What the European Accessibility Act requires specifically from e-commerce providers.
- Vispero. What’s the Difference Between WCAG, the EAA, and EN 301 549?. How the three standards relate and which applies in which legal context.
René Manikofski is a Senior UX Designer with 10+ years of experience in e-commerce and digital product design across Europe. All articles are based on personal professional experience and supported by AI in writing.