UtilibyWritten by the Utiliby editorial team · Last updated October 13, 2026 · Rules and formulas reviewed October 2026
What this free accessibility statement generator does
An accessibility statement tells visitors that you care about accessibility, which standard you follow, how well your site meets it, what is still broken and how to ask for help. This free online accessibility statement generator turns a short form into a complete statement you can publish in minutes. You choose the standard (WCAG 2.2, 2.1, 2.0 or EN 301 549), your conformance status, how you assessed the site, the technologies you rely on, known limitations and your contact details. The tool writes a clear, plain-language statement with an optional region section for the United States, European Union, United Kingdom or Canada.
You get a live preview with a conformance badge, and the finished text as HTML, Markdown or plain text, ready to paste into your CMS or download as a page. Everything runs in your browser, so your details stay private. The result is a template: it is only as good as the facts you enter, and it is not legal advice.
How to create an accessibility statement
- Enter your details. Organization name, website address, contact email, and optional phone and postal address.
- Pick the standard and status. Choose the version of WCAG or EN 301 549 you tested against and your honest conformance level.
- Say how you assessed. Self-evaluation, independent audit, both, or automated and manual testing.
- List technologies and limitations. Tick the technologies your site relies on and write one known limitation per line.
- Choose a region template. General, US, EU, UK or Canada, and add any enforcement body details.
- Generate, check and publish. Review the preview, fix any bracketed placeholders, then copy the HTML or download the file and link it from your footer.
The parts of an accessibility statement
| Part | What to say | Why it matters |
|---|---|---|
| Commitment | That you want the site to be usable by everyone | Sets the tone and shows intent |
| Standard and conformance | For example, partially conformant with WCAG 2.2 AA | The core factual claim |
| Technologies | HTML, CSS, JavaScript, WAI-ARIA, PDF and so on | Required by the W3C model statement |
| Assessment approach | Self-evaluation, audit, tools, dates | Shows how the claim was tested |
| Known limitations | The real problems and, ideally, plans to fix them | Honesty builds trust and can reduce complaints |
| Feedback and contact | Email, phone, form and response time | Lets people get help |
| Enforcement or complaints | Required by EU and UK rules for public bodies | Gives a route if you do not reply |
| Date | When prepared and last reviewed | Shows the statement is current |
Choosing your conformance status honestly
WCAG describes three levels of conformance claim. Fully conformant means the content meets every success criterion at the level you name, with no exceptions. Partially conformant means some parts do not fully meet the standard. Not conformant means most of the content does not meet it. Very few large or frequently updated sites are fully conformant, so partial conformance with a clear list of known problems is the most common and most credible claim. Do not claim a status you have not tested. Overstated statements can damage trust and may create legal risk, particularly where consumer protection or accessibility laws apply.
Region templates: US, EU, UK and Canada
| Region | What the template mentions | Extra steps to consider |
|---|---|---|
| General | Commitment, WCAG and contact details | Add any local rules that apply |
| United States | ADA, and Section 508 where it applies | Offer alternative formats and a clear contact route |
| European Union | Directive (EU) 2016/2102, the European Accessibility Act, EN 301 549, enforcement procedure | Add the national enforcement body and contact details; some member states require a specific model statement |
| United Kingdom | Equality Act 2010, PSBAR 2018, EASS | Public bodies should follow the government model statement and mention disproportionate burden if used |
| Canada | AODA and the Accessible Canada Act | Check the requirements for your province or sector |
These are short starting points. Laws change and apply differently by sector and organisation size, so confirm the details with a professional before relying on them.
Where to publish and how to keep it current
- Use a clear URL such as
/accessibilityor/accessibility-statement. - Link to it from the footer of every page.
- Make sure the statement page itself passes WCAG.
- Review it at least once a year, after major redesigns and after a new audit.
- Update the limitations list when you fix something, with the date.
- Monitor the contact address and reply within the time you promised.
Common accessibility statement mistakes
- Claiming full conformance without testing.
- Leaving no contact details, or an address nobody reads.
- Never updating the date.
- Listing no limitations on a large site with PDFs, video or third-party embeds.
- Burying the page so it cannot be found.
- Copying another organisation's text, including its technologies and limitations, without checking that they are true for you.
- Publishing a statement but not fixing known issues.
Writing a statement people will read
Use plain language, short sentences and active voice. Say what you did and what you plan to do next, with dates if you can. Offer more than one way to contact you, such as email and phone, for people who cannot use one of them. Offer alternative formats (large print, audio, easy read, braille) where you can. A good statement is useful to a person who is stuck on your site right now, not just to a regulator.
What this tool does not do
It does not test your site, decide your conformance level, produce a detailed VPAT, or provide legal advice. It does not know your local legal requirements beyond the short templates. Use the HTML accessibility checker and the WCAG checklist generator on this site to start your assessment, and consider an independent audit.
Accessibility statement, VPAT and ACR: what is the difference?
An accessibility statement is a short public page for your visitors. A VPAT (Voluntary Product Accessibility Template) is the blank form, and an ACR (Accessibility Conformance Report) is the completed version. An ACR goes through each WCAG success criterion, or each Section 508 and EN 301 549 clause, and records whether the product supports it, with remarks. Vendors give ACRs to buyers during procurement. The two documents serve different readers: the statement helps the person using your site today, while the ACR helps an organization decide whether to buy your product. Many organizations publish both, and the findings in one should match the other.
Example wording and tone
Good statements are specific. Instead of we strive to be accessible, say we aim to meet WCAG 2.2 level AA. We tested our main pages in May with NVDA and VoiceOver, and the checkout page does not yet meet success criterion 3.3.8. Name the problem, say what it affects and give a date for the fix when you can. When a person cannot use a feature, say what they can do instead, such as a phone number or an email address that is answered by a real person within the stated time.
Avoid legal-sounding promises you cannot keep, such as fully compliant with all laws. A statement describes the facts about your site, and the facts will change. The date on the page tells readers how current they are, so update it whenever you review or fix something.
A simple process for keeping a statement honest
- Test your key journeys, such as home, search, sign-up and checkout, with an automated checker and by hand, including keyboard-only use and a screen reader.
- Record the failures in the limitations field.
- Fix the most serious items first and update the statement as each is fixed.
- Review the statement at least yearly, and after every major release.
- Keep a log of complaints and how they were resolved.
Privacy
Your entries are used only to build the statement in your browser. They are not uploaded, logged or stored. Close or reload the page and they are gone, so copy or download your statement before you leave.
Related free tools
Use these free online tools together with this one:
- Check a page for accessibility problems with the HTML accessibility checker.
- Work through what to test with the WCAG checklist generator.
- See how your colours look to colour-blind visitors with the colour blind test.
- Check that your sitemap is valid with the sitemap validator.
- Build an accessible signup form with the newsletter signup form generator.
- Mix colours with enough contrast using the color mixer.
Frequently asked questions
What is an accessibility statement?
An accessibility statement is a page on your website that describes how accessible the site is, which standard you aim to meet, any known problems and how people can contact you for help. It is usually linked from the footer on every page.
Do I need an accessibility statement?
Public sector bodies in the EU and UK are legally required to publish one. In the United States there is no general federal requirement for a statement, but publishing one is widely recommended and is often part of settlements and procurement. Many private organisations publish one as good practice. Check the rules that apply to you.
What should an accessibility statement include?
A commitment, the standard used (such as WCAG 2.2 AA), your conformance status, technologies relied on, how you assessed the site, known limitations, contact details for feedback, a response time, any region-specific complaint or enforcement information, and the date of the statement and last review.
Is this statement legally valid?
It is a template, not legal advice, and it does not make your site compliant. A statement is only valid if it is true. Have important statements reviewed by a qualified professional, especially if you are a public body or have contractual or regulatory duties.
Which conformance status should I choose?
Choose the one that matches your real testing. Fully conformant means every success criterion at the stated level is met. Partially conformant means some parts are not. Not conformant means most of the content does not meet it. Most large sites are partially conformant, and honesty is better than an unsupported claim.
Which standard should I choose, WCAG 2.2, 2.1 or EN 301 549?
WCAG 2.2 AA is the current W3C standard and the best default. EU public sector bodies refer to EN 301 549, which currently incorporates WCAG 2.1 AA. Some contracts and older laws still cite WCAG 2.0 AA.
What does the EU template add?
It refers to Directive (EU) 2016/2102 and the European Accessibility Act, uses EN 301 549 and adds an enforcement procedure paragraph. You should add the name and contact details of the enforcement body in your country.
What does the UK template add?
It refers to the Equality Act 2010 and the Public Sector Bodies Accessibility Regulations 2018 and points users who are not satisfied with your reply to the Equality Advisory and Support Service.
Where should I publish the statement?
Put it on its own page, usually at /accessibility or /accessibility-statement, and link to it from the footer of every page so it is easy to find. Keep the page itself accessible.
How often should I update it?
At least once a year and whenever you make big changes to the site, fix a known limitation or change your testing results. Use the last reviewed date field to show that it is current.
Can I use the HTML on my site?
Yes. The HTML uses a simple article with one h1, h2 headings, paragraphs and lists, so it inherits your site styles. Download the file or copy the code into your CMS.
Should I mention third-party content?
Yes. If you embed third-party widgets, videos, chat or payment forms that you do not control, list them under known limitations and explain how users can get help.
What counts as a response time?
It is the number of working days in which you commit to answer accessibility feedback. Five working days is common. Only promise a time you can keep.
Do I need an independent audit?
Not always. Self-evaluation is acceptable for many organisations, but an independent audit is stronger evidence and is often expected for public bodies, large organisations and procurement.
Does this tool store my details?
No. Everything is generated in your browser and nothing is uploaded or stored. Reloading the page returns the example.
Can I generate a VPAT or ACR with this?
No. A VPAT or Accessibility Conformance Report is a detailed criterion-by-criterion document. Use the WCAG checklist generator on this site to track success criteria and record your results.
What can I print or save?
Print / save as PDF, CSV and Copy summary work on the tab you are viewing. The Preview tab has copy buttons for HTML, Markdown and plain text and a download for a complete HTML file.
Sources and further reading
- W3C Web Accessibility Initiative, Developing an Accessibility Statement, and the W3C accessibility statement generator, for the recommended parts of a statement.
- Directive (EU) 2016/2102 on the accessibility of websites and mobile applications of public sector bodies, and Directive (EU) 2019/882 (European Accessibility Act).
- UK Government Digital Service, Sample accessibility statement, and the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
- W3C WCAG 2.2, Conformance section, for definitions of conformance levels and partial conformance claims.
Sources were consulted in October 2026. Standards and rules can change, so always check the official page for your situation.