Legal & Compliance
Accessibility Statement Generator (WCAG 2.2)
Write an accessibility statement for your website — your WCAG 2.2 conformance target, known limitations, how people can report problems, and the enforcement procedure — in the format used by the UK and EU public sector model.
For general information only — not legal advice. Laws vary by location; consult a qualified lawyer.
How to use
- 1Enter your organisation and site.
- 2Choose your conformance status and list known issues.
- 3Publish the statement and link it from every page.
Frequently asked questions
Is this accessibility statement legally binding?
A document like this is binding when the parties agree to it (and sign where required). Whether each clause is enforceable depends on your local law, so have important agreements reviewed by a lawyer.
Who needs an accessibility statement?
UK and EU public sector bodies must publish one. Since 28 June 2025 the European Accessibility Act also requires many private businesses selling products and services to EU consumers to provide accessibility information. It's good practice for everyone.
What does 'partially compliant' mean?
That some parts of the site don't yet meet the WCAG level you target. List them honestly with a fix date.
Is my information stored?
No. The document is generated in your browser and nothing you type is sent to our servers.
Why 'partially compliant' is the honest default, not a weak answer
The generator defaults to 'Partially compliant' rather than 'Fully compliant' because that's the realistic starting position for almost any existing website — full WCAG 2.2 AA conformance across an entire site, including every legacy PDF and old video, is rare even for organizations that take accessibility seriously. Choosing 'partial' and listing specific known issues (the default example cites inaccessible older PDFs and uncaptioned pre-2024 video) is considered more credible and more useful to a disabled visitor than an unqualified 'fully compliant' claim that a quick screen-reader test could disprove.
Worked example: Accessibility Statement Generator
An organization targeting WCAG 2.2 AA that marks its status as partial, with two known issues, a target of 5 working days to respond to feedback, and a last-tested date of a recent audit, gets a statement reading: 'This website is partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 level AA, due to the issues listed below,' followed by a 'Known limitations' section listing both issues verbatim, and a feedback section promising a reply within 5 working days. Change status to 'Fully compliant' instead, and the known-limitations section disappears entirely — the generator only prints it when status isn't 'full,' so claiming full compliance with issues still listed isn't something the tool will produce.
Why this is increasingly not just a public-sector document
Accessibility statements used to be mainly a UK/EU public-sector requirement, but the European Accessibility Act, in force since 28 June 2025, extends similar information obligations to many private businesses selling products and services to EU consumers — e-commerce, banking, transport booking and more. A private US business with EU customers may now need one even without a direct US legal mandate, which is worth checking against your specific market rather than assuming this only applies to government sites.
What publishing a statement doesn't fix
Writing down 'video content before 2024 has no captions' is a disclosure, not a remedy — the statement documents the gap honestly but doesn't caption the videos. It's most useful alongside an actual remediation plan and periodic re-testing, since a statement that's never updated after the 'last tested' date stops reflecting the site's real state.
An empty test date uses the day you generate the statement
Last tested starts blank. Leave it blank and the how-we-tested line uses the same calendar day as the prepared-on line at the bottom, which is the day you generate the statement. Pick a date and it is written out in full. Reply time starts at 5 working days and stays between 1 and 30. Status starts on partially compliant and the target on WCAG 2.2 AA, with AAA available. Fully compliant drops both the phrase about issues listed below and the known-limitations section, even if the issues box still has text. Partially compliant or not compliant with an empty issues box still says issues are listed below, but it does not print a known-limitations heading. Blank lines in that box are skipped. The page opens as Northwind Studio and northwind.example.
Related tools
- Terms and Conditions Generator
Generate terms and conditions (terms of service) for a website, online shop, SaaS or app — accounts, payments and refunds, acceptable use, intellectual property, liability limits and governing law.
- Cookie Policy Generator
Create a cookie policy listing the cookies your site uses — necessary, preferences, analytics and marketing — with how to manage consent, as required by the GDPR, UK PECR and the EU ePrivacy Directive.
- EU AI Act Risk Checker
Find out which EU AI Act risk category your AI system falls into — prohibited, high-risk, limited risk (transparency) or minimal risk — plus general-purpose AI model duties, the obligations that apply and the key deadlines.
- Privacy Policy Generator (GDPR, UK GDPR & CCPA)
Create a privacy policy for your website or app — what you collect, why, who you share it with, cookies, retention, and the rights sections GDPR, UK GDPR and California (CCPA/CPRA) require. Download as Word or PDF.
- Website Accessibility Checker (WCAG 2.2 Quick Scan)
Scan a web page for common WCAG 2.2 accessibility failures — missing alt text, unlabelled form fields and buttons, empty links, heading order, page language and title, disabled zoom and more — with fixes for each.
- Word Accessibility Checker
Check a Word document for accessibility problems: missing alt text, skipped or fake headings, tables without header rows, unclear links, low-contrast text, typed lists and more, each tied to its WCAG rule. Add alt text, a title and the language, and save a fixed copy.