Directive (EU) 2019/882 covers e-commerce services provided to consumers through websites or mobile device-based services with a view to concluding a consumer contract.
Use this page to scope a checkout flow, map identification, security and payment steps to Annex I, and keep release evidence that supports the public accessibility information required for services.
Structured answer sets in this page tree.
Cited legal and guidance references.
An EAA checkout review should follow the consumer's actual path to contract: product or service selection, basket, account or guest identification, security checks, delivery and billing details, payment, order review, confirmation, help, and cancellation or correction points. The point is not to label the whole shop as accessible; it is to show that the contract-forming service is perceivable, operable, understandable, robust, and supported by evidence.
Treat a checkout flow as in scope when it is part of an e-commerce service provided to consumers at a distance through a website or mobile device-based service, by electronic means, at the individual request of the consumer, with a view to concluding a consumer contract. That captures the online sale journey even when the product being sold is not itself an EAA product.
Define the review boundary around the steps needed to conclude the contract. For a typical store this includes product detail accessibility information when supplied by the responsible economic operator, basket changes, account sign-in or guest checkout, identity verification, security challenge, coupon or gift-card entry, delivery option selection, billing address, payment handoff, order review, error recovery, confirmation, and customer support entry points linked from checkout.
Do not overstate the scope. Article 2 lists website and mobile application content exclusions such as third-party content that is not funded, developed by, or under the control of the economic operator, and certain archive or pre-application-date content. Those exclusions still need a page-level record so the team can explain why a payment widget, review plug-in, map, downloadable file, or legacy content was treated as in or out of the checkout evidence set.
Use this EAA checkout guide to align product, engineering, design, legal, procurement, and support teams around the same scope record, standards map, test evidence, and consumer-facing accessibility information.
Annex I requires covered services to provide service information through more than one sensory channel, in an understandable and perceivable way, with text formats that can generate alternative assistive formats, adequate font size and contrast, adjustable spacing, alternatives for non-text content, and electronic information that is perceivable, operable, understandable and robust. Websites, online applications, and mobile device-based services must also be accessible in a consistent and adequate way using those four principles.
For e-commerce specifically, Annex I adds three checkout-relevant duties: provide accessibility information about the products and services being sold when that information is provided by the responsible economic operator; make identification, security and payment functionality accessible when it is delivered as part of the service instead of a product; and provide identification methods, electronic signatures and payment services that are perceivable, operable, understandable and robust.
A practical checkout acceptance test should therefore cover the full happy path and failed states. Test keyboard operation, focus order, visible labels, programmatic names, required-field cues, error identification, error suggestions, prevention before committing legal, financial or data changes, status messages, payment handoff return states, confirmation pages, receipts, and accessible support information.
The evidence package should let a reviewer replay the compliance conclusion without attending the sprint review. Keep the checkout inventory, user journeys, platform versions, third-party components, test scope, defects, fixes, retest results, source mapping, and release decision together.
For service providers, Article 13 requires procedures so the service remains in conformity when service characteristics, accessibility requirements, harmonised standards, or technical specifications change. Annex V also requires information assessing how the service meets the requirements to be included in the general terms and conditions or an equivalent document, with information about the design, operation, monitoring, and relevant accessibility requirements.
If the team relies on fundamental alteration or disproportionate burden, keep that as a separate Article 14 record. The assessment must be documented, retained for the required period, renewed for services when the service is altered, when authorities request it, and at least every five years, and it cannot be used where accessibility funding rules prevent reliance on disproportionate burden.
Do not publish a vague accessibility promise. The consumer-facing statement for the checkout service should describe the service in accessible formats, explain how the checkout operates, and describe how relevant Annex I requirements are met. Keep it close to the checkout or terms location where consumers can find it before or during the transaction.
Useful wording identifies the covered channels, the checkout functions assessed, the standard or technical specification used where applicable, known limitations, accessible support routes, and how consumers can report accessibility barriers. Avoid claiming full EAA compliance for third-party or excluded content unless the evidence package actually covers it.
The statement should stay aligned with releases. Article 13 requires service providers to take adequate account of changes in the service, accessibility requirements, harmonised standards, or technical specifications, so the public information and internal checkout evidence should be updated together when payment, identity, fraud, template, mobile app, or support flows change.
"made available to the public"
"ICT products and services"
"European Accessibility Act"
"Harmonised standards"