Skip to content
Guide

Writing an Accessibility Statement for Your Online Shop

Accessibility (EAA)

An accessibility statement tells your customers how usable your shop is for people with disabilities, which standard you aim to meet, and how to get in touch if something is not working for them. Under the European Accessibility Act it is good practice rather than a strict formal requirement, but it is one of the most useful pages you can publish. This guide explains what to include and gives you a short template to adapt.

Where the statement fits in

The European Accessibility Act (EAA), Directive (EU) 2019/882, has applied since 28 June 2025. It requires many e-commerce services to meet the harmonised technical standard EN 301 549, which in practice points to WCAG 2.1 level AA. An accessibility statement does not replace the technical work, but it documents your commitment, records where you stand, and gives users a clear route to report problems.

What to include

A good statement is honest and specific. Vague promises help no one. Aim to cover the following areas.

The standard you meet

State which standard you are working to, typically WCAG 2.1 AA as referenced by EN 301 549, and to what degree you meet it. Be plain about whether you are fully conformant, partially conformant, or still working towards conformance. Shoppers and auditors both value candour over a polished but empty claim.

Known limitations

List the parts of your shop that you know are not yet fully accessible. This might include a third-party payment widget, certain PDFs, or older product images without descriptive alternative text. Naming limitations honestly builds trust and shows you are managing the issues rather than hiding them. Where you can, add a rough timescale for fixing each item.

A contact and feedback route

Give people a clear way to tell you when something blocks them, and set an expectation for how quickly you will respond. An email address or a simple contact form is enough. The feedback route is arguably the single most important element, because it turns your statement into a living channel rather than a static declaration.

A short template

Use the following outline as a starting point and fill in the details for your own shop.

  • Introduction: who you are and your commitment to accessible service.
  • Standard met: the target standard, for example WCAG 2.1 AA under EN 301 549, and your level of conformance.
  • Scope: which pages, services and checkout flows the statement covers.
  • Known limitations: a frank list of areas that are not yet accessible, with timescales where possible.
  • Feedback route: how to report a barrier and how quickly you aim to reply.
  • Last reviewed: the date you last checked the statement and the underlying site.

Keeping it current

An accessibility statement is only useful if it reflects reality. Review it whenever you change your theme, add a module, or redesign checkout, and update the “last reviewed” date each time. If you fix a limitation you had listed, remove it. If you discover a new one, add it. Treat the statement as part of your ongoing accessibility work, not a one-off task.

A note on who this applies to

Not every business is bound by the EAA’s service requirements. Microenterprises providing services, defined as fewer than 10 staff and an annual turnover or balance-sheet total of no more than €2 million, are exempt from those service requirements. Even so, publishing a statement remains good practice and a straightforward way to welcome more customers.

For more, see our complete accessibility guide, the background on the Accessibility Act, and who must comply with the EAA.

This article is educational and does not constitute legal advice.