Free Accessibility Statement Generator

An accessibility statement is a page on your website that declares how accessible your site is, which standard you measure against (such as WCAG 2.1 AA / EN 301 549), any known limitations, and how users can give feedback or request help. It signals good faith, gives users with disabilities a contact route, and is expected practice under EU accessibility rules.

Publishing an accessibility statement is the expected practice for services covered by the European Accessibility Act, and it is a strong signal that you are meeting your obligations in good faith. Enforcement is national: France, for example, imposes a separate €25,000-per-year penalty specifically for a missing accessibility statement, on top of fines for non-conformance. Even where no fixed penalty exists, a published statement plus supporting audit records is the documentation regulators look for.

Yes — it runs entirely in your browser, with no account and no sign-up. You fill in your details, the statement builds live, and you can copy the text, copy the HTML, or download a ready-to-publish HTML file. Nothing you type is sent to a server.

A complete statement, following the EU model structure, includes: a conformance status (fully, partially, or not conformant with the standard); a list of any non-accessible content; how and when the site was assessed; and feedback and contact information so users can report barriers. This generator produces all four sections.

For the web, the answer is almost always WCAG 2.1 Level AA. It is the standard the European Accessibility Act references through EN 301 549, and the same benchmark used by the ADA in the US and AODA in Canada. The generator lets you frame the statement for the EAA/EN 301 549, WCAG 2.1 or 2.2 AA, or ADA/Section 508.

Only if it genuinely is. Declaring "fully conformant" when your site still has gaps is worse than an accurate "partially conformant" statement — it can undermine the good faith the statement is meant to show, and it misleads users who rely on it. Be honest about known issues and show that you are working on them; that is what regulators and disability advocates expect.

Publish it at a stable, easy-to-find URL — commonly yoursite.com/accessibility — and link to it from your website footer so it is reachable from every page. Keep the date current and update the known-issues list whenever your site changes; a statement dated two years ago with no updates signals neglect rather than good faith.

No. An accessibility statement documents your conformance and your feedback route — it does not, on its own, make the underlying site accessible. It works alongside the actual work: scanning your pages against WCAG 2.1 AA, fixing the issues, and keeping supporting audit records. Use the statement to declare where you stand, not to substitute for the fixes.