Cost
Free
/ Free tool · accessibility statement

Accessibility statement generator. Free, ready in a few minutes.

EU public bodies must publish an accessibility statement, and many businesses publish one next to what the EAA asks of them. Answer a few questions and get a draft to check and publish, free.

Standards you target

This generator writes the document in English or German. The Polish statutory declaration has a tool of its own.

Fill in the form and your tailored accessibility statement appears here, ready to copy or download.

/ Statement guide

Who needs an accessibility statement, and what has to be in it

An accessibility statement says how accessible a website or app is, what is not, and where to turn when something blocks you. EU public bodies must publish one in a fixed shape. Businesses under the European Accessibility Act owe something related but different.

/ The laws

What each statute says

Web Accessibility Directive

Directive (EU) 2016/2102, Art. 7

Who it binds
Public sector bodies in the EU member states, through national law.
What it requires
A detailed, comprehensive and clear accessibility statement for each website and mobile app, in an accessible format, on the Commission's model, regularly updated. It explains content that is not accessible and why, links to a feedback mechanism and links to the enforcement procedure.
Enforcement
Set nationally. Each member state provides the enforcement procedure the statement must link to.

Model accessibility statement

Commission Implementing Decision (EU) 2018/1523

Who it binds
Statements of public sector bodies under Directive (EU) 2016/2102.
What it requires
Mandatory sections on compliance status, non-accessible content, preparation (date and method), feedback and contact, and the enforcement procedure. Claims must be accurate and based on an actual evaluation, by self-assessment or by a third party, and the method must be named.
Enforcement
Through the national laws that transpose Directive (EU) 2016/2102.

European Accessibility Act

Directive (EU) 2019/882, Art. 13(2) and Annex V

Who it binds
Providers of the services listed in Art. 2(2) to consumers, except microenterprises.
What it requires
Information on how the service meets the accessibility requirements, in the general terms and conditions or an equivalent document, public in written and oral format and accessible, kept for as long as the service runs. The directive does not call it a statement.
Enforcement
Authorities designated by each member state (Art. 23); penalties set nationally (Art. 30).

Behindertengleichstellungsgesetz (Germany)

§ 12b BGG

Who it binds
Federal public bodies in Germany.
What it requires
An Erklärung zur Barrierefreiheit naming content that is not fully accessible, the reasons and any accessible alternative, a direct electronic contact route, and a pointer to the conciliation procedure under § 16 BGG with a link to the conciliation body.
Enforcement
Conciliation procedure under § 16 BGG.

Digital accessibility act (Poland)

Act of 4 April 2019, consolidated text Dz.U. 2023 poz. 1440, art. 10, 11, 19

Who it binds
Polish public entities listed in art. 2 of the act.
What it requires
A deklaracja dostępności for every language version of every website and app, built on the 2018/1523 model plus national items, reviewed by 31 March each year.
Enforcement
Minister for digital affairs: fines up to PLN 5,000 for a missing or incomplete deklaracja and up to PLN 10,000 for unjustified, persistent inaccessibility (art. 19).

BFSG and BFSGV (Germany)

§ 14 and Anlage 3 BFSG, § 12 BFSGV

Who it binds
Providers of the consumer services the BFSG covers, the German law carrying the European Accessibility Act.
What it requires
Information, in the terms and conditions or in another clearly visible way, on how the service meets the requirements: a general description in an accessible format, what is needed to understand how the service is carried out, how it meets the requirements, and the competent market surveillance authority. § 12 BFSGV adds that information about the service is offered through more than one sensory channel and in text formats that can be turned into other accessible formats.
Enforcement
The market surveillance body of the Länder (MLBF). The information is kept for as long as the service is offered.

What a statement is

An accessibility statement is a public page about one website or app. It says how far the service meets a named accessibility standard, lists what does not meet it and why, says how and when that was established, and gives anyone who hits a barrier a working route to report it. Under EU public-sector law it also points to the body that handles complaints the organisation fails to resolve.

A statement that only says the organisation cares about accessibility is not a statement. What makes it one is a conformance status worded as the EU model words it (fully, partially or not compliant), a dated list of the content that does not conform, the assessment method, a contact route and, where the law requires it, an escalation route.

It is not a certificate. Nothing in the directives or national acts cited on this page turns a statement into proof of conformance. It is a claim the organisation makes about itself, and it should be no stronger than the evaluation behind it.

