Accessibility Statement

A WCAG accessibility statement that states what you actually meet, names known issues, and gives people a route to report problems.

100% free. Runs entirely in your browser - your files and data never leave your device and nothing is uploaded to any server.

Template, not legal advice. This is a template, not legal advice. It only describes what you tell it, so the conformance level you claim must be one you can evidence - an overstated claim is a liability rather than a shield. If you are a public sector body in the UK or EU, the required wording and the enforcement route are prescribed by regulation, and you should check the current government guidance against what this produces.

Start from an example

Fills every answer with a worked example you can edit. Pick the one closest to your business.

0 of 8 details filled
Your organisation
What you are measuring against
Claim "fully conforms" only after an audit. An untrue claim here is worse than no statement, because it is a representation you can be held to.
How you know

Claim only what you can evidence. An overstated claim here is a liability rather than a shield.

What is not right yet

Naming real problems with a fix date is what makes a statement credible.

Name them. A statement that lists real issues and a fix date is credible; one that claims none is not.
Where you operate
Public sector bodies in the UK and EU have a legal duty to publish a statement in a prescribed form. This adds the enforcement paragraph that duty requires.

Accessibility Statement

8 sections · 577 words · updates as you type

Accessibility Statement

Last updated: 13 September 2026

Our commitment

[Your organisation] wants [your website] to be usable by as many people as possible. That means you should be able to:

  • navigate the whole site using a keyboard alone
  • use it with a screen reader such as NVDA, JAWS, VoiceOver or TalkBack
  • zoom to 200% without text being cut off or overlapping
  • change colours, contrast and text spacing in your browser without breaking the layout
  • read text that contrasts sufficiently with its background

We treat accessibility as part of building the site rather than as a task that finishes, which is why this statement lists what is not right yet as well as what is.

How accessible this site is

This site partially conforms to the Web Content Accessibility Guidelines version 2.2, Level AA.

"Partially conforms" means most of the site meets the standard but some parts do not. The problems we know about are listed in the next section. We would rather tell you about them than let you find them.

Known problems

We are not currently aware of any part of the site that fails the standard above. That is not the same as there being none, so if something does not work for you, please tell us.

Content we do not control

Some parts of the site are supplied by third parties - embedded maps, video players, payment forms and similar. We choose which of these to use and we raise accessibility problems with the suppliers, but we cannot change their code ourselves.

If one of these blocks you from doing something, tell us what you were trying to do. We can usually offer another way to do it, and knowing which embed caused the problem helps us push the supplier or replace them.

If something does not work for you

Email [your contact email] and tell us:

  • the page you were on
  • what you were trying to do
  • what happened instead, and what you were using at the time (browser, screen reader, magnifier)

We reply within five working days. If you need something the site cannot give you - a document in large print, a form completed over the phone, information in another format - ask, and we will find another way to provide it.

Technical information

[Your organisation] is committed to making this site accessible in accordance with the Web Content Accessibility Guidelines version 2.2, Level AA.

The site relies on HTML, CSS and JavaScript. It is built to work with current versions of Chrome, Edge, Firefox and Safari, and with the assistive technology those browsers support. Accessibility depends partly on the browser and assistive technology you use, and a very old combination may not work as intended even where the site itself conforms.

How we tested this

This site was last reviewed in [date of last review] using automated accessibility testing tools, supported by manual keyboard checks.

Automated tools catch roughly a third of accessibility problems. They cannot judge whether alt text is meaningful, whether a heading structure makes sense, or whether a custom control behaves correctly with a screen reader. We are honest about that limit, and we plan to arrange a fuller assessment.

What we are doing next

Accessibility is checked as part of building anything new here, not audited afterwards: new components are tested with a keyboard and a screen reader before they ship, and contrast is checked at design stage.

The items listed above are prioritised by how much they block someone from completing a task, not by how easy they are to fix.

This statement is reviewed whenever the site changes substantially, and at least once a year.

Generated from a template. Not legal advice - read it before you publish or sign it.

Other documents you can generate

Most sites need more than one. A privacy policy without terms, or terms without a refund policy, leaves the obvious gap.

Privacy PolicyA privacy policy written from what your site actually does - GDPR and CCPA sections included only where they apply.Terms and ConditionsTerms of service built around what you actually sell - goods, subscription, downloads or services.Cookie PolicyA cookie policy with a real table - each cookie named, with its purpose and how long it lasts.Cookie Consent BannerGenerates a working consent banner - blocks tagged scripts until consent, Google Consent Mode v2, no dark patterns.Refund and Return PolicyA refund policy customers can follow and payment processors accept - windows, exclusions and statutory rights in plain words.Website DisclaimerA disclaimer that names the actual risk your site carries, plus affiliate and sponsorship disclosures.Non-Disclosure AgreementA mutual or one-way NDA with a real purpose clause, standard carve-outs and a defined term.Freelance ContractAn independent contractor agreement that pins down scope, revisions, IP ownership and what happens when payment is late.Data Processing AgreementA GDPR Article 28 processor agreement with the eight mandatory clauses and a filled-in processing schedule.W-9 FormFills a substitute Form W-9 in your browser - your TIN is never uploaded, stored or sent anywhere.1099-NEC Contractor SummaryPrepares a 1099-NEC recipient statement and a payer summary - with a straight answer about what you can and cannot print yourself.Shipping PolicyA shipping policy Shopify and Amazon sellers can publish - origin, times, tracking, duties and who pays.DSAR Form GeneratorA data-delete and access request page you can host - GDPR and CCPA wording, no upload, no signup.

