EU Accessibility Act for ecommerce websites

Directive (EU) 2019/882 defines e-commerce services as services provided at a distance, through websites and mobile device-based services, by electronic means and at the individual request of a consumer, with a view to concluding a consumer contract. That makes the scoping question practical: identify every consumer journey where a user can select, configure, order, subscribe, reserve, pay for, or otherwise conclude a contract online.

The directive also says ecommerce accessibility obligations apply to the online sale of any product or service, including items that are themselves covered elsewhere in the directive. A retailer should therefore avoid limiting the review to regulated product categories; the online sales service is the trigger.

Annex I requires covered services to provide accessible information about how the service functions and to make websites, online applications, mobile services, and mobile applications perceivable, operable, understandable, and robust. For an ecommerce team, that means the audit must follow the buying task, not only isolated page templates.

The ecommerce-specific requirements add three concrete workstreams: provide accessibility information about the products and services being sold when the responsible economic operator provides that information; make identification, security, and payment functionality accessible when delivered as part of the service; and make identification methods, electronic signatures, and payment services perceivable, operable, understandable, and robust.

Article 13 requires service providers to prepare information explaining how their services meet the applicable accessibility requirements, make that information public in written and oral format, and keep it for as long as the service operates. Annex V says the information belongs in the general terms and conditions or an equivalent document and should describe the service, the operation of the service, and how the relevant Annex I requirements are met.

The evidence file should be usable by product, legal, support, procurement, and authority-response teams. It should show the journey tested, requirements applied, standards or technical specifications used, defects found, remediation decisions, vendor evidence relied on, and how monitoring keeps the service conformant when the service, standards, or accessibility requirements change.

The directive allows accessibility requirements to apply only to the extent that compliance does not fundamentally alter the basic nature of the product or service and does not impose a disproportionate burden. For ecommerce services, that is an evidence-backed assessment, not a shortcut: service providers relying on disproportionate burden must renew the assessment when the service changes, when authorities request it, and at least every five years.

Microenterprises providing services are exempt from the service accessibility requirements and related obligations in Article 4(3). Larger ecommerce providers should not copy that exemption unless the enterprise actually meets the directive's microenterprise definition and the relevant national transposition preserves the exemption. The directive also includes transitional rules for services using products lawfully used before the application date and for pre-existing service contracts, so treat legacy terminals, long-running contracts, and platform migrations as separate facts to document.

A useful ecommerce implementation plan starts with the transaction path and ends with a release gate. Each release that can affect the consumer's ability to conclude a contract should carry accessibility acceptance criteria and evidence before it ships.