What this generator writes, and what it leaves to you

The English version has five parts: a commitment, the conformance status in the wording of the level you picked (fully, partially or non-conformant) against the standards you ticked, the known limitations if you typed any, a feedback paragraph with your contact address, and an assessment line with the date. The German version has six: the same parts in German, framed by the BFSG, plus a paragraph on the enforcement procedure that names the MLBF, the market surveillance body of the German Länder.

Three things it cannot know. It always says the assessment was a self-evaluation supported by automated testing, so change that line if a third party evaluated the site. It has no date of last review, which the EU model asks for. And the English version has no enforcement procedure, which an EU public body has to add from its national law.

It also does not write the information a business owes under the EAA. In Germany that is the Anlage 3 text: a general description of the service, what a customer needs to understand how it is carried out, how it meets the accessibility requirements, and the competent market surveillance authority. The German statement names the authority. The other three are yours to write, because only you know how your service works.

A worked example

A bakery with an online booking calendar enters its name and address, ticks WCAG 2.1 Level AA, picks partially conformant, gives access@example.com as the contact and types two limitations: the PDF menus have no tags, and the booking calendar cannot be used with a keyboard.

The conformance paragraph comes back as: "Our website (https://example.com) is partially conformant with WCAG 2.1 Level AA. Partially conformant means some parts of the content do not fully conform to the accessibility standard." The known limitations paragraph repeats the two barriers word for word, and the assessment line ends with the date the statement was created.

Before publishing, read it the way a supervisor would. Does partially conformant match what was actually tested? Does each limitation name the function that fails, in words a customer understands? Is there a date for fixing it? Does the contact address reach a person who answers? A public body adds its review date and national enforcement route. If the limitations came from a scan, add what the scan cannot judge.

Who must publish one

EU public sector bodies. Directive (EU) 2016/2102 requires them to provide and regularly update a statement for their websites and mobile apps, in an accessible format and on the Commission's model. A website's statement is published on that website; an app's statement sits on the website of the body that developed it or alongside the download information. Each member state carries this into its own law: German federal bodies under § 12b BGG, Polish public entities under the 2019 digital accessibility act, where the document is called a deklaracja dostępności.

Businesses under the European Accessibility Act. The EAA does not ask for an accessibility statement. Article 13 and Annex V ask a service provider to explain how the service meets the accessibility requirements, in its general terms and conditions or an equivalent document, in written and oral format and accessibly, for as long as the service runs. Germany's market surveillance body says it outright: the accessibility information the BFSG asks of companies is not the same thing as the public-sector Erklärung zur Barrierefreiheit. Poland's 2024 act puts the same information into the service regulations.

Everyone else. Where no law requires one, a statement is voluntary. W3C recommends one anyway, with at least a commitment to accessibility, the standard applied and contact details for users who hit problems. That is the usual position of a US company with no EU public-sector work: none of the EU rules described here makes it publish a statement, and a clear one still helps users and the buyers who ask about accessibility.

What the EU model requires

Implementing Decision (EU) 2018/1523 sets the minimum content for public bodies. Member states may add requirements on top of it. The mandatory part has six elements.

The same decision lists optional content: a commitment beyond the legal minimum with a remediation timeline, formal endorsement, the publication and last substantial update dates of the site or app, a link to an evaluation report (recommended in particular when claiming full compliance), and additional phone support for disabled users. The link to the statement should be easy to find, placed prominently on the homepage or on every page, for example in a static header or footer.

  • Opening and scope: the body commits to accessibility under the national law and names the websites or apps covered, with version and date for apps.
  • Compliance status, one of three: fully compliant only if every requirement of the standard is met without exception; partially compliant if most are met with some exceptions; not compliant if most are not met.
  • Non-accessible content, grouped by reason: non-compliance (in plain terms, naming the requirement not met), disproportionate burden being invoked, or content outside the scope of the law, with accessible alternatives where they exist.
  • Preparation: the date the statement was prepared, the method (self-assessment or an assessment by a third party, such as a certification) and the date of the last review.
  • Feedback and contact: a description of and link to the feedback mechanism, and who handles requests sent through it.
  • Enforcement procedure: a description of and link to the procedure for unsatisfactory responses, with the contact details of the enforcement body.

What a business under the EAA writes instead

