E-Commerce
All websites, mobile apps, online shops, and digital platforms that sell products or services to EU consumers.
A practical guide to what the EAA covers, why enforcement risk varies by country, and how mobile app teams can build credible evidence.
It is a set of regulations that came into force in EU countries in June 2025, enforcing in law that certain digital products must be accessible.
In-scope products must meet the relevant criteria defined in EN 301 549. This standard covers a range of physical and digital consumer products, but for apps and websites, the relevant technical standard is WCAG 2.1 Level AA.
It applies to B2C digital products falling into these categories.
All websites, mobile apps, online shops, and digital platforms that sell products or services to EU consumers.
Video streaming platforms, digital television services, and electronic program guides.
Digital books, publications, and the specialised software used to read and download them.
Customer-facing digital banking portals, mobile banking applications, and electronic financial interfaces.
Fixed or mobile telephony services, internet access providers, VoIP software, and digital messaging apps.
Digital infrastructure and responses to the single European emergency number "112".
Websites, mobile applications, interactive map services, digital ticketing platforms, and real-time travel information systems for air, rail, bus, and waterborne travel.
Micro-enterprises are exempted from legal enforcement, so companies with less than 10 staff and turnover, or balance sheet, that does not exceed €2 million are treated differently.
Larger organisations, regulated services, and teams selling digital services into the EU should not assume an exemption without legal review.
This law applies to all countries in the EU where your product is available. Even if that region is not your primary market, or you do not sell in the local currency or language, you still must comply.
Why it is in-scope: This constitutes an e-commerce service. By offering international shipping to EU members, the site actively targets EU consumers, requiring the entire digital browsing and checkout funnel to meet standards.
Why it is in-scope: This falls under consumer banking services. The EAA explicitly covers digital credit agreements, meaning critical loan terms like dynamic APRs and repayment schedules must be fully screen-reader readable.
Why it is in-scope: Microtransactions, subscriptions, and digital storefronts constitute a consumer contract under e-commerce rules.
Why it is in-scope: Even if the physical service takes place in the UK, the digital storefront provides consumer bookings directly to EU citizens, classifying it as an e-commerce service.
Why it is in-scope: While the software is B2B, client companies may need to deploy accessible tools to their own teams and consumers under EU workplace and service requirements, putting pressure on UK vendors to comply.
Why it is in-scope: The EAA regulates audio-visual media services. While user video uploads may be treated differently, the app's navigation, player controls, and captioning tools still need to be accessible.
Why it is in-scope: The EAA explicitly highlights e-books and dedicated reading software. If a site sells downloadable instructional text documents to EU users, the checkout flow and document structure must meet accessibility rules.
Why it is in-scope: It can constitute an element of passenger transport infrastructure and an interactive payment gateway, making user interactions regulated.
The EAA for digital products relies on self-declaration. All in-scope digital products must publish an accessibility statement within the digital product or a link to the statement online.
The document must include your compliance status, for example conforming to EN 301 549 or WCAG 2.1 AA. This should include a list of any known temporary accessibility issues.
In addition, you must provide an active feedback mechanism, such as an email or form, allowing users to report accessibility barriers.
Enforcement happens via market surveillance and customer complaints. If a regulator receives a complaint from an EU citizen about your app or website, they can launch an investigation and request internal technical documentation and assessment records.
The authority sends an official notice outlining accessibility bugs and gives you a strict deadline, often 30 to 90 days, to fix them. Fines are triggered if you miss the deadline or refuse to make changes.
Failing to publish a valid Public Accessibility Statement, or failing to provide internal technical testing documentation to a market authority within the requested timeframe, can create enforcement risk.
Leaving an accessibility reporting email unmonitored, ignoring complaints filed by disabled consumers, or failing to log and address those complaints can trigger investigation.
Many countries, including France, apply ongoing daily fines often up to €1,000 per day until your software engineering team pushes an update that resolves the specific violations.
Flat penalties for severe or repetitive violations vary by location. For example, Germany's BFSG Enforcement Law issues fines up to €100,000, while other nations cap them closer to €10,000 to €20,000 per violation.
For software and apps, surveillance authorities can legally force Apple and Google to remove your app from the regional App Store entirely, blocking your business from operating in that country until compliance is proven.
In rare, extreme cases of continuous, willful neglect, some countries target company leadership. For example, Ireland's EAA transposition allows corporate directors to face up to 6 months of prison time.
To make a mobile application or website fully accessible, you must build user interfaces that function independently of standard touchscreens or mice. Under global standards like WCAG 2.1 Level AA, digital products must be compatible with assistive technologies, flexible layouts, and alternative input methods.
The foundation of digital accessibility relies on native screen reader optimisation: VoiceOver for iOS, TalkBack for Android, and NVDA or JAWS for desktop browsers. Your code must provide accurate programmatic labels, roles, and values for every user interface component.
Apps and websites must support text reflow and scaling up to at least 200% without breaking the user interface. Content cannot clip, overlap, or become obscured, and layouts should avoid unnecessary horizontal scrolling.
The entire interface must be navigable using standard tab or arrow inputs. Interactive journeys need a logical focus order, visible high-contrast focus indicators, and no keyboard traps in forms, modals, or pop-ups.
Standard text must achieve a minimum contrast ratio of 4.5:1 against its background. Large text and essential graphical components require a minimum ratio of 3:1, and color must not be the only way information is communicated.
Accessibility is now a board-level operational risk, not a design afterthought. The safest message is practical: see the risk clearly, prioritise it sensibly, and fix it in the product. Our audits connect the legal context to the digital journeys that matter: identity, payments, records, checkout, account recovery, bookings and support.
We provide accessibility audit, remediation and reporting support. We do not provide legal advice, and no statement on this site is a legal opinion on obligations in any jurisdiction.