We use privacy-by-default, cookieless analytics.

Optional analytics cookies are used only if you accept them.

Read our Terms of Use and Privacy Policy.

FAQEuropean Accessibility Act

EAA FAQ Accessible e-commerce checkout

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

This FAQ helps test the complete checkout journey, keep service information and evidence together, and avoid overstating what standards evidence proves.

Back to main artifactReview sources
Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
4 sections4 primary sources
Overview

For provided to consumers after 28 June 2025, 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. Apply the national law that transposes Directive (EU) 2019/882 in each market where the service is provided.

Search this module

Find a question or answer quickly

4 of 4 questions
Question 1

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

Directive (EU) 2019/882 defines 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.
  • Check Article 2 website and mobile-content exclusions separately. They can exclude qualifying old media, old office files, accessible-map cases, uncontrolled third-party content, or unchanged archives, but they do not remove the remaining checkout journey from scope.

How should an e-commerce checkout be tested for European Accessibility Act compliance?

Test the complete consumer contract journey, not isolated pages. A useful EAA checkout test covers product or service accessibility information, cart changes, account creation or guest checkout, identification, electronic signature where used, security checks, payment, error messages, order confirmation, and support contact paths. Record which website or mobile app version was tested, which assistive technologies or accessibility checks were used, the defects found, fixes made, retest results, and who approved release.

Does the EAA require accessible identification, security, and payment in online checkout?

Yes, for the Directive adds specific requirements for identification, electronic signatures, security, and payment functionality when those functions are delivered as part of the service. They must be perceivable, operable, understandable, and robust, so test login, one-time passcode screens, fraud checks, wallet redirects, card fields, payment confirmation, and failure recovery as part of the checkout path.

Recommended next step

Review the checkout evidence before release

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

Research workflow
Open Research Copilot

Check EAA scope and cited evidence before release.

Explore next step
Talk to Sorena
Talk through implementation

Review checkout flows, payment evidence, service information, and open risks.

Explore next step
Question 2

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.
  • Third-party steps: record redirects, hosted payment fields, identity checks, wallet screens, and authentication hand-offs as part of the tested journey. A supplier report can support the evidence, but it does not by itself show that the integrated consumer journey is accessible.
  • 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.

Can a checkout team rely on WCAG or EN 301 549 evidence alone?

No single standards label should be treated as the whole EAA answer. EN 301 549 and WCAG-based results are useful technical evidence for web, mobile, software, document, and assistive-technology behaviour, but the EAA record should also map the checkout to the Directive's service scope, e-commerce-specific identification, security and payment requirements, service information, support information, fixes, and release decision. A presumption of conformity based on a harmonised standard depends on its reference being published in the Official Journal and applies only to the requirements that the standard or part covers.

Question 3

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.

What if full checkout accessibility would require a fundamental alteration or disproportionate burden?

Do not bury that conclusion in a test report. Article 14 requires a requirement-specific assessment before relying on fundamental alteration or disproportionate burden, and relevant results must be kept for five years after the service was last provided and supplied to authorities on request. Notify the relevant service-compliance authorities when Article 14 is relied on unless the operator is a microenterprise. A service disproportionate-burden assessment must be renewed when the service changes, when an authority asks, and at least every five years. An operator that receives public or private funding from outside its own resources for the purpose of improving accessibility cannot rely on disproportionate burden, and every unaffected requirement still applies.

Question 4

Common checkout documentation mistakes

The main risk is producing a generic accessibility statement that does not prove the checkout can actually be completed. Follow the purchase and account journeys from start to finish, including authentication, payment, confirmation, and error recovery.

  • 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.
Primary sources

References and citations

Directive (EU) 2019/882 (European Accessibility Act)
eur-lex.europa.eu5 citations
Referenced sections
  • Primary legal source for EAA e-commerce service scope, service-provider duties, Annex I service requirements, Article 14 assessments, and Annex V service information.
  • Defines e-commerce services, lists e-commerce in Article 2 scope, and separates physical payment terminals from virtual payment environments.
  • Annex I sets the general service accessibility requirements and the specific e-commerce requirements for accessibility information, identification, security, and payment.
