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.
This page helps 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.
An 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 evidence should show which parts of the contract-forming service are perceivable, operable, understandable, and robust, without turning a scoped checkout result into a claim about the whole shop.
1
Section 1
E-commerce checkout scope under the EAA
Treat a checkout flow as in scope when it is part of an 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, but do not assume that outsourced content is excluded. Article 2 excludes only where it is neither funded, developed by, nor under the economic operator's control. A contracted payment widget, identity flow, or delivery selector therefore needs a fact-specific assessment of those conditions. Other exclusions cover certain pre-28 June 2025 media and office files, navigational maps with essential information supplied accessibly, and archives containing only material not updated or edited after that date.
The service rules apply to covered e-commerce services provided to consumers after 28 June 2025. A service contract agreed before that date may continue without alteration until expiry or 28 June 2030, whichever comes first, but Article 32 does not create a general grace period for an existing checkout site, a new release, or an altered contract.
Record the consumer contract path, channels covered, countries served, and whether the service is provided to consumers in the Union.
Identify third-party checkout dependencies such as payment service providers, fraud tools, address lookup, tax engines, delivery selectors, chat, and consent tools. Record who funds, develops, configures, and controls each one before treating any content as excluded.
Separate EAA checkout duties from unrelated product compliance claims, but include accessibility information about products or services being sold when that information is provided by the responsible economic operator.
Check whether the service provider is a microenterprise before applying service accessibility obligations, because Article 4 exempts microenterprises providing services from the accessibility requirements and related obligations.
Supports the e-commerce service definition, consumer-service scope, website and mobile content exclusions, microenterprise service exemption, and the rule that online sales of products or services can be covered.
Commission policy source for the EAA as an EU accessibility directive covering selected products and services.
European Accessibility Act
Recommended next step
Review the checkout evidence before release
This EAA checkout guide helps 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.
Map basket, account, security, delivery, payment, review, confirmation, and support steps to Annex I Section III service requirements.
Map identification, security, electronic signature if used, and payment steps to Annex I Section IV e-commerce requirements.
Use the applicable EN 301 549 web-content clauses to organise technical evidence for checkout pages, especially keyboard access, focus order, labels and instructions, error handling, error prevention, and status messages.
For mobile apps or embedded non-web checkout software, record the equivalent EN 301 549 software or document clauses used rather than treating a website-only test as complete.
Supports Annex I Section III service accessibility requirements and Section IV e-commerce requirements for information, identification, security, electronic signatures, and payment functionality.
Official ETSI source for EN 301 549, the ICT accessibility standard used to structure technical checkout evidence for websites, documents, software, and support services.
ICT Accessibility
3
Section 3
Evidence package for a checkout accessibility review
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 and retained for five years after the service was last provided. A service provider relying on disproportionate burden must renew it when the service changes, when the authority requests it, and at least every five years. The Directive sets no fixed cost percentage for disproportionate burden and does not allow that ground where outside public or private funding was provided to improve accessibility.
Keep an Annex I matrix that maps each checkout step to service requirements, e-commerce-specific requirements, EN 301 549 clauses, test method, result, owner, and defect link.
Retain manual assistive-technology notes for the contract path, automated scan results as supporting evidence, browser and device coverage, and proof that payment and security handoffs returned accessible status and error messages.
Keep supplier evidence for payment, identity, fraud, delivery, chat, and consent tools; include contract clauses or declarations only when they identify the exact service, version, and accessibility features relied on.
Store the public accessibility information text, approval history, customer-support scripts, complaint intake route, monitoring cadence, and release sign-off with the checkout record.
Supports Article 13 service-provider obligations, Annex V service information, and Article 14 documentation and renewal rules for fundamental alteration or disproportionate burden assessments.
Commission source for harmonised-standard context used when a service provider relies on standards or technical specifications as evidence.
Harmonised standards
4
Section 4
Consumer-facing information for checkout accessibility
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.
Publish a plain description of the checkout service, not an internal legal memo.
Describe account, guest checkout, payment, confirmation, customer support, and accessibility-feedback routes in accessible formats.
List known limitations only when they are accurate, time-bounded by remediation ownership, and not used as a substitute for required accessibility.
Version the statement and link it to release evidence so public claims match the checkout tested.
Supports the requirement to make service accessibility information public, accessible, retained while the service operates, and described in general terms and conditions or an equivalent document.
Supports using EN 301 549 as the technical reference behind public claims about website, mobile, document, software, and support-service accessibility.
Primary legal source for EAA e-commerce service scope, Article 13 service-provider duties, Article 14 exceptions, Article 15 presumption of conformity, Annex I checkout-relevant requirements, and Annex V public service information.
Supports the e-commerce service definition, consumer-service scope, website and mobile content exclusions, microenterprise service exemption, and the rule that online sales of products or services can be covered.
Supports Annex I Section III service accessibility requirements and Section IV e-commerce requirements for information, identification, security, electronic signatures, and payment functionality.
Show 2 more
Supports Article 13 service-provider obligations, Annex V service information, and Article 14 documentation and renewal rules for fundamental alteration or disproportionate burden assessments.
Supports the requirement to make service accessibility information public, accessible, retained while the service operates, and described in general terms and conditions or an equivalent document.
Official ETSI source for EN 301 549, used here as the technical standards mapping reference for checkout web, mobile, document, software, and support evidence.
Official ETSI source for EN 301 549, the ICT accessibility standard used to structure technical checkout evidence for websites, documents, software, and support services.
Supports using EN 301 549 as the technical reference behind public claims about website, mobile, document, software, and support-service accessibility.