EAA E-commerce Accessibility: WCAG Audit & Checkout

European E-commerce Accessibility: EAA Compliance, WCAG 2.2 AA and Accessible Checkout Testing

European Accessibility Act | Online Retail | WCAG Audits

Your online store may have an accessible homepage, but can every customer search, choose, buy, pay and manage an order?

The European Accessibility Act (EAA) applies to covered e-commerce services from 28 June 2025. For online retailers, accessibility is not limited to page design. It includes the complete shopping experience.

Enabled.in European e-commerce accessibility services: EAA gap assessment, WCAG 2.2 AA audits and VPAT/ACR support for Shopify, WooCommerce, Magento, Adobe Commerce and BigCommerce.
European e-commerce accessibility: EAA assessments, WCAG testing and VPAT/ACR support by Enabled.in.

A customer may be able to read a product description but still be unable to select a size, change a quantity, apply a discount code or complete payment using a keyboard or screen reader.

This guide explains European e-commerce accessibility requirements, common barriers, WCAG testing priorities and how businesses can assess their online stores.

Enabled.in supports retailers, marketplaces and e-commerce technology providers through EAA implementation gap assessments , WCAG accessibility audits, assistive technology testing, VPAT/ACR support and remediation guidance.

Key takeaway: An accessibility score does not prove that a customer can complete a purchase. Test the full shopping journey, including search, product options, cart, checkout, payment and account functions.

1. Executive Summary

European e-commerce accessibility means customers with disabilities can use an online shopping service without facing avoidable barriers.

For covered services, businesses must consider the EAA requirements and the relevant national laws that implement them.

A practical assessment should cover:

  • Product search and navigation
  • Filters and sorting
  • Product images and descriptions
  • Size, colour and product configuration
  • Shopping cart and discount codes
  • Checkout forms and validation
  • Payment and authentication
  • Customer accounts and order history
  • Returns and customer support
  • Mobile shopping experiences
  • Consent banners and third-party widgets

The goal is not simply to remove automated accessibility errors. It is to make important customer tasks usable with different input methods and assistive technologies.

2. European Accessibility Act Requirements for E-commerce

Does the EAA Apply to Online Stores?

Yes. The EAA covers e-commerce services that meet its scope. These include services provided at a distance through websites or mobile services, by electronic means and at a consumer’s individual request, with a view to concluding a consumer contract.

The EAA has applied since 28 June 2025. Businesses should review the national legislation in each relevant EU Member State.

What Does the EAA Require?

The EAA includes general accessibility requirements for covered services and additional requirements for e-commerce services.

These address accessible information, websites and mobile services, as well as identification, security and payment functions when they form part of the service.

The requirements focus on making information and functionality perceivable, operable, understandable and robust.

Does Every Small Online Business Have to Comply?

The directive exempts microenterprises providing services. The definition generally covers enterprises with fewer than 10 employees and annual turnover or annual balance-sheet total not exceeding EUR 2 million.

Other exceptions, including fundamental alteration and disproportionate burden, have specific conditions. Businesses should not assume that an exemption applies without reviewing their circumstances and national law.

Is WCAG 2.2 AA Legally Required?

The EAA does not simply state that every online store must meet WCAG 2.2 AA. Its legal requirements are set out in the directive and national laws.

EN 301 549 is an important European accessibility standard used to assess ICT accessibility. Its applicable version and legal status must be checked for the relevant context.

WCAG 2.2 AA is a useful modern testing target because it includes additional accessibility criteria beyond WCAG 2.1 AA. However, WCAG 2.2 AA alone does not establish compliance with every EAA requirement.

Recommended approach: Map applicable EAA requirements to relevant EN 301 549 provisions and WCAG success criteria. Test the service and its supporting processes, then document the results.

3. What 2026 Research Reveals About European E-commerce Accessibility

In July 2026, AccessLumens published research on accessibility across 170 major websites in eight EU countries. The sample included retail, marketplaces, banking, travel and telecommunications.

170 Websites

The research attempted to assess 170 websites across eight EU countries.

107 Scored

107 websites returned results that could be scored.

52.3%

