Free Tool

Accessibility Statement Generator

Fill in a short form and get a properly-formatted accessibility statement you can copy or download as Markdown. The template is aligned with the W3C Web Accessibility Initiative's guidance on accessibility statements and references your chosen WCAG conformance target.

# Accessibility Statement for [Your organization]

[Your organization] is committed to ensuring digital accessibility for people
with disabilities. We are continually improving the user experience
for everyone and applying the relevant accessibility standards.

## Conformance status

The Web Content Accessibility Guidelines (WCAG) define requirements
for designers and developers to improve accessibility for people
with disabilities. They define three levels of conformance: Level A,
Level AA, and Level AAA. [your website URL] is partially conformant with
WCAG 2.1 AA.

Partially conformant means that some parts of the content do not fully conform to the accessibility standard.

## Feedback

We welcome your feedback on the accessibility of [your website URL].
Please let us know if you encounter accessibility barriers:

- Email: [contact email]

We try to respond to feedback within 5 business days.

## Date

This statement was prepared on 2026-05-28.

This is a starting template — review it against your actual site and any specific regulatory obligations before publishing.

Why publish an accessibility statement

A published accessibility statement is one of the simplest, cheapest signals of good faith your site can offer. It tells users with disabilities that you have thought about them, names the standard you are trying to meet, and gives them a way to report problems instead of giving up or filing a complaint. For public-sector projects in the United States, Section 508 and many state procurement rules effectively require one. For government and education vendors in the EU, the Web Accessibility Directive requires a conforming statement on every public-facing site. Even where it is not strictly required, a clear statement reduces friction with procurement teams, auditors, and accessibility researchers.

What goes in a real statement

The W3C Web Accessibility Initiative recommends that a statement include, at minimum, your commitment to accessibility, the conformance status against a named standard (typically WCAG 2.1 AA today), any known limitations you are aware of, and a clear contact path so users can report issues. Many of the statements published on the web fail on the "known limitations" piece — they claim full conformance with no caveats, which is rarely true and undermines the document's credibility. It is better to honestly list the parts of the site that are still being worked on, the date you last reviewed conformance, and the date of the most recent substantive update.

Where to publish it

The de facto convention is to publish the statement at /accessibility on your domain and link to it from your global footer. Some organizations also link to it from the contact page and the help center. Whatever you pick, keep it reachable from every page — that is what users with assistive technology will look for first, and it is what auditors and procurement reviewers will look for too.

How often to review it

Review and refresh the statement at least once a year, and any time you ship a substantive redesign, replatform, or add a major new flow such as checkout, account creation, or a booking system. If you remediate a known limitation, remove it from the statement. If you uncover a new one, add it. Treat the statement as living documentation, not a one-time legal artifact.

The statement is not the work

Most importantly: publishing a statement is not a substitute for actually doing the accessibility work. A polished statement on a site that fails dozens of WCAG criteria is, if anything, worse than no statement at all — it documents that you knew and did not act. Before publishing, scan your site, fix what you can find, and use the "known limitations" section to honestly disclose what remains. A short, accurate statement with a clear remediation roadmap is far stronger than a long one full of unverified claims.

This page and the generated statement are informational and are not legal advice. Accessibility obligations vary by site, organization, and jurisdiction. For legal guidance, consult qualified counsel. The generated statement is a template — you are responsible for verifying that its claims about your site are accurate before publishing it.

Most sites can't honestly claim conformance. Scan yours first.

Before you publish a statement claiming WCAG 2.1 AA, run a free scan to see what your site would actually need to fix. ADA CodeFix surfaces likely failures and generates developer-reviewable code fixes you can ship.

Scan My Site Free