Accessibility statement generator

Fill in the form, get a statement following the EU model structure. Everything runs in your browser — nothing you type is sent anywhere, and there is nothing to sign up for.

A statement is a description, not a certificate. Claiming conformance you do not have is worse than admitting problems: it is a written record that can be held against you. Under-promise here. Listing known issues honestly is normal, expected, and protects you.

Who and what

Organisation name As it should appear in a legal document.

Website or service this covers One statement per site or app.

Conformance

Standard you are measuring against

Conformance status

Partially conformant Most of it conforms; some things do not. This is the honest answer for almost everyone.

Fully conformant Only if a full manual audit says so. An automated scan cannot establish this.

Not conformant Work has not started or is at an early stage. Saying so with a plan is respected.

Known problems One per line. Say what is wrong and, if you know, when it will be fixed.

How this was assessed

Contact and dates

Contact email for accessibility problems Must be monitored. An unanswered address is worse than none.

Response time you commit to, in working days

Date this statement was prepared

Your statement

Markdown. Edit it freely — this is a starting point, not a finished document.

Before you publish it: link it from your footer, make sure the contact address works, and set a reminder to review it. Several jurisdictions expect an annual review, and a statement dated three years ago reads worse than no statement at all.

What a statement cannot do

It does not make an inaccessible site accessible, and publishing one does not discharge an obligation. What it does is describe the current position honestly, give people a way to report barriers, and show that somebody is paying attention — which is what enforcement bodies actually look for first.

If you want to know what is wrong before writing the "known problems" section, A11yScope runs the automatable WCAG 2.2 checks on any page in one click. It finds roughly a third of the problems — the rest still needs a person.

More on what the European Accessibility Act requires.