Of scored websites, 52.3% had at least one critical accessibility barrier.

The research also reported that 42.1% of scored sites had a detected failure mapped to WCAG 4.1.2, Name, Role, Value.

This criterion covers important information about user interface components, including accessible names, roles and states.

For an online store, such problems may affect buttons, menus, filters, product selectors and other controls.

What the Research Does Not Prove

The study used automated analysis and scripted keyboard testing. It did not provide a full manual accessibility audit of every website.

Only 11 product pages were scored, and transaction pages mainly represented login or account pages, not completed payment journeys.

Therefore, the findings should be treated as a useful risk indicator, not a legal EAA conformance determination.

Read the AccessLumens 2026 research .

4. Accessibility Risks Across the Complete Shopping Journey

Retail accessibility testing should follow the tasks customers perform. Each stage may introduce a different barrier.

Shopping Stage Potential Barrier User Impact What to Test
Product Search Search suggestions cannot be used with a keyboard. Customers cannot find products efficiently. Keyboard interaction, suggestions and announcements.
Filters and Sorting Checkboxes or custom controls have unclear names or states. Customers cannot narrow results reliably. Accessible names, states, focus and updates.
Product Details Images lack useful alternatives or product details are poorly structured. Customers miss information needed to choose. Alternative text, headings, tables and descriptions.
Product Configuration Size or colour options cannot be selected using a keyboard. Customers cannot configure the product. Control operation, selection state and error messages.
Cart Quantity and price updates are not communicated. Customers do not know whether changes succeeded. Status messages and keyboard controls.
Checkout Forms have missing labels or inaccessible validation. Customers cannot complete their order. Labels, errors, focus order and task completion.
Payment Payment widgets or authentication steps are inaccessible. Customers may be unable to pay. Third-party payment and authentication flows.
Customer Accounts Login, password reset or order history is inaccessible. Customers cannot manage purchases. Authentication, account navigation and forms.
Returns Return forms or status messages are inaccessible. Customers cannot request or track returns. Complete return and support journeys.

5. Accessible Checkout: The Most Important Customer Journey to Validate

Checkout accessibility should be a high-priority testing area because a barrier at this stage can prevent a customer from completing a purchase.

Checkout Forms

Every input needs a clear purpose and an accessible name. Required fields, instructions and errors must be communicated in a way customers can understand.

Test billing addresses, shipping addresses, delivery options, contact details and payment fields.

Error Identification and Recovery

When a customer submits an incomplete form, the application should explain what went wrong and how to correct it.

Errors should not rely only on colour. Screen reader users must be able to discover the error information.

Payment and Authentication

Payment methods, security checks and authentication processes must be included in the accessibility assessment.

This is particularly important when checkout uses external payment providers, embedded forms, CAPTCHAs or one-time passwords.

Order Confirmation

After payment, the customer should receive a clear confirmation. Order details, delivery information and next steps should be accessible.

Example: Checkout Failure

A customer completes the delivery address form and selects Pay. An error appears visually beside the card number field, but focus does not move and the error is not announced.

A screen reader user may not understand why payment failed. The team should verify error identification, accessible instructions and error recovery.

Business recommendation: Test checkout with real product options, shipping methods, discount codes and payment states. A successful homepage scan is not enough.

6. WCAG 2.2 AA Testing Priorities for Online Stores

The following WCAG criteria are important examples for e-commerce. A complete assessment must cover all applicable requirements.

WCAG Criterion E-commerce Example Validation
1.1.1 Non-text Content Product images and icon buttons Meaningful text alternatives
1.3.1 Info and Relationships Forms, product tables and filter groups Semantic structure and relationships
1.4.3 Contrast (Minimum) Product prices and error text Text contrast ratios
1.4.10 Reflow Checkout on narrow screens Content reflow and usability
2.1.1 Keyboard Menus, filters and product selectors Keyboard-only operation
2.4.3 Focus Order Multi-step checkout Meaningful focus sequence
2.4.7 Focus Visible Links, buttons and controls Visible keyboard focus
2.4.11 Focus Not Obscured (Minimum) Sticky cart and cookie banners Focused elements are not fully hidden
2.5.8 Target Size (Minimum) Quantity controls and small icons Target dimensions or applicable spacing exceptions
3.3.1 Error Identification Checkout validation Clear identification of errors
3.3.8 Accessible Authentication (Minimum) Account login Accessible authentication without prohibited cognitive-function tests
4.1.2 Name, Role, Value Custom filters and payment controls Correct accessible names, roles and states
4.1.3 Status Messages Cart updates and search results Appropriate status announcements

