Europe’s Accessibility Law Reaches the Checkout

An online shop can look finished and still make the sale impossible. The product page loads, the photographs are polished and the payment provider is connected. Then keyboard focus disappears inside the address form, an error is announced only by colour, or a screen reader reaches an unlabeled payment button.

That failure is often filed as a design defect. In Europe it can also be a market-access and consumer-rights issue.

Since 28 June 2025, EU Member States have been required to apply national measures transposing Directive (EU) 2019/882, widely known as the European Accessibility Act. The Directive covers specified products and services, including e-commerce, consumer banking and parts of electronic communications and passenger transport. More than a year after the application date, accessibility belongs in operating reviews, supplier contracts and release decisions—not in a promise to fix the website later.

E-commerce means the journey to a consumer contract

The Directive defines an e-commerce service around a commercial outcome. It concerns a service provided at a distance, through websites and mobile-device services, electronically and at the consumer’s individual request, with a view to concluding a consumer contract.

That definition makes the checkout an obvious focal point, but not the only one. A consumer may need to identify the product, understand its price and conditions, choose a delivery method, create or avoid creating an account, enter personal details, correct an error, authenticate a payment, receive confirmation and contact support. A barrier anywhere in that chain can prevent the contract.

Other covered services include consumer banking services, e-books and their dedicated software, electronic communications services, access to audiovisual media services, and specified information and ticketing elements of air, bus, rail and waterborne passenger transport. Covered products include consumer computer hardware systems and operating systems, certain self-service terminals, consumer equipment used for electronic communications or audiovisual access, and e-readers.

The list is specific. The law should not be described as applying identically to every website, every business-to-business portal or every digital product. A company should map the exact product or service, the customer, the countries where it is offered and its role in the supply chain against the relevant national implementation.

A company outside the EU cannot stop the review at its address

A startup in the United States, United Kingdom, Canada, Australia, Singapore, Sri Lanka or another non-EU market may sell through an EU storefront, offer a consumer subscription in Member States or supply a product placed on the EU market. The Directive’s definitions and duties concern economic activity on the Union market, with different responsibilities for manufacturers, importers, distributors and service providers.

That does not mean every overseas website is automatically covered. It means the registered office alone is not a reliable scope test. The business must examine where the covered service is provided, who the consumer is, how the contract is concluded, which entity is the legal provider and how national law has transposed the Directive.

A marketplace creates another layer. The platform, merchant, payment provider, identity service, delivery selector and customer-support tool can each control a part of the journey. Legal responsibility cannot be allocated by an editorial article, but operational responsibility can be made visible: every critical component needs an owner, an accessibility requirement and a tested fallback.

The microenterprise exemption is narrower than the word ‘small’

The Directive exempts microenterprises that provide services from the service accessibility requirements. It defines a microenterprise as one employing fewer than 10 people and with annual turnover not exceeding €2 million or an annual balance-sheet total not exceeding €2 million.

A founder should not turn that into a general small-business exemption. The treatment of covered products is different. Group relationships, headcount, financial thresholds, the identity of the service provider and national transposition all matter. A growing company can also cross a threshold, while a retailer or platform may contractually require accessibility from suppliers regardless of whether a statutory exemption applies to one party.

There are also provisions dealing with fundamental alteration and disproportionate burden. These are not informal labels for work that is inconvenient. The Directive requires an assessment against criteria, documentation and renewed assessment in relevant circumstances. A business relying on such a provision should use qualified legal and accessibility advice in the Member State concerned.

Transition clauses are not a universal five-year holiday

The Directive contains transitional measures. It allows service providers, until 28 June 2030, to continue providing services using products they were already using lawfully before 28 June 2025. Service contracts agreed before the 2025 application date may continue without alteration until they expire, but not for more than five years from that date. Separate rules address existing self-service terminals.

These provisions are tied to specific products, contracts and facts. A newly redesigned checkout, a new service, a replacement terminal or a fresh consumer contract should not be treated as automatically protected by a headline about 2030. The correct transition analysis belongs in the launch record.

An accessible checkout is a product, not a compliance page

The useful question is not whether the footer contains an accessibility link. It is whether a customer can complete the same commercial task with different ways of seeing, hearing, moving, understanding and entering information.

