Skip to main content

EU accessibility statements

Accessibility statement generator for EU online stores

Turn a WCAG 2.1 AA scan of your shop into an accessibility statement you can review, sign and publish yourself — in any of the 24 official EU languages. A declaration built from findings rather than from a questionnaire.

The scan is free and needs no account. Statement generation, versioning and retention require Starter or higher.

Inside the document

Accessibility statement

Compliance status

Self-declared by the provider

Partially compliant, pending the non-compliances listed below

Non-accessible content

  • Non-compliances
  • Disproportionate burden (Art. 14)
  • Content outside the scope of the applicable law
  • Feedback and contact information
  • Legal basis
  • Signed by

These are the actual headings your statement carries — read from the same source the PDF renders from, so this preview cannot drift from the product.

What goes into the statement

The document follows the European model accessibility statement — the structure established for public-sector bodies by Commission Implementing Decision (EU) 2018/1523 and now the common template across the EU. It is the shape auditors and national authorities expect. Note that it is a template, not a form the EAA itself prescribes for private e-commerce.

  • A compliance status you declare yourself

    Fully, partially, or not compliant with the standard. It is a self-declaration by the provider — no third party signs it off for you, and the document says so in those words, where a reader can see it.

  • Non-accessible content, split three ways

    Non-compliances, content exempted as a disproportionate burden, and content outside the scope of the applicable law. Three different claims, and the model statement deliberately keeps them apart. Collapsing them into one list weakens all three.

  • A way to complain, and somewhere to escalate

    A feedback mechanism, a contact address, and the enforcement body a user can turn to when you do not reply. Leave the escalation route out and the statement stops doing the one job it has.

How the generator works

  1. 01

    Scan the shop

    We crawl your pages and test them for machine-detectable WCAG 2.1 AA failures. What the scan finds becomes the draft — not what you remember about your site.

  2. 02

    Review the draft

    The status is never pre-filled as fully compliant. AI-drafted descriptions are flagged until a human has read them, and a flagged draft is refused at finalisation rather than quietly going out.

  3. 03

    Finalise and download

    Finalising versions the statement and mints a tagged, screen-reader-navigable PDF you download and publish on your own site. Finalise again without changing anything and you get the same document back, not a duplicate.

What remains your responsibility

  • This is not statutory certification. The statement is provider-authored accessibility information; no official EU accessibility certificate exists for it to stand in for.

  • It does not prove conformance. Automated testing finds violations; it cannot prove there are none. Our own reports say “no automated violations”, never “meets”.

  • It is not legal advice. We supply the transposing statute, the supervisory authority and the penalty ceiling for the countries we cover. What you declare remains your decision.

  • It does not write your compliance status. The model drafts descriptive prose only. The status, the legal citations and the penalty figures are fixed by us and never model-generated.

  • It does not publish for you. You download the PDF and put it on your own site, and you decide when a change is material enough to re-issue it.

Country-specific legal basis

For three countries the statement fills in the transposing statute, the supervisory authority and the penalty ceiling:

  • Polski

    Statute
    Ustawa z dnia 26 kwietnia 2024 r. o zapewnianiu spełniania wymagań dostępności (Dz.U. 2024 poz. 731)
    Supervisory authority
    Minister właściwy do spraw informatyzacji / PFRON
  • Deutsch

    Statute
    Barrierefreiheitsstärkungsgesetz (BFSG) §14 / Anlage 3
    Supervisory authority
    Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF), Magdeburg
  • Čeština

    Statute
    Zákon č. 424/2023 Sb., §14
    Supervisory authority
    Česká obchodní inspekce (ČOI)

Selling elsewhere in the EU? The statement still generates, but without a country-specific legal block — that is limited to the three above while we verify the remaining transpositions. We would rather leave a field out than print a statute we have not checked.

In the language your customers actually read

Produce the statement in any of the 24 official languages of the European Union. Statutes and supervisory authorities are named as the law names them, not translated into an approximation.

Questions worth answering before you start

Does the European Accessibility Act require an accessibility statement?
The EAA requires providers of services in scope to publish information on how the service meets the accessibility requirements — that duty comes from Article 13 and Annex V, and it has applied since 28 June 2025. The EAA does not prescribe the model statement format this generator produces; that template comes from the public-sector accessibility rules and has become the common European practice. Microenterprises providing services — fewer than 10 staff and up to €2M turnover — are exempt, though products placed on the market stay in scope.
Can I generate the statement for free?
The scan is free and needs no account. Statement generation, versioning and retention require Starter or higher. The free scan is useful on its own: it tells you what a statement would have to admit.
Does publishing a statement make my store compliant?
No. The statement declares where you stand; it does not move you. If the scan finds missing alt text or failing contrast, your statement will say so until you fix them — which is precisely what it is for.
Who signs it?
You do. You can record a signatory name and role, and the document is dated and versioned. The declaration belongs to the provider. We generate the document, not the responsibility that comes with it.
What happens when my shop changes?
A statement goes stale. We re-scan on a monthly cycle and flag a statement once it passes a year old, so you find out that your site has moved on. Updating what you published is a step you take — a re-scan never edits a statement you have already issued.

Start with the scan. The statement follows.

One free scan, no account, no card. It tells you what your statement would have to say before you commit to anything.

Run a free scan