Read the W3C WCAG 2.2 standard for the complete requirements and conformance rules.

7. Third-Party Applications and E-commerce Accessibility

Many online stores depend on third-party tools. These may include payment providers, search widgets, reviews, consent management, chat assistants and product recommendation systems.

These components should not be excluded from testing simply because another vendor developed them.

Priority Third-Party Components

  • Payment gateways and card entry forms
  • Consent and cookie preference banners
  • CAPTCHA and identity verification
  • Live chat and customer support widgets
  • Product reviews and ratings
  • Search and recommendation applications
  • Delivery date selectors
  • Returns management systems

Recommended Vendor Controls

Ask vendors for accessibility documentation, supported assistive technology information and available VPAT/ACR reports where appropriate.

However, a vendor’s accessibility report does not replace testing the integrated component inside your store.

The final behaviour may change because of theme code, configuration, custom CSS or application integration.

8. Shopify, Shopify Plus, WooCommerce and Custom E-commerce

The platform used to build a store does not automatically determine whether the finished service meets accessibility requirements.

Shopify and Shopify Plus

Review the theme, navigation, product variants, cart, checkout customisations and installed applications.

Shopify Plus businesses should also review custom integrations and enterprise shopping workflows.

Read the Shopify Plus Accessibility Guide .

WooCommerce

Test the WordPress theme, WooCommerce components, checkout extensions, product variation controls and payment plugins.

Magento and Adobe Commerce

Review custom storefronts, complex product configuration, dynamic filters, customer accounts, checkout and payment integrations.

BigCommerce and Headless Commerce

Evaluate storefront templates, custom components, third-party applications and the complete transaction flow.

For headless applications, test the rendered interface and its complete user journeys.

Key point: An accessible theme or component library is a useful starting point. It does not guarantee that the finished store is accessible.

9. How to Conduct an E-commerce Accessibility Audit

A useful audit should cover both technical conformance and real customer tasks.

Step 1: Define the Scope

Identify websites, mobile applications, markets, languages, user roles, third-party components and critical shopping journeys.

Step 2: Map Legal Requirements

Identify applicable EAA requirements, relevant national law, EN 301 549 provisions and WCAG testing criteria.

Step 3: Select Representative Pages

Include the homepage, search results, product details, cart, checkout, account management and returns.

Step 4: Test Interactive States

Test menus, open filters, validation errors, modal dialogs, cart updates, payment states and confirmation messages.

Step 5: Run Automated Checks

Use automated accessibility testing to identify detectable issues such as missing names, invalid ARIA and contrast failures.

Step 6: Perform Manual Testing

Verify keyboard navigation, focus order, visual presentation, error handling and task completion.

Step 7: Test Assistive Technology

Use an agreed test matrix, which may include NVDA, JAWS, VoiceOver, TalkBack, keyboard-only navigation and magnification.

Step 8: Report and Remediate

Provide each issue with the affected component, actual behaviour, user impact, steps to reproduce and clear recommendations.

Step 9: Retest and Document

Verify fixes and document remaining issues, exceptions and accessibility evidence.

10. EAA E-commerce Accessibility Readiness Checklist

Use this checklist to identify areas that need further assessment. It is a planning aid, not a legal compliance certificate.

Area Readiness Question
Legal Scope Have applicable EAA and national requirements been identified?
Search Can customers search and use suggestions with a keyboard and screen reader?
Filters Can customers select and clear filters accessibly?
Products Are product descriptions, images and options accessible?
Cart Are cart changes and totals understandable?
Checkout Can customers complete checkout without a mouse?
Payment Are payment and authentication steps accessible?
Accounts Can customers log in and manage orders?
Mobile Have relevant mobile experiences been tested?
Third Parties Have integrated applications been included in testing?
Remediation Are issues assigned, corrected and retested?
Evidence Are accessibility findings and service information documented?

