---
title: "EAA e-commerce checkout accessibility guide"
canonical_url: "https://www.sorena.io/artifacts/eu/accessibility-act/e-commerce-checkout-accessibility"
source_url: "https://www.sorena.io/artifacts/eu/accessibility-act/e-commerce-checkout-accessibility"
author: "Sorena AI"
description: "Grounded EU Accessibility Act guide for accessible e-commerce checkout scope, payment and identification requirements, evidence, standards mapping, and customer information."
published_at: "2026-05-09"
updated_at: "2026-05-17"
keywords:
  - "EU Accessibility Act e-commerce"
  - "EAA checkout accessibility"
  - "Directive (EU) 2019/882"
  - "EN 301 549 checkout"
  - "accessible payment"
  - "accessible identification"
  - "EU Accessibility Act"
  - "EAA"
  - "e-commerce accessibility"
  - "checkout accessibility"
  - "EN 301 549"
---
**[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform

[Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io)

---

# EAA e-commerce checkout accessibility guide

Grounded EU Accessibility Act guide for accessible e-commerce checkout scope, payment and identification requirements, evidence, standards mapping, and customer information.

*Artifact Guide* *EU*

## EAA e-commerce checkout accessibility

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.

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.

## E-commerce checkout scope under the EAA

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.

- 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; assign each to in-scope, relied-on evidence, or documented exclusion.
- 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.

Sources for this answer:

- [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - 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.
- [European Commission - European Accessibility Act policy page](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/european-accessibility-act-eaa_en?ref=sorena.io) - Commission policy source for the EAA as an EU accessibility directive covering selected products and services.

*Recommended next step*

*Placement: after evidence section*

## Review the checkout evidence before release

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.

- [Open Research Copilot](/solutions/research-copilot.md): Answer EAA scope and standards-mapping questions with cited outputs.
- [Talk through implementation](/contact.md): Review checkout scope, evidence, public statements, and remediation priorities.

## Checkout requirements to map before release

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 EN 301 549 web-content clauses as the technical evidence spine 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.

Sources for this answer:

- [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports Annex I Section III service accessibility requirements and Section IV e-commerce requirements for information, identification, security, electronic signatures, and payment functionality.
- [ETSI - EN 301 549 accessibility standard overview](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Official ETSI source for EN 301 549, the ICT accessibility standard used to structure technical checkout evidence for websites, documents, software, and support services.

## 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, 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.

- 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.

Sources for this answer:

- [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Supports Article 13 service-provider obligations, Annex V service information, and Article 14 documentation and renewal rules for fundamental alteration or disproportionate burden assessments.
- [European Commission - harmonised standards overview](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards_en?ref=sorena.io) - Commission source for harmonised-standard context used when a service provider relies on standards or technical specifications as evidence.

## 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.

Sources for this answer:

- [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - 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.
- [ETSI - EN 301 549 accessibility standard overview](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Supports using EN 301 549 as the technical reference behind public claims about website, mobile, document, software, and support-service accessibility.

## Primary sources

- [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - 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.
  - Quote: "e-commerce services"
- [ETSI - EN 301 549 accessibility standard overview](https://www.etsi.org/human-factors-accessibility/en-301-549-v3-the-harmonized-european-standard-for-ict-accessibility?ref=sorena.io) - Official ETSI source for EN 301 549, used here as the technical standards mapping reference for checkout web, mobile, document, software, and support evidence.
  - Quote: "ICT Accessibility"
- [European Commission - harmonised standards overview](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards_en?ref=sorena.io) - Commission source for harmonised standards and presumption-of-conformity context when published OJEU references cover relevant EAA requirements.
  - Quote: "Harmonised standards"
- [European Commission - European Accessibility Act policy page](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/european-accessibility-act-eaa_en?ref=sorena.io) - Commission policy source for the EAA as an EU accessibility directive covering selected products and services.
  - Quote: "European Accessibility Act"

## Related Topic Guides

- [EAA Accessibility Conformance Statement Template](/artifacts/eu/accessibility-act/accessibility-conformance-statement-template.md): Template language for an EU Accessibility Act conformance statement covering scope, Annex I mapping, service information, standards, support routes, evidence, and limits.
- [EAA Article 14 disproportionate burden workflow](/artifacts/eu/accessibility-act/disproportionate-burden-assessment-workflow.md): A grounded EU Accessibility Act workflow for Article 14 fundamental alteration and disproportionate burden assessments, records, reassessment triggers, and evidence.
- [EAA conformance statements: products, services, EN 301 549 evidence](/artifacts/eu/accessibility-act/faq/conformance-statements.md): What an EU Accessibility Act conformance statement should include, with product EU declarations, service information, EN 301 549 and WCAG evidence boundaries.
- [EAA e-commerce checkout accessibility FAQ](/artifacts/eu/accessibility-act/faq/e-commerce-checkout.md): How to test an e-commerce checkout under the European Accessibility Act, including service scope, payment and identification flows, service information, and evidence.
- [EAA EN 301 549 and WCAG mapping](/artifacts/eu/accessibility-act/en-301-549-and-wcag-mapping.md): Map European Accessibility Act Annex I requirements to EN 301 549 and WCAG evidence without overstating what WCAG tests can prove.
- [EAA EN 301 549 clause mapping for ICT evidence](/artifacts/eu/accessibility-act/en-301-549-clause-mapping.md): Map EN 301 549 clauses to EU Accessibility Act evidence, Annex I outcomes, product and service records, and gaps that need non-ICT support.
- [EAA procurement clauses and accessibility acceptance criteria](/artifacts/eu/accessibility-act/procurement-language-and-acceptance-criteria.md): Buyer-side EU Accessibility Act procurement language for covered products and services, with supplier evidence, EN 301 549 limits, Article 14 exception records, and acceptance criteria.
- [EAA scope classifier workflow for products and services](/artifacts/eu/accessibility-act/accessibility-scope-classifier-workflow.md): Classify EU Accessibility Act scope by product or service category, consumer use, market or service date, operator role, exclusions, exemptions, Article 14 records, and evidence.
- [EAA testing and conformance evidence | Annex I, EN 301 549 and Article 14](/artifacts/eu/accessibility-act/testing-and-conformance-evidence.md): How to document European Accessibility Act testing evidence: Annex I mappings, product technical files, service information, EN 301 549 boundaries, harmonised-standard limits, and Article 14 exception records.
- [EAA WCAG evidence and procurement acceptance](/artifacts/eu/accessibility-act/wcag-evidence-and-procurement-acceptance.md): How to use EN 301 549 and WCAG evidence in EU Accessibility Act procurement acceptance without overstating presumption of conformity.
- [EN 301 549 clause mapping for the EU Accessibility Act | EAA FAQ](/artifacts/eu/accessibility-act/faq/en-301-549-clause-mapping.md): How to map EN 301 549 and WCAG evidence to EU Accessibility Act Annex I requirements without overclaiming presumption of conformity.
- [EN 301 549 evidence matrix workflow for EAA readiness](/artifacts/eu/accessibility-act/en-301-549-evidence-matrix-workflow.md): Build an EN 301 549 evidence matrix for European Accessibility Act work: scope rows, clause mapping, test evidence, owner sign-off, exception records, and limits of standards evidence.
- [EN 301 549 vs WCAG for EAA evidence](/artifacts/eu/accessibility-act/en-301-549-vs-wcag.md): Compare EN 301 549 and WCAG for European Accessibility Act planning: ICT scope, web-content overlap, harmonised-standard limits, and evidence beyond WCAG-only tests.
- [EU Accessibility Act Applicability Test](/artifacts/eu/accessibility-act/applicability-test.md): Check whether the European Accessibility Act covers a product or consumer service, which role applies, which date matters, and what evidence to keep.
- [EU Accessibility Act authority request response FAQ](/artifacts/eu/accessibility-act/faq/authority-response.md): How to answer EU Accessibility Act checks from market surveillance or service authorities with technical documentation, service information, Article 14 records, and corrective actions.
- [EU Accessibility Act checklist for products and services](/artifacts/eu/accessibility-act/checklist.md): Checklist for EAA scope, operator role, Annex I mapping, product technical files, service information, Article 14 assessments, supplier evidence, release checks, and monitoring.
- [EU Accessibility Act compliance operating model](/artifacts/eu/accessibility-act/compliance.md): Build an EU Accessibility Act compliance file for covered products and services: scope, operator roles, Annex I mapping, conformity evidence, Article 14 assessments, corrective actions, and records.
- [EU Accessibility Act deadlines and compliance calendar](/artifacts/eu/accessibility-act/deadlines-and-compliance-calendar.md): Calendar for the EU Accessibility Act: 2022 transposition, 2025 application, 2027 emergency communications timing, 2030 transition rules, owner actions, and evidence records.
- [EU Accessibility Act deadlines and transition plan](/artifacts/eu/accessibility-act/deadlines-and-transition-plan.md): Plan for the European Accessibility Act application date, service-contract transition, self-service terminal transition, 112 derogation, and evidence gates.
- [EU Accessibility Act disproportionate burden decision](/artifacts/eu/accessibility-act/disproportionate-burden-decision.md): How to document an EU Accessibility Act Article 14 disproportionate burden decision with supported criteria, retained evidence, limits, notifications, and review triggers.
- [EU Accessibility Act exemptions and disproportionate burden](/artifacts/eu/accessibility-act/exemptions-and-disproportionate-burden.md): Article 14 EAA guide covering fundamental alteration, disproportionate burden, service microenterprise exemptions, content exclusions, transition limits, and documentation.
- [EU Accessibility Act FAQ: scope, dates, services, Article 14](/artifacts/eu/accessibility-act/faq.md): Clear answers on EU Accessibility Act scope, 28 June 2025 application, covered products and services, microenterprises, Article 14, service information, standards, and penalties.
- [EU Accessibility Act for ecommerce websites](/artifacts/eu/accessibility-act/accessibility-act-for-ecommerce-websites.md): Grounded guide for ecommerce teams applying the EU Accessibility Act to consumer checkout journeys, service information, accessibility evidence, and exceptions.
- [EU Accessibility Act microenterprise exemption and disproportionate burden FAQ](/artifacts/eu/accessibility-act/faq/microenterprise-and-disproportionate-burden-decisions.md): FAQ explaining when EAA microenterprise relief applies, how Article 14 disproportionate-burden assessments work, what Annex VI requires, and what records to keep.
- [EU Accessibility Act penalties and enforcement](/artifacts/eu/accessibility-act/penalties-and-fines.md): How Directive (EU) 2019/882 handles penalties, Member State enforcement, market surveillance for products, and service compliance checks.
- [EU Accessibility Act procurement acceptance criteria | EAA FAQ](/artifacts/eu/accessibility-act/faq/procurement-acceptance.md): How to write EAA procurement acceptance criteria that ask suppliers for scoped accessibility evidence, standards mappings, declarations, and exception records without overclaiming conformity.
- [EU Accessibility Act Product and Service Scope](/artifacts/eu/accessibility-act/product-and-service-category-scoping.md): Scope products and services under the EU Accessibility Act using Article 2 categories, Article 3 definitions, limited content exclusions, microenterprise treatment, and evidence records.
- [EU Accessibility Act products and services in scope](/artifacts/eu/accessibility-act/products-and-services-in-scope.md): Article 2 scope guide for the European Accessibility Act: covered products, covered consumer services, economic-operator roles, Article 3 definitions, and evidence records.
- [EU Accessibility Act Requirements: Annex I, Products, Services](/artifacts/eu/accessibility-act/requirements.md): Map EU Accessibility Act requirements by Article 4, Annex I, product and service obligations, Article 13 evidence, standards, and Article 14 exceptions.
- [EU Accessibility Act service transition rules under Article 32 | EAA FAQ](/artifacts/eu/accessibility-act/faq/transition-services.md): FAQ on EU Accessibility Act Article 32 transition rules for service providers, pre-28 June 2025 contracts, 2030 limits, self-service terminals, evidence records, and change triggers.
- [EU Accessibility Act services: banking, transport, media and e-books](/artifacts/eu/accessibility-act/faq/banking-transport-and-media-services.md): FAQ on which consumer banking, transport, audiovisual media access, electronic communications, e-book, and e-commerce services fall under the EU Accessibility Act.
- [EU Accessibility Act vs ADA and Section 508: EAA-grounded comparison](/artifacts/eu/accessibility-act/accessibility-act-vs-ada-and-section-508.md): Compare the EU Accessibility Act with ADA and Section 508 planning boundaries, using grounded EAA scope, evidence, standards, procurement, and operator-duty points.
- [EU Accessibility Act vs Web Accessibility Directive](/artifacts/eu/accessibility-act/accessibility-act-vs-web-accessibility-directive.md): Compare the European Accessibility Act with the Web Accessibility Directive: scope, covered actors, services, standards, evidence, monitoring, enforcement, and key dates.
- [WCAG Evidence for the EU Accessibility Act and EN 301 549 | EAA FAQ](/artifacts/eu/accessibility-act/faq/wcag-evidence.md): When WCAG test evidence helps EAA work, how it maps through EN 301 549, and why WCAG alone does not prove European Accessibility Act compliance.
- [Which products and services does the EU Accessibility Act cover? | EAA FAQ](/artifacts/eu/accessibility-act/faq/product-and-service-categories.md): Article 2 and Article 3 scope summary for EU Accessibility Act covered products, services, exclusions, product-service boundaries, and records to keep.


---

[Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us)

(c) 2026 Sorena AB (559573-7338). All rights reserved.

Source: https://www.sorena.io/artifacts/eu/accessibility-act/e-commerce-checkout-accessibility