---
title: "EAA e-commerce checkout accessibility FAQ"
canonical_url: "https://www.sorena.io/artifacts/eu/accessibility-act/faq/e-commerce-checkout"
source_url: "https://www.sorena.io/artifacts/eu/accessibility-act/faq/e-commerce-checkout"
author: "Sorena AI"
description: "How to test an e-commerce checkout under the European Accessibility Act, including service scope, payment and identification flows, service information, and evidence."
published_at: "2026-05-09"
updated_at: "2026-05-09"
keywords:
  - "European Accessibility Act"
  - "EAA e-commerce"
  - "checkout accessibility"
  - "payment accessibility"
  - "EN 301 549"
  - "EAA"
  - "e-commerce accessibility"
---
**[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 FAQ

How to test an e-commerce checkout under the European Accessibility Act, including service scope, payment and identification flows, service information, and evidence.

*FAQ* *European Accessibility Act*

## EAA FAQ Accessible e-commerce checkout

The European Accessibility Act covers e-commerce services provided to consumers, including websites and mobile services used to conclude consumer contracts.

Use this FAQ to test the complete checkout journey, keep service information and evidence together, and avoid overstating what standards evidence proves.

An EAA checkout review should test whether a consumer can complete the online purchase journey with accessibility support intact. Cover product and service information, cart and account steps, identification, electronic signature where used, security prompts, payment, error recovery, confirmation, and customer support information.

## What does the EAA cover in an e-commerce checkout?

Directive (EU) 2019/882 defines e-commerce services as services provided at a distance, through websites or mobile device-based services, by electronic means and at the individual request of a consumer, with a view to concluding a consumer contract.

For checkout testing, that means the relevant scope is the consumer journey used to buy the product or service online. The review should not stop at a home page or product page audit if the consumer still needs to sign in, choose delivery, accept terms, authenticate, pay, or receive confirmation.

- Confirm that the tested flow is consumer-facing and is used to conclude a consumer contract.
- Include website and mobile app checkout variants when both are offered to consumers.
- Include accessibility information about the products or services being sold when the responsible economic operator provides that information.
- Do not treat physical point-of-sale payment terminals as the same fact pattern as online checkout; the Directive defines payment terminals as physical point-of-sale devices, not virtual environments.

Sources for this answer:

- [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Defines e-commerce services, lists e-commerce in Article 2 scope, and separates physical payment terminals from virtual payment environments.
- [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 page used for the public EAA context and covered-products-and-services framing.

## What should the checkout test cover?

Use the EAA service requirements as the control map. Annex I requires service information to be provided through accessible channels, websites and mobile services to be perceivable, operable, understandable, and robust, and available support services to provide accessibility and assistive-technology compatibility information in accessible communication modes.

For a checkout, the practical evidence should show that the user can understand the offer, move through each step, enter and review data, recover from mistakes, authenticate where required, complete payment, and receive confirmation without losing accessibility support.

- Product and service information: names, prices, variants, delivery choices, accessibility information supplied by the responsible operator, and terms needed before purchase.
- Controls and navigation: keyboard path, focus order, labels, headings, state changes, modals, cart updates, and status messages.
- Forms and errors: required fields, input purpose, validation messages, error suggestions, address lookup, coupon fields, and order review.
- Identification and security: sign-in, account creation, password reset, multi-factor prompts, biometric alternatives where relevant, session timeout, and fraud checks.
- Payment and confirmation: card fields, hosted payment frames or redirects, wallet flows, electronic signatures where used, failure messages, receipts, and order-status pages.

Sources for this answer:

- [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Annex I sets the general service accessibility requirements and the specific e-commerce requirements for accessibility information, identification, security, and payment.
- [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 overview for EN 301 549, the ICT accessibility standard useful for mapping web, mobile, software, and assistive-technology test evidence.

## What evidence should be kept for an EAA checkout review?

Service providers must prepare information explaining how covered services meet applicable accessibility requirements, make that information publicly available in written and oral format including accessible formats, and keep it for as long as the service is in operation.

The checkout evidence pack should therefore connect public service information with release evidence. It should be clear which checkout was tested, which EAA requirements were mapped, what standards or test methods were used, what defects remain, and how changes in the service or applicable standards will be reviewed.

- Scope record: consumer-facing checkout URL or app screen set, countries or markets covered, service provider owner, and whether the flow concludes a consumer contract.
- Requirement map: Annex I general service requirements, e-commerce-specific identification, security and payment requirements, and any standards clauses used as technical evidence.
- Test evidence: automated findings, manual keyboard and screen-reader notes, mobile app checks where relevant, payment-provider test evidence, screenshots or recordings, defect tickets, fixes, and retests.
- Service information: general description of the service in accessible formats, explanation of checkout operation, accessibility statement or equivalent terms content, and support-service accessibility information.
- Change control: review trigger for checkout redesigns, payment provider changes, new authentication methods, mobile app releases, harmonised-standard updates, complaints, incidents, or authority requests.

Sources for this answer:

- [Directive (EU) 2019/882 (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj?ref=sorena.io) - Article 13 and Annex V support the service-provider evidence model for public information, service-operation descriptions, monitoring, and authority response.
- [European Commission - accessibility standardisation](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/accessibility-standardisation_en?ref=sorena.io) - Commission source for the role of common European accessibility standards in ICT and internal-market accessibility implementation.

## Common checkout documentation mistakes

The main risk is producing a generic accessibility statement that does not prove the checkout can actually be completed. Evidence is stronger when it follows the money path and the account path from start to finish.

- Do not cite EN 301 549 or WCAG as a standalone EAA conclusion without mapping the checkout to EAA service and e-commerce requirements.
- Do not exclude payment-provider frames, redirects, authentication prompts, fraud checks, or wallet flows if they are necessary to complete the purchase.
- Do not remove accessibility support during security steps; if security requirements constrain assistive-technology access, record the constraint and the accessible alternative tested.
- Do not publish product or service accessibility information only in an inaccessible PDF, image, modal, or account-only area if consumers need it before purchase.
- Do not let release evidence go stale after checkout redesigns, new payment providers, mobile app changes, or updates to the standards used in the conformance claim.

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 need to keep services conforming after changes and to make service information accessible.
- [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 treating EN 301 549 as ICT accessibility test evidence across web pages, mobile applications, software, hardware, and combinations.

## 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, service-provider duties, Annex I service requirements, Article 14 assessments, and Annex V service information.
  - Quote: "e-commerce services"
- [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) - Official Commission EAA policy context source used to keep public-facing scope language aligned with EU materials.
  - Quote: "European Accessibility Act"
- [European Commission - accessibility standardisation](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/accessibility-standardisation_en?ref=sorena.io) - Commission source for the role of common European accessibility standards, including ICT accessibility, without treating standards evidence as wider than the covered requirements.
  - Quote: "Common European accessibility standards"
- [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 as an ICT accessibility standard relevant to checkout web, mobile, software, and assistive-technology evidence.
  - Quote: "Accessibility requirements for ICT products and services"

## 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 guide](/artifacts/eu/accessibility-act/e-commerce-checkout-accessibility.md): Grounded EU Accessibility Act guide for accessible e-commerce checkout scope, payment and identification requirements, evidence, standards mapping, and customer information.
- [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.

*Recommended next step*

*Placement: after evidence section*

## Review the checkout evidence before release

Map your checkout journey to EAA service scope, identification, security, payment, service information, standards evidence, and release records.

- [Open Research Copilot](/solutions/research-copilot.md): Check EAA scope and source-linked evidence before release.
- [Talk through implementation](/contact.md): Review checkout flows, payment evidence, service information, and open risks.


---

[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/faq/e-commerce-checkout