Jump to the next useful tool without leaving your flow.

See more

About this tool

Answer a handful of questions and the document writes itself. It exists for public sector bodies, anyone selling to them, and any business that would rather answer an accessibility complaint than an ADA demand letter, and after you have tested the site, not before - the statement reports findings rather than intentions is when it is worth twenty minutes. The thing worth knowing before you start: this is the one document where claiming less protects you more. An unaudited claim of full WCAG 2.2 AA conformance is a representation that can be used as evidence against you; a statement listing three known problems with a fix date is credible and is what the regulations actually ask for. The questionnaire is not decoration. Clauses appear and disappear based on what you tell it, which is why two people using this page get materially different documents rather than the same text with a different name at the top. Everything runs in your browser. What you type is never uploaded, never stored, and gone when you close the tab - which matters here more than on most tools, because these documents carry company details, client names and sometimes tax identifiers.

How to use this tool

  1. Answer the questionsOrganisation name. Website or app this covers. Accessibility contact email. Nothing you type leaves the browser.
  2. Watch it assembleClauses appear and disappear as you answer, so the document matches what you actually do rather than a generic template.
  3. Copy or downloadCopy the text, or download as PDF, Word or plain text. The Word version is the one to edit.

Key features

  • Downloads as PDF, Word or plain text - the Word file is editable with no protection on it.
  • Runs entirely in your browser. Nothing uploaded, nothing stored, no account.
  • Free with no watermark, no email wall and no per-document limit.
  • Built from your answers, so clauses you do not need are left out rather than padded.
  • Says plainly what it is and is not, above the preview rather than in a footer.

Common uses

  • Replacing a copied document that describes a different business.
  • Getting something in place after you have tested the site, not before - the statement reports findings rather than intentions.
  • Public sector bodies, anyone selling to them, and any business that would rather answer an accessibility complaint than an ADA demand letter.
  • Preparing what a client, an app store or a payment processor has asked to see.
  • Giving a lawyer a draft to review rather than paying them to start from nothing.

Tips for better results

  • Download the Word version if you expect to edit it. The PDF is for publishing; the .docx is for changing.
  • Publishing a statement with no contact route. The entire mechanism assumes a person who hits a barrier can tell you, and a statement that ends without an email address fails the only test that matters to the person reading it.
  • Pair it with Disclaimer. Publishing one without the other leaves the gap people notice first.
  • Keep a copy of each version with its date. When someone asks what your terms said last March, the answer needs to be a file rather than a memory.

Mistakes to avoid

  • Publishing a statement with no contact route. The entire mechanism assumes a person who hits a barrier can tell you, and a statement that ends without an email address fails the only test that matters to the person reading it.
  • Treating a generated draft as a reviewed one. This is a starting point, and where the stakes are real it is worth a professional reading it.
  • Hiding it. A document nobody can find does not do its job - it belongs in the footer of every page.
  • Publishing it and never looking again. These go stale - you add a tool, change a processor, start selling somewhere new, and the document still describes last year.

Frequently asked questions

Answer the questions on the left. The document builds as you type, and you can copy it, or download it as PDF, Word or plain text when it looks right.

No. It assembles a draft from standard clauses, and every page says so above the preview. US web accessibility lawsuits run into the thousands per year, and the first thing a plaintiff firm checks is whether the site claimed conformance it did not have.

Publishing a statement with no contact route. The entire mechanism assumes a person who hits a barrier can tell you, and a statement that ends without an email address fails the only test that matters to the person reading it.

Most people need Disclaimer and Privacy Policy as well. They cover the gaps this one does not.

Yes. Download the Word version and change anything you like - it is a normal .docx with no protection on it.

Broadly, public sector bodies, anyone selling to them, and any business that would rather answer an accessibility complaint than an ADA demand letter. The best time to do it is after you have tested the site, not before - the statement reports findings rather than intentions.

No. Everything happens on your device - nothing is sent to a server, nothing is stored, and closing the tab clears it.

People also search for

  • accessibility statement generator for small business
  • free accessibility statement generator
  • accessibility statement generator
  • accessibility statement generator uk
  • accessibility statement generator no signup
  • accessibility statement generator template
  • accessibility statement generator usa

Related guides