Annex V of the EAA sets the content of the service information. Where applicable it contains a general description of the service in accessible formats, the descriptions and explanations needed to understand how the service operates, and a description of how the service meets the relevant requirements of Annex I. The provider must also be able to show that the way the service is delivered and monitored keeps it compliant.

Germany adds one item: Anlage 3 of the BFSG requires the information to name the competent market surveillance authority, which for the BFSG is the MLBF. Poland's 2024 act asks for the information in the service regulations or an equivalent document, published in an accessible way.

A business can publish a voluntary statement page as well, which helps when customers or procurement teams ask for one. It does not replace the terms-and-conditions information. The practical order is to write the Annex V text first and let the statement page summarise it.

How long writing one takes

The writing is the short part. Once an evaluation exists, filling in the model is a matter of hours, because every section is a factual answer: what was tested, against which standard, what failed, who answers feedback, where complaints go.

The evaluation is the long part, and it grows with the service. A small brochure site can be self-assessed quickly. A shop with search, account, checkout and payment needs each of those flows tested with a keyboard and a screen reader, not only with an automated scan. Automated tools find many failures but cannot judge others, such as whether alt text makes sense, so a statement built on a scan alone should say so in its method.

Before starting, collect the list of sites and apps covered, the standard and version tested against, the evaluation report with its date, known failures with planned fix dates, the contact person or team and, for public bodies, the national enforcement route.

How often to review it

The EU model recommends reviewing the accuracy of the claims regularly and at least once a year, and carrying out an evaluation and updating the statement after a substantial revision of the site or app. A review done without a full evaluation still gets its date on the statement.

Some national laws make that a hard deadline. Polish public entities review and update the deklaracja by 31 March every year, and without delay whenever a change could affect accessibility.

For businesses under the EAA there is no annual date but there is a standing duty: service providers keep procedures in place so the service stays compliant, and take account of changes to the service, to the requirements and to the standards they rely on. A template release, a checkout change or a new payment provider is a reason to re-check the information.

Common faults

These are the faults that make a statement useless to the person reading it, or wrong in a way a supervisor will notice.

  • Full compliance claimed after an automated scan, although the model reserves it for every requirement met without exception.
  • No dates, or a preparation date years old with no review date.
  • Non-accessible content described as tool output instead of plain words that name the function that fails.
  • A feedback route that is itself inaccessible, such as a form behind a CAPTCHA with no alternative.
  • No enforcement route on a public-sector statement, or one that names the wrong body.
  • The statement page failing the standard it reports on.
  • A link placed where keyboard and screen reader users never reach it.
  • Under the EAA, a statement page published in place of the information in the terms and conditions, or information that never says how the service meets the requirements.
  • In Germany, Anlage 3 information that leaves out the market surveillance authority.
/ Questions

Questions people ask

Does the European Accessibility Act require an accessibility statement?
Not under that name. The EAA asks service providers for information on how the service meets the accessibility requirements, in the general terms and conditions or an equivalent document. A statement page can sit next to it but does not replace it.
Can I publish what this generator produces as-is?
You can, and many do. Read the limitations section first: it has to describe your service honestly, and only you know what is not conformant yet. An EU public body must also follow its national model, and a business under the EAA still needs the terms-and-conditions information.
How often does a statement need reviewing?
At least once a year, and after any change to your templates or a re-audit. The statement carries the date it was last reviewed, so a stale one shows. Polish public entities have a fixed deadline of 31 March.
What if I do not know my conformance status?
Run the free scan first. It will not give you a legal answer, but it shows whether you are anywhere near level AA before you commit to a wording. A full or partial claim then needs a manual check of the key flows.
Which standard should the statement name?
EU public bodies name EN 301 549 or the national law that points to it; for web content, clause 9 of EN 301 549 V3.2.1 equals WCAG 2.1 level AA. A business names the version it actually tested against, WCAG 2.1 or WCAG 2.2 level AA.
Is the German version a complete BFSG statement?
No. The BFSG does not ask for a statement page. It asks for the Anlage 3 information in the terms and conditions or in another clearly visible way, and the generator writes only the part that names the authority. Publish the German statement as the public page and write the Anlage 3 text next to it.
/ Sources

Where each statement comes from

Checked against the sources on .

This page explains the rules in general terms. It is not legal advice, and it does not tell you whether a rule applies to your organisation. For that, ask a lawyer who practises in the jurisdiction.