11. How Enabled.in Helps European E-commerce Businesses

Enabled.in supports businesses that need to understand, test and improve the accessibility of online shopping services.

EAA Implementation Gap Assessment

Identify gaps between current e-commerce functionality and applicable accessibility requirements.

WCAG 2.2 AA Accessibility Audit

Assess representative pages, components and shopping workflows through automated and manual testing.

Checkout Accessibility Testing

Evaluate checkout forms, payment processes, validation and confirmation with assistive technologies.

Mobile Accessibility Testing

Review responsive websites and mobile applications using relevant devices and assistive technologies.

Developer Remediation Support

Provide clear recommendations for resolving accessibility issues and improving components.

VPAT/ACR and Compliance Evidence

Support appropriate accessibility conformance reporting, retesting and evidence for procurement and compliance reviews.

For organisations preparing an EAA accessibility programme, explore Enabled.in’s EAA Implementation Gap Assessment and Accessibility Audit Services .

Businesses using Shopify can also review our Shopify Accessibility Audit and Testing Services .

12. Frequently Asked Questions

Does the European Accessibility Act apply to e-commerce websites?

Yes. The EAA covers e-commerce services within its scope. Businesses must review the directive and applicable national legislation to determine their obligations.

When did EAA requirements begin applying?

The EAA has applied from 28 June 2025, subject to the directive’s transitional provisions and relevant national laws.

Does an online store need WCAG 2.2 AA compliance?

WCAG 2.2 AA is a strong accessibility testing target, but the EAA has its own legal requirements. Businesses should map those requirements to applicable standards and national law.

Is an accessible homepage enough for EAA compliance?

No. Covered e-commerce services must address accessibility across relevant functions, including shopping and transaction processes.

What is accessible checkout?

Accessible checkout allows customers to complete purchasing steps using supported input methods and assistive technologies, with clear forms, errors, instructions and feedback.

Does the EAA apply to Shopify stores?

The EAA may apply to a covered e-commerce service regardless of the platform used. Shopify does not automatically establish or remove legal obligations.

Should third-party payment applications be tested?

Yes. Payment and authentication functions that form part of the covered shopping service should be included in the accessibility assessment.

Can automated accessibility tools prove EAA compliance?

No. Automated tools identify some accessibility problems. They cannot fully evaluate legal requirements, interaction quality or complete user journeys.

What should an e-commerce accessibility audit include?

It should include representative pages, interactive states, shopping journeys, automated checks, manual keyboard testing, assistive technology validation and remediation recommendations.

Can Enabled.in provide VPAT/ACR reports for e-commerce platforms?

Enabled.in provides accessibility testing and supports VPAT/ACR preparation for agreed products and reporting standards. A VPAT/ACR is an accessibility conformance report, not an automatic certificate of EAA compliance.

Is Your Online Store Accessible From Search to Checkout?

An accessible homepage is only the beginning. Customers must also be able to find products, configure orders, complete payment and manage purchases.

Enabled.in helps retailers, marketplaces and e-commerce technology teams identify accessibility barriers and prepare practical remediation plans.

Request an EAA Accessibility Assessment

Email: sathasivam@enabled.in

Phone / WhatsApp: +91 9840515647

Website: enabled.in

13. Sources and References

This article provides general accessibility information and does not constitute legal advice. EAA obligations and enforcement depend on applicable national legislation and the circumstances of each service.

Contact an Accessibility Expert

Sathasivam Kannupayan

Head of Digital Accessibility Services, Enabled.in

IAAP Certified Professional in Web Accessibility (CPWA), with over 17 years of experience in digital accessibility, enterprise application testing, WCAG audits, assistive technology validation and VPAT/ACR assessments.

Discuss your European e-commerce accessibility requirements


Discover more from Enabled.in

Subscribe to get the latest posts sent to your email.

Discover more from Enabled.in

Subscribe now to keep reading and get access to the full archive.

Continue reading