EAA Compliance for Ecommerce: What the European Accessibility Act Requires

What the European Accessibility Act requires for ecommerce websites

The European Accessibility Act and ecommerce websites means many online stores, marketplaces and mcommerce apps must meet accessibility requirements when trading in the EU. The Act is Directive (EU) 2019/882. Member States had to transpose it into national law by 28 June 2022 and most commercial suppliers must comply by 28 June 2025. The rules sit alongside the Web Accessibility Directive that covers public sector bodies.

Which ecommerce businesses must comply

Compliance applies where your business supplies products or services covered by the Directive and operates in an EU Member State. That includes private online retailers, platforms that enable sales between traders and consumers, and many digital services used to sell or deliver goods. Small firms that clearly fall outside the Directive may be exempt, but most consumer-facing businesses should assess applicability.

How the Act maps to technical standards

The Directive requires accessible design and information. EU guidance and harmonised European standards are used to define technical requirements. In practice, compliance is achieved by meeting recognised web accessibility standards such as WCAG at an appropriate level, together with applicable European accessibility standards like EN 301 549. Use of WAI ARIA and semantic HTML helps meet those standards.

Core accessibility requirements for ecommerce sites

For ecommerce the technical requirements focus on usability by people who use assistive technology. Key areas are:

• Perceivable content: images, videos and product information must be accessible. Provide alt text, captions and transcripts.
• Operable interface: every control must work from keyboard only and support focus order and visible focus indicators.
• Understandable flows: labels, error messages and instructions must be clear, consistent and localised where needed.
• Robust code: use semantic HTML, valid ARIA only where needed and ensure third-party widgets are accessible.

Priority ecommerce pages and interactions to fix first

Not all pages have equal legal or commercial risk. Prioritise by transaction impact and frequency. Start with:

• Product pages and search results. Include accessible product names, descriptions and alternative text for images.
• Shopping cart and checkout flows. Ensure every field, label and payment option is keyboard operable and described to screen readers.
• Account creation and sign in, subscription management and password recovery flows.
• Delivery options, invoices, order confirmations and digital receipts.
• Customer support pages, contact forms and live chat widgets.

Common ecommerce gaps most sites miss

Automated scans often show many problems but miss real user issues. Typical gaps are:

• Third-party checkouts and embedded payment frames that break keyboard focus.
• Dynamic content updates without appropriate ARIA live regions or notifications.
• Image-heavy product galleries without alternative text or accessible carousels.
• PDF invoices and product brochures that are not tagged for accessibility.
• Complex form controls such as custom selects and date pickers lacking accessible labels.

Practical compliance checklist and timeline for ecommerce teams

Use a short audit then a phased remediation plan. Typical roadmap for a medium site over 3 to 6 months:

1. Discovery week: automated scan, inventory of pages and third parties, quick keyboard and screen reader checks on core flows.
2. Prioritise: mark pages as critical, important or low risk based on conversion and legal exposure.
3. Remediate critical items over 4 to 12 weeks. Fix checkout, account and product pages first.
4. Test with assistive tech and at least five users with diverse disabilities.
5. Publish an accessibility statement and feedback mechanism. Start continuous monitoring and quarterly reviews.

Minimum acceptance criteria for a remedial ticket

• Passes automated checks for the issue class plus manual keyboard and screen reader verification.
• Has a test script showing steps and expected behaviour with NVDA or VoiceOver.
• Includes updated unit or integration tests where possible and a deploy checklist.

Testing methods and tools

Combine automated and manual testing. Automated tools catch many straightforward failures but cannot replicate real user experience.

Automated tools

• Run axe-core or WAVE to identify failures such as missing labels and contrast problems.
• Include accessibility checks in CI pipelines for new builds and releases.

Manual checks

• Keyboard only navigation across full purchase flows. No mouse use allowed.
• Screen reader testing with at least one free screen reader such as NVDA on Windows and VoiceOver on iOS.
• Mobile testing for touch targets, orientation and zoom.
• User testing with people who have a range of impairments. Five users catch most major problems in a single flow test.

Third parties, plugins and payment providers

Third parties can create liability and practical problems. Treat them as part of the product. Steps to manage risk:

• Record every third-party widget that appears in core flows. Ask vendors for an accessibility conformance statement or evidence.
• Prefer vendors with documented compliance to WCAG 2.1 Level AA or EN 301 549.
• Wrap or replace inaccessible widgets for critical flows such as checkout and sign in.

Accessibility statement and complaints handling

Publish an accessibility statement that states your current conformance level, the scope of pages covered and your remediation plan. The statement should also give a contact for feedback, expected response time and an alternative way to complete purchases for customers who cannot use the site.

Simple accessibility statement elements

• Scope: which parts of the site and apps are covered.
• Standards: reference WCAG 2.1 Level AA and any European standards used.
• Contact: email, phone or web form and target response time.
• Known limitations and a plan or timeline to fix them.

Enforcement, remedies and commercial risk

Member States implement enforcement. Remedies and penalties vary by country. Many national regimes allow complaints to be brought by individuals or consumer bodies and offer orders to fix barriers. Commercial risks include fines, legal costs and lost sales from customers who cannot complete purchases.

Maintenance: keep accessibility part of product development

Accessibility is ongoing. Make it part of your product lifecycle by:

• Including accessibility in design and code reviews.
• Adding automated tests to CI and running manual regression checks on major flows before releases.
• Training product, design and engineering teams on semantic HTML, ARIA best practice and accessible components.

Practical example: prioritising fixes by business impact

Map each page to revenue impact and known accessibility issues. Fix items in this order.

• High revenue, high severity: checkout broken for keyboard users. Fix immediately.
• High revenue, low severity: product descriptions have missing alt text. Fix in the next sprint.
• Low revenue, high severity: marketing carousel inaccessible. Schedule after conversion-critical fixes.

Next steps for ecommerce teams

Start with a short audit of critical purchase flows and third-party integrations. Publish a clear accessibility statement and a remediation roadmap. Use a mix of automated tools, manual testing and real users to validate fixes. That approach reduces legal risk and improves conversion for a significant share of customers.

Resources to explore

• WCAG 2.1 guidance on web content accessibility for technical success criteria.
• EN 301 549 for European ICT accessibility guidance and how it is used by Member States.
• Free screen readers NVDA and VoiceOver for manual testing.