Skip to main content
Scanready Test now

Create an accessibility statement

One form, one finished text. The generator produces the document you actually need — for companies under the European Accessibility Act, for public sector bodies under Directive (EU) 2016/2102. Everything runs in your browser; your entries never leave the page.

RL (EU) 2019/882 · EN 301 549

What this document cannot do

An accessibility statement does not make a website accessible. It is a statement about the actual state of things — nothing more. If you select “partially compliant”, that is exactly what goes into the document, together with the reasons.

That is the difference to vendors who hand you a statement declaring your site accessible in one sweeping sentence. An untrue statement is not protection, it is extra exposure: it is a representation made to consumers and to the market surveillance authority.

So this generator asks for the real state — and offers to measure it first.

Form

Your details

Every field marked “required” is needed. The text is produced when you submit — in the browser, nothing is transmitted.

Who is issuing the statement?

This decides which document you need. The two are frequently confused.

Determines the legal basis and the competent authority in the generated text.

As it appears in your legal notice.

Street, postcode, town.

Website, online shop, app — as your users know it.

The address this statement applies to.

Measure the real state

You can have the address above tested right now. The scanner checks it against EN 301 549 (WCAG 2.1 AA) and writes the result, with the date, into the statement as a tested finding. This usually takes less than a minute.

What do you offer? Two or three sentences are enough.

How is it used — ordering, sign-in, payment, customer support?

Compliance status

Answer honestly. This is the core of the document.

Known non-accessible content

Tick what applies. Every item appears in the text with its success criterion.

Anything not ticked above — one item per line, with a reason if you can.

What do you offer instead of the parts that are not accessible?

Assessment method used

How was the status above established?

When was this statement written?

When was the state last checked?

Name, department or job title.

Must be reachable without signing in.

Only give a number that someone actually answers.

Issued

Your statement

The text is ready. Read it before you publish it — especially the reasons you give.

Beschl. (EU) 2018/1523

What belongs in it

These parts are prescribed by law. The generator sets all of them — the order follows the model statement of Implementing Decision (EU) 2018/1523.

  1. 01

    Provider and service

    Who is issuing the statement and which website, shop or app it applies to. Without that link the document is worthless.

  2. 02

    Compliance status

    Fully, partially or non-compliant — with reasons. For public sector bodies these three levels are prescribed by law.

  3. 03

    Non-accessible content

    Named and explained, plus accessible alternatives where they exist. Sweeping sentences are not enough: the affected areas must be identifiable.

  4. 04

    Date and assessment method

    When the statement was prepared and last reviewed, and how it was assessed — self-assessment, tool or third-party evaluation.

  5. 05

    Feedback mechanism

    A directly available, accessible electronic way to report barriers. Public sector bodies must answer within one month.

  6. 06

    Enforcement procedure or authority

    Public sector bodies name the enforcement or conciliation body. Companies instead name the competent market surveillance authority.

Two documents that are constantly confused

Templates circulate that produce a public-sector style statement for an online shop, complete with a reference to a conciliation body that has no jurisdiction over companies at all. Wrong legal framework, wrong authority.

Public sector bodies issue an accessibility statement under Directive (EU) 2016/2102, using the model of Implementing Decision (EU) 2018/1523. It documents existing shortcomings, names a feedback route and points to the enforcement procedure. It must be reviewed at least once a year and after every substantial change.

Companies fall under Directive (EU) 2019/882, the European Accessibility Act. Annex V requires them to state, in their general terms and conditions or an equivalent document, (a) a general description of the service in accessible formats, (b) the descriptions and explanations needed to understand how the service operates, and (c) a description of how the service meets the accessibility requirements. Individual member states add further requirements — Germany, for example, additionally demands that the competent market surveillance authority be named.

This generator therefore asks first who you are, and only then which country you are in.

Do you need a separate template per region?

For companies: usually not. The European Accessibility Act is transposed as national law, and the competent market surveillance authority is normally a single national body. Regional templates are the same text with a different place name.

For public sector bodies the picture differs by country: some member states have regional legislation and regional enforcement bodies. Germany is the clearest case — every federal state has its own equality act, its own IT accessibility regulation and its own enforcement body. Those differences are handled in the “Legal framework” field on the German version of this page, not as near-identical separate pages.

Note

Legal sources

Checked on 24 August 2026. We name them so that you can read them yourself instead of having to trust us.

Measure first, then declare

A statement is worth exactly as much as the testing behind it. The scanner tells you where your site stands in under a minute.

Test a website See pricing