Kerbly

Accessibility statement generator

Answer a few questions and get a clear, honest accessibility statement for your website, ready to paste. Free, no sign-up, and nothing leaves your browser.

About you

Where your site stands

Standard you aim for

WCAG 2.2 is the newest. If you are not sure, keep it.

How well does the site meet it today?
How have you checked it?
Known gaps you want to be upfront about

Your statement

Still to fill in: organisation name, website address, contact email.

Accessibility statement for [Your organisation]

Our commitment

[Your organisation] wants [your website address] to be usable by as many people as possible. That includes people who use screen readers, keyboards, voice control or screen magnification, and people with low vision, hearing loss, or motor or cognitive disabilities.

Conformance status

The standard we aim to meet is the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the World Wide Web Consortium (W3C).

This website partially conforms to WCAG 2.2 Level AA. Partially conforms means that some parts of the content do not fully meet the standard yet.

How we checked

We looked at the website in these ways:

  • We reviewed the website ourselves against the standard.
  • We ran automated accessibility scans. These catch many common problems but not all of them.

Feedback and contact

If you have trouble using any part of this website, or you spot something that should be fixed, please tell us. It helps if you include the page address, what you were trying to do, and any assistive technology you use.

We aim to reply within 5 working days and, where we can, to give you the information in another format.

  • Email: [your email address]

About this statement

This statement was prepared on 21 November 2026. We will review it when the website changes significantly, and at least once a year.

This tool gives you a starting template, not legal advice. Only publish what is true for your site, and check the rules that apply in your country. Public sector sites in the UK and EU should use their official model statement.

What a good accessibility statement includes

Good statements are short and specific. They tell a visitor what to expect and who to ask when something does not work. Here is what the generator covers, and what you should always keep.

  1. A commitmentOne or two sentences saying you want the site to work for as many people as possible.
  2. The standard you aim forUsually WCAG 2.2 Level AA. Name the version and the level.
  3. Your honest statusFully meets, partly meets, or working towards. Pick the one you can prove.
  4. How you checkedAutomated scans, keyboard testing, screen reader testing, or an outside audit.
  5. Known gapsWhat you already know is not right yet. Being upfront builds trust.
  6. How to reach youAn email address or phone number, and how fast you reply.
  7. The dateWhen you wrote it, so people can tell whether it is still current.

Make it true before you publish it

A statement is only as good as the site behind it. Saying you aim for WCAG 2.2 AA while the site fails the basics invites criticism, not trust. Scan the pages you care about first, fix the big issues, and then describe what is left. Automated scans find roughly a third to a half of real problems, so say “we ran automated scans”, not “we are fully compliant”.

Common things to fix first: low colour contrast, images with no description, and form fields with no label. You can test your colours with the free contrast checker.

Where to put it

Publish it as its own page, commonly at /accessibility, and link to it from the footer of every page. Keep the wording plain. Then put a reminder in your calendar to review it once a year.

Questions people ask

What is an accessibility statement?

It is a page on your website that says how accessible the site is, what you have done to check it, which problems you already know about, and how someone can contact you if they get stuck. It is a plain-language note to your visitors, not a certificate.

Do I legally have to publish one?

It depends on who you are and where you operate. Public sector websites in the UK and EU must publish a statement, usually in an official format. For most private businesses there is no single rule that applies everywhere, but accessibility laws such as the European Accessibility Act and US disability-discrimination claims make a clear statement worth having. This is general information, not legal advice. If you are unsure, ask a lawyer who knows your country.

Will a statement protect me from a lawsuit or demand letter?

No. A statement shows good faith and gives people a way to tell you about problems, which can help. It does not replace fixing the problems, and a statement that claims more than is true can make things worse.

Which conformance status should I pick?

Pick the one you can back up. Most sites should choose "partly meets", which is the honest answer when the site is mostly good but not perfect. Choose "working towards" if you have not done a proper check yet. Only choose "fully meets" if a full audit or thorough testing supports it.

Can I say my website is ADA compliant or fully compliant?

We advise against it unless an expert audit supports it. The ADA does not name a technical standard for most private websites, so "ADA compliant" is hard to prove. Saying which WCAG level you aim for, and how you checked, is more honest and easier to defend.

Where should I put the statement?

Make a page, often at /accessibility, and link to it from the footer of every page so it is easy to find with a keyboard or a screen reader. Make sure the statement page itself is accessible.

How often should I update it?

Review it at least once a year, and whenever you redesign the site, add a major feature, or fix a known problem. Update the date each time. An old statement that no longer matches the site is worse than a short, current one.

Is what I type sent anywhere?

No. The statement is written in your browser as you type. Nothing is uploaded or stored, and there is no sign-up.

I run a UK or EU public sector website. Can I use this?

Use the official model statement for your country instead. Public sector rules require specific sections and wording, and this tool is aimed at businesses and organisations that have no prescribed format.

Check your site before you describe it

A free scan checks your page against WCAG 2.2 and gives you a plain-English list of what to fix.

No account needed. Takes about 30 seconds.