Accessibility statement generator
Answer a few questions about your website and get an accessibility statement in plain English, laid out like the GOV.UK sample. It's made for parish, town and community councils, but any small organisation can use it.
Your answers stay in this browser and are never sent to us.
Your result
Fill in the form to begin
Your result appears here straight away. Nothing is uploaded or saved.
How the generator builds your statement
The statement follows the headings in the GOV.UK sample statement, in the same order: who runs the website, how accessible it is, how to contact you, how to report a problem, the enforcement procedure, the technical information, what you’re doing to improve it, and when the statement was prepared.
Each problem you tick is written up twice: once in plain words near the top, for visitors, and once in the technical section with the WCAG 2.2 success criterion it fails. Maps and embedded content from other organisations go under “content that’s not within the scope”, because the regulations treat them differently. You get the result as plain text, for an email or a Word document, and as HTML, for your website’s code view. Anything in square brackets is a gap for you to fill in.
What is an accessibility statement, and who has to have one?
An accessibility statement is a page on your website that tells visitors how well the site works for disabled people, what doesn’t work yet, and how to ask for information in another format. Parish and town councils in England, and community and town councils in Wales, count as public sector bodies. Under the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, you must publish one and keep it up to date.
Charities, community groups and businesses usually don’t have to by law. The generator still works for them, and changes the legal wording to suit.
Before you start: what you’ll need
Have these to hand and the form takes a few minutes:
- the email address people should use to ask for documents in another format, usually the clerk’s
- how long you’ll take to reply, such as 10 working days
- a list of the problems you already know about
- who checked the website, and when
If you haven’t checked the site yet, do that first. Our guide on how to write a parish council accessibility statement walks through a basic check you can do yourself.
Be honest about the problems
Most small council websites have a few known problems: scanned minutes that a screen reader can’t read, photos without text descriptions, or a pale colour scheme. It’s fine to say so. The regulations expect you to list what doesn’t work and say what you’re doing about it. A statement that claims everything is perfect when it isn’t is worse than one that’s honest. If you’re not sure about your colours, try our colour contrast checker.
A note on “disproportionate burden”
You can only claim a disproportionate burden if you’ve written down an assessment weighing the cost of fixing something against the benefit to disabled people. A small budget can be part of that, but “it’s a lot of work” on its own isn’t enough. Most councils don’t need to claim it at all.
Tidying up the draft
The statement includes a paragraph about live video, such as streamed meetings. Delete it if you don’t stream anything. Check the list of things visitors should be able to do, like zooming in to 400% or using a keyboard, and remove any that aren’t true for your site. Then search for square brackets and fill in every gap.
Where to put it and when to review it
Put the statement on its own page called “Accessibility statement”, with a link in the footer so it’s on every page. Review it at least once a year, and whenever the website changes a lot. Update the review date each time. Nothing you type into the form is saved, so keep a copy of the text.
If your council’s website is hard to update, see our websites for parish and town councils. We build and look after the site for £47 a month, and fixes like these can be sent as part of your 10 changes a month.
Questions about this tool
Does our parish council need an accessibility statement?
Yes. Parish and town councils in England and community and town councils in Wales are public sector bodies under the 2018 accessibility regulations. Your website should meet the WCAG 2.2 AA standard as far as you can, and you must publish a statement saying how well it does.
Do charities and small businesses need one?
Usually not by law, as the regulations are mainly for public sector bodies. It’s still good practice, and the Equality Act 2010 expects you to make reasonable adjustments for disabled people. A statement tells visitors how to ask for help.
Will this make our website compliant?
No. The statement describes your website; it doesn’t change it. You still need to check the site, fix what you can and keep the statement up to date.
Do we have to fix all our old minutes and PDFs?
PDFs and other documents published before 23 September 2018 don’t have to be fixed if they’re not needed for your current services. Documents published since then, and anything people need now, such as the latest agenda, should be accessible.
Related free tools
Colour contrast checker
Pale grey text, a white button label on bright orange, a footer you have to squint at: check any colour pair before it goes on your website. Enter two hex codes and you'll see the contrast ratio and whether it passes WCAG.
Open tool → PerformanceWebsite image size calculator
Big photos are the most common reason a small business page feels slow. Enter how many images a page has, their average file size and a connection speed, and see how long the images alone take to download.
Open tool → PlanningWebsite page planner
Not sure how many pages your website needs? Tell us what you sell, where you work and what you can show customers, and the planner suggests the pages worth writing.
Open tool →More ways to improve your website.
Get your business website for £47 a month.
We design it, write it, host it and make your changes. No setup fee, no contract, and your first draft commonly the same day.