Etoolio

Accessibility Statement Generator

Free accessibility statement generator. Answer a few questions to produce a clear, editable accessibility statement covering your WCAG conformance, known issues, contact details and complaints procedure. Runs in your browser.

Standard you aim to meet
How accessible it is now
How it was tested
Where you operate (sets the complaints wording)

Your accessibility statement

Accessibility statement for this website

This statement applies to this website. It is run by [Your organisation].

We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • change colours, contrast levels and fonts using browser or device settings
  • zoom in up to 400% without the text spilling off the screen
  • navigate most of the website using just a keyboard
  • navigate most of the website using speech recognition software
  • listen to most of the website using a screen reader

How accessible this website is

this website is partially compliant with the WCAG 2.2 AA standard, because of the issues listed below.

Feedback and contact information

If you find a problem, or you need information in a different format such as large print, Easy Read or audio, please contact us.

We will consider your request and get back to you as soon as we can.

Enforcement procedure

If you are not happy with how we respond to your feedback, you can contact the accessibility enforcement body in your EU country. Under the European Accessibility Act, each member state has a body that handles complaints about inaccessible products and services.

Technical information about this website's accessibility

[Your organisation] is committed to making this website accessible, in line with accessibility law.

This website aims to conform to the WCAG 2.2 AA standard of the Web Content Accessibility Guidelines (WCAG).

How we tested this website

This statement is based on our own review of this website against the WCAG 2.2 AA standard.

Preparation of this statement

This statement was prepared on [date].

This generates a solid first draft of an accessibility statement in plain language. Edit it to match your real situation before you publish it, and only claim the level of compliance you have actually reached. An accessibility statement is a public commitment, so it should be honest: it is better to list known problems and your plan to fix them than to overstate compliance. This is general information, not legal advice, and specific duties vary by country. The generator runs entirely in your browser.

Every accessible site needs one honest page

An accessibility statement is the page where you tell people how accessible your website really is, what still needs work, how to get help, and how to complain. Public-sector bodies must publish one, and under the European Accessibility Act many businesses now should too. Writing one from scratch is daunting, so this free generator asks a few plain questions and assembles a clear, editable statement you can publish. It runs entirely in your browser.

What it produces

  • A complete statement covering what it applies to, the standard you aim for, your level of compliance, known problems, how to get help, the complaints route, how you tested, and the date.
  • In plain language, the same clear style accessibility itself calls for.
  • Ready to use: copy it, download it as Markdown or text, or print it, then edit to fit your situation.

Honesty beats a perfect score

The instinct is to claim full compliance, but a statement is a public commitment, and overclaiming is worse than admitting gaps. Regulators and users both respond better to a statement that says "we are partially compliant, here are the specific issues, and here is our plan" than to a bold claim that falls apart on the first page. This generator makes it easy to be honest: list your known issues and it folds them in, so your statement is accurate on the day you publish it.

Set the right complaints route

Where you operate changes what the statement should say about enforcement. The generator adjusts that section for the EU (each member state's accessibility body under the European Accessibility Act), the UK (EASS and the EHRC), the US (ADA and Section 508), or elsewhere, so readers know where to turn if you do not resolve their problem. You can edit the wording to name the exact body that applies to you.

Part of the accessibility toolkit

A statement is a commitment, so back it with action. Use our WCAG 2.2 AA checklist to work through the actual requirements, the colour contrast checker to fix the most common failure, and the Easy Read tools to make key information understandable, then let this generator document where you have got to. This is general information, not legal advice, and duties vary by country, so have someone check the final statement before you publish it. Everything is generated locally and nothing you type is uploaded.

Good to know

Accessibility Statement Generator, frequently asked questions

What is an accessibility statement?

An accessibility statement is a page on your website that says how accessible your site is, lists any known problems, tells people how to get help or an alternative format, and explains how to complain if they are not happy. It is expected of public-sector bodies and, increasingly, of businesses under the European Accessibility Act and equivalent laws. This tool builds a clear, plain-language draft you can edit and publish.

Who needs one?

Public-sector websites and apps are generally required to publish an accessibility statement. Under the European Accessibility Act, many private businesses that sell to consumers, such as e-commerce, banking, e-books, telecoms and transport, are now expected to make their services accessible and to be transparent about it. Even where it is not strictly required, a statement is good practice: it shows you take access seriously and gives disabled users a way to reach you.

What should the statement include?

The essentials are: which website or app it covers, the standard you aim to meet (usually WCAG 2.2 Level AA), whether you are fully, partially or not yet compliant, a list of known problems, how someone can request help or an alternative format, how they can complain and to whom, how the site was tested, and the date it was prepared. This generator asks for each of these and assembles them into a finished statement.

Should I claim full compliance?

Only if it is true. An accessibility statement is a public commitment, so honesty matters more than looking perfect. It is far better to say you are partially compliant, list the specific problems and give a plan to fix them, than to claim full compliance and be caught out. Users and regulators respect a truthful statement with a clear direction of travel.

Can I edit the result?

Yes, and you should. The generator gives you a strong first draft in Markdown that you can copy, download or print, then adapt to your real situation, add your specific known issues, and have someone check before publishing. It is general information, not legal advice, and duties differ by country.

Is it free and private?

Yes. It is free with no signup, and everything is generated in your browser, so none of your details are sent anywhere.