Begin with keyboard operation. Can a person reach every interactive control without a mouse, see where focus is, open and close menus, select delivery, edit the basket and submit payment without becoming trapped? W3C explains that keyboard availability also supports assistive technologies that emulate keyboard input.

Then test names and relationships. A screen reader needs meaningful labels for search, quantity controls, address fields, discount codes and payment actions. Headings should describe the page structure. Product images that carry information need useful alternative text; decorative images should not create noise.

Error recovery deserves its own test. If a card, postcode or required field is rejected, the message should identify the problem in text, be connected to the field and make correction possible without losing valid information. Colour alone should not distinguish success from failure. Time limits, verification codes and security challenges need accessible handling and appropriate alternatives.

Zoom and reflow expose another class of barriers. Text, controls, totals and legal information should remain usable when enlarged or viewed on a narrow screen. A cookie banner, chat widget or sticky promotion should not cover the action needed to continue.

Finally, test the handoffs. A shop may be accessible until it redirects to an inaccessible payment page, identity check, booking widget or support portal. From the customer’s perspective, the purchase is one experience. From the operator’s perspective, each vendor needs acceptance criteria, incident routing and evidence that updates will not silently reintroduce barriers.

Automated scans find defects; people find failed journeys

Automated tools can identify missing labels, duplicate identifiers, certain contrast problems and other machine-testable issues. They are valuable in development pipelines because they can prevent known defects from returning.

They cannot determine whether a product description is understandable, whether focus moves sensibly after an error, whether a screen-reader user can compare delivery options or whether the support alternative actually works. W3C states plainly that no tool alone can determine whether a site meets accessibility guidelines and that knowledgeable human evaluation is required.

That makes disabled people part of product quality, not the audience for a final demonstration. Recruit participants with varied access needs, compensate them fairly, provide accessible research materials and include their findings in prioritisation. One screen-reader user cannot represent every blind person; one wheelchair user cannot represent every motor-access need; and disability also includes hearing, cognitive, neurological and speech-related access.

The accessibility statement should describe evidence, not ambition

For covered services, the Directive requires information explaining how the service meets accessibility requirements, made available in writing and orally, including in an accessible manner. Annex V describes information that should appear in terms and conditions or an equivalent document, including a general description, explanations necessary to understand operation and evidence of conformity.

A statement should therefore identify the service and its relevant standard or method, describe known limitations accurately, provide an accessible contact route and explain how feedback is handled. A claim of full compliance should not be copied from a template when the underlying evaluation does not support it.

Keep the supporting record: scope decision, design requirements, test plan, defect log, user-research evidence, supplier assurances, release sign-off and corrective actions. Accessibility changes as content, code, payment flows and third-party components change. The evidence needs a maintenance owner.

Accessibility already extends beyond one European rule

The European Accessibility Act is not a worldwide accessibility code. The United States Department of Justice separately explains that businesses open to the public must ensure that goods and services provided online are accessible under the Americans with Disabilities Act’s general requirements. Australia’s Human Rights Commission published 2025 guidance to help providers meet obligations when delivering digital goods and services under the Disability Discrimination Act.

The legal tests and enforcement systems differ, and businesses should not substitute WCAG certification language for jurisdiction-specific advice. The commercial pattern is nevertheless converging: digital access is becoming part of what it means to offer a service, not an optional feature added after launch.

A practical review starts with one real purchase

Choose a representative customer task and complete it from discovery to confirmation using only a keyboard. Repeat it with a screen reader, enlarged text and a narrow viewport. Include the payment handoff, authentication, order email, cancellation or return process and support contact.

Record every barrier by business impact and affected step. Fix the underlying component rather than the single page where it was found. Add accessibility requirements to design files, code review, content publishing and vendor procurement. Retest after changes with disabled users and keep evidence of the decision.

The result is not merely a cleaner audit. Labels improve clarity. Structured content travels more reliably across devices. Keyboard support strengthens interaction design. Clear errors can reduce avoidable support contacts. Captions, transcripts and readable content work in more situations than disability alone.

An inaccessible checkout rejects a customer after marketing has already paid to attract them. An accessible one does something more important than protect conversion: it recognises that disabled people are customers, founders, employees and product experts with an equal claim on the digital market.