Skip to main content
WCAGrules
Quick navigation

Free tools · Generator

Accessibility statement generator

The EAA, BFSG, RGAA, and UK regulations all expect a published accessibility statement, and regulators check for it first, because it is the easiest violation to spot. Generate yours in two minutes: fill the form, pick your laws, copy or download.

Laws that apply to you (optional)

Your statement

Accessibility statement for [Organization name]

[Organization name] is committed to making [website address] accessible to everyone, including people who use screen readers, keyboard navigation, voice control, magnification, and other assistive technology.

Conformance status
This website is partially conformant with WCAG 2.2 Level AA. Partially conformant means some parts of the content do not yet fully meet the standard; they are listed below and fixes are in progress.

Technical standard
Accessibility is assessed against WCAG 2.2 Level AA, the Web Content Accessibility Guidelines published by the W3C.

Feedback and contact
If you encounter an accessibility barrier on this site, please tell us: [accessibility contact email]. Describe the page and the problem, and we will respond within 5 business days and fix verified barriers as quickly as we can.

Enforcement and escalation
If you are not satisfied with our response, you may escalate to [name the enforcement body for your jurisdiction, with its address, email and telephone number]. Several accessibility laws require this body to be named here rather than described, so replace the bracket before you publish.

How this statement was prepared
This statement was prepared on September 7, 2026, based on [say how you assessed the site, for example a self-assessment against WCAG 2.2 Level AA or an audit by a named third party, and give the date of that assessment].

A statement describes your accessibility. It never creates it, and a draft out of a generator creates it least of all, because every word above is a claim about your site that only your own testing can stand behind. “Fully conformant” is the sharpest example. Anyone can test it, including the regulator reading it, so pick the status you could defend if they did. An audit is how you find out which one that is. Two more things this cannot do for you. Where a law sets its own model for the statement, as the European rules do for public sector bodies, that model asks for the enforcement body by name with its contact details, and only you know which body that is. And the known-limitations list is the part a reader trusts you for, so an empty one on a real site reads as a page nobody tested.

A statement is a claim, not a shield

Publishing “partially conformant” is honest; publishing “fully conformant” over a broken checkout is evidence against you. Base the status on testing: start with the free scan, then let the human audit give you a status, and a known-limitations list, you can defend.

Go somewhere useful

Find tools, resources and your workspace.

29 destinations