Show 2 more
  • Article 13 and Annex V support the service-provider evidence model for public information, service-operation descriptions, monitoring, and authority response.
  • Supports the need to keep services conforming after changes and to make service information accessible.
"e-commerce services"
More quoted passages
"with a view to concluding a consumer contract"
"perceivable, operable, understandable and robust"
"for as long as the service is in operation"
"provision of services remains in conformity"
ETSI - EN 301 549 accessibility standard overview
etsi.org3 citations
Referenced sections
  • Official ETSI source for EN 301 549 as an ICT accessibility standard relevant to checkout web, mobile, software, and assistive-technology evidence.
  • Official ETSI overview for EN 301 549, the ICT accessibility standard useful for mapping web, mobile, software, and assistive-technology test evidence.
  • Supports treating EN 301 549 as ICT accessibility test evidence across web pages, mobile applications, software, hardware, and combinations.
"Accessibility requirements for ICT products and services"
More quoted passages
"ICT products and services"
"web pages, mobile applications, desktop applications"
European Commission - accessibility standardisation
commission.europa.eu2 citations
Referenced sections
  • Commission source for the role of common European accessibility standards, including ICT accessibility, without treating standards evidence as wider than the covered requirements.
  • Commission source for the role of common European accessibility standards in ICT and internal-market accessibility implementation.
"Common European accessibility standards"
More quoted passages
"support implementation of accessibility"
European Commission - European Accessibility Act policy page
commission.europa.eu2 citations
Referenced sections
  • Official Commission EAA policy context source used to keep public-facing scope language aligned with EU materials.
  • Commission policy page used for the public EAA context and covered-products-and-services framing.
"European Accessibility Act"
More quoted passages
"European Accessibility Act (EAA)"

Related guides

EAA conformance statements: products, services, EN 301 549 evidence

What an EU Accessibility Act conformance statement should include, with product EU declarations, service information, EN 301 549 and WCAG evidence boundaries.

EN 301 549 clause mapping for the EU Accessibility Act | EAA FAQ

How to map EN 301 549 and WCAG evidence to EU Accessibility Act Annex I requirements without overclaiming presumption of conformity.

EU Accessibility Act authority request response FAQ

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 microenterprise exemption and disproportionate burden FAQ

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 procurement acceptance criteria | EAA FAQ

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 service transition rules under Article 32 | EAA FAQ

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.

Show all related guides (35)

EU Accessibility Act services: banking, transport, media and e-books

FAQ on which consumer banking, transport, audiovisual media access, electronic communications, e-book, and e-commerce services fall under the EU Accessibility Act.

WCAG Evidence for the EU Accessibility Act and EN 301 549 | EAA FAQ

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

Article 2 and Article 3 scope summary for EU Accessibility Act covered products, services, exclusions, product-service boundaries, and records to keep.

EAA Accessibility Conformance Statement Template

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

A cited EU Accessibility Act workflow for Article 14 fundamental alteration and disproportionate burden assessments, records, reassessment triggers, and evidence.

EAA e-commerce checkout accessibility guide

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

EAA EN 301 549 and WCAG mapping

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

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

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

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

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

How to use EN 301 549 and WCAG evidence in EU Accessibility Act procurement acceptance without overstating presumption of conformity.

EN 301 549 evidence matrix workflow for EAA readiness

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

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

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 checklist for products and services

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

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

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

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

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

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

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

EU Accessibility Act guide for ecommerce teams covering consumer checkout journeys, service information, accessibility evidence, and exceptions.

EU Accessibility Act penalties and enforcement

How Directive (EU) 2019/882 handles penalties, Member State enforcement, market surveillance for products, and service compliance checks.

EU Accessibility Act Product and Service Scope

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

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

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 vs ADA and Section 508

Compare EAA product and consumer-service duties with ADA Title II and III accessibility duties and US federal Section 508 ICT requirements.

EU Accessibility Act vs Web Accessibility Directive

Compare the European Accessibility Act with the Web Accessibility Directive: scope, covered actors, services, standards, evidence, monitoring, enforcement, and key dates.