How to Use an Accessibility Statement Generator
An accessibility statement is one of the simplest, highest-impact accessibility documents you can publish. This guide explains what it must contain, why it matters legally, and how to use an accessibility statement generator to create a compliant statement in minutes — without copying boilerplate that does not match your site.
What an accessibility statement actually is
An accessibility statement is a public page that tells visitors how accessible your website is. It states the standard you are targeting (almost always WCAG 2.1 or 2.2 Level AA), whether you currently meet it, what is not yet accessible, and how someone can report a barrier or request information in another format. It is a transparency document, not a marketing page — and that honesty is exactly what regulators and users expect.
A generator helps because the structure is standardised. Rather than writing legal language from scratch, you answer a short set of questions and the tool assembles a statement that follows the recognised template. You can create one with the FixMyWeb accessibility statement generator and adapt the output to your situation.
Why you need one in 2026
The legal backdrop has tightened. The European Accessibility Act is now enforced across EU member states, and covered businesses are expected to document their conformance. In the US, ADA-related web accessibility cases continue to rise each year, and a clear statement is a standard part of demonstrating good faith. Public sector bodies in the EU and UK have published statements as a hard requirement for years. Even where no specific law names it, a statement reduces risk and improves trust.
Before you write the statement, it helps to know where your site actually stands. Run a free accessibility scan so the limitations you declare are based on real findings rather than guesswork.
What a compliant statement must include
A generator should prompt you for each of these. If it skips any, add them manually:
- Conformance target. The standard and level you aim to meet, for example WCAG 2.2 Level AA.
- Conformance status. Whether the site is fully conformant, partially conformant, or not conformant.
- Known limitations. An honest list of content or features that are not yet accessible, with a note on planned fixes.
- Feedback mechanism. A contact email or form, and the time within which you aim to respond.
- Preparation and review dates. When the statement was written and last reviewed.
- Testing approach. The tools, browsers, and assistive technologies used to evaluate the site.
Step-by-step: from scan to published statement
The process is short when you do it in the right order:
- 1. Audit first. Scan your site so you know which WCAG criteria pass and which fail. Use the WCAG audit to get a per-criterion breakdown.
- 2. Decide your conformance status. If material issues remain, you are partially conformant — and that is fine to declare, provided you list the gaps.
- 3. Generate the statement. Enter your organisation name, contact details, target standard, and known limitations into the generator.
- 4. Review the output. Make sure every limitation is accurate and that the contact route works. Never publish a statement claiming full conformance you have not verified.
- 5. Publish and link it. Place the statement in your footer so it is reachable from every page, and set a calendar reminder to review it annually.
Common mistakes to avoid
The biggest mistake is copying a competitor’s statement and claiming full WCAG conformance you have never tested. An inaccurate statement is worse than none: it can be used as evidence that you misrepresented your accessibility. Other frequent errors include leaving out a feedback channel, forgetting to date the statement, and never revisiting it after the site changes. A generator solves the structure; you are still responsible for the truth of the content.
Frequently asked questions
What is an accessibility statement?
An accessibility statement is a public page on your website that describes how accessible your site is, which standard it targets (usually WCAG 2.1 or 2.2 Level AA), any known limitations, and how visitors can report problems or request content in an alternative format. It signals your commitment to accessibility and is a documented requirement under several laws.
Is an accessibility statement legally required?
It depends on your jurisdiction and sector. Public-sector bodies in the EU and UK are explicitly required to publish one, and the European Accessibility Act expects covered businesses to document conformance. In the US, while the ADA does not name a statement by regulation, a clear statement is considered a best practice and is commonly referenced in remediation. When in doubt, publish one.
What should an accessibility statement include?
At minimum: the conformance target (e.g. WCAG 2.2 Level AA), the conformance status (fully, partially, or not conformant), any known non-accessible content, the date it was prepared and last reviewed, the technologies and assistive tech it was tested with, and a feedback mechanism with contact details and a response time.
How often should I update my accessibility statement?
Review it at least once a year, and whenever you make a significant change to your site or complete a new accessibility audit. The statement should always reflect the current state of the site, including any limitations you are actively working to fix.
Create your statement
Once you know where your site stands, generating the statement takes minutes. Start with a free accessibility scan, confirm the details with a WCAG audit, then use the accessibility statement generator to publish a compliant, honest statement for your website.