EAA Accessibility Statement Example for Ecommerce Stores

An accessibility statement is not magic. It does not make an inaccessible store accessible, and it should never claim "fully compliant" if that is not true.

Used properly, it does three things:

1. tells customers what standard you are working toward;
2. explains what you have already tested and fixed;
3. gives a real contact route for barriers you have not found yet.

For ecommerce stores preparing around the European Accessibility Act, the statement should sit on top of a dated evidence file: test results, manual checks, fixes, known limitations and owners.

This is general guidance, not legal advice. Start with official materials from the European Commission and EUR-Lex, then confirm your market-specific obligations.

Do not publish a perfect-sounding statement

The riskiest statement is the one that sounds reassuring but cannot be evidenced:

• "Our site is fully accessible."
• "We are 100% EAA compliant."
• "This website meets all accessibility standards."
• "Our widget makes the site compliant."

If those claims are not true, they create trust risk. A better statement is specific, dated and honest.

A safer structure

Use this structure as a draft framework:

1. Scope

Name the store, the domain, and the pages or journeys covered by the review.

Example:

This accessibility statement applies to the customer-facing ecommerce journey at example.com, including the homepage, collection pages, product pages, cart and account forms.

2. Target standard

Say what you are working toward without overclaiming.

Example:

We aim to make this store usable by as many people as possible and are working toward WCAG 2.1 AA aligned accessibility for the main shopping journey.

3. Current status

Be honest. "Partially conformant" is often more credible than "fully conformant."

Example:

Based on our latest self-assessment dated 19 June 2026, the store is partially conformant. We have identified and fixed several issues, and we are still working through the limitations listed below.

4. What has been tested

List the actual tests, not vague intent.

Example:

We tested keyboard navigation, focus visibility, form labels, error messages, image alternatives, heading structure, landmark structure, colour contrast and the product-to-cart journey.

5. Known limitations

Name the remaining issues plainly.

Example:

Known limitations: some older product images still need better alternative text; one third-party review widget has limited keyboard behaviour; several promotional badges need contrast review.

6. Contact route

Give a monitored route and expected response time.

Example:

If you experience an accessibility barrier, email support@example.com with the page URL, the issue, and the assistive technology or browser you used. We aim to acknowledge reports within five working days.

7. Review date

State when the statement was last updated and who owns it.

Example:

This statement was last updated on 19 June 2026 and is owned by the store operations lead.

The evidence file behind the statement

The statement is the public surface. The evidence file is the private proof.

Keep:

• automated scan results;
• manual keyboard-test notes;
• screenshots of fixed issues;
• dates of fixes;
• owner names;
• unresolved issues;
• third-party app notes;
• customer barrier reports and responses;
• planned next review date.

If a B2B buyer or regulator asks what you have done, the evidence file is the answer.

Where the pack helps

The EAA Conformity Evidence Pack generates a draft accessibility statement from your own inputs, plus a dated conformity dossier and manual-test record. If you are not ready to buy, start with the free Accessibility Quick-Scan and use the results to populate your first evidence log.

The tool is not a certification and it does not replace professional review. It gives you a structured, honest record to take into that review.

FAQ

Can I copy an accessibility statement from another ecommerce site? Use another statement for structure only. The facts must be yours: your pages, your tests, your known limitations and your contact route.

Should I say my store is EAA compliant? Only if you can stand behind that claim with qualified review and evidence. Most stores should use more careful wording such as "working toward" or "partially conformant" until verified.

Do I need to mention third-party apps? Yes, if they affect the user journey. Reviews, chat widgets, payment widgets and loyalty apps can all introduce accessibility barriers.

How often should I update the statement? Update it after material theme changes, new apps, major fixes, customer barrier reports or scheduled accessibility reviews.

Bottom line

An accessibility statement is not marketing copy. It is a dated accountability document. Keep it specific, keep it honest, and keep the evidence behind it.