Skip to main content
Complience.app

Accessibility statement generator

An accessibility statement generator writes a page you can paste onto your site. W3C says that page is for people who hit a barrier, and that it is not a declaration of conformity. Try a sample below. The draft updates on this page.

Try a draft

Pick a sample or type your own details. The preview and the HTML update here. Northwind Studio and Harbor Bakery are examples, not customers. Replace the name, the URL, and the email before you publish.

Sample drafts

Edit this copy so it matches what you actually test. Publishing a statement after an automated scan is not a WCAG or ADA finding.

Preview

Accessibility statement

[Organization] wants [website URL] to be usable by as many people as possible. The target we are working toward: WCAG 2.2 Level AA. Naming a target is not a claim that the site conforms.

This statement describes intent, contact, and known limits. It is not a certificate, and it is not a finding that the site meets WCAG, the ADA, Section 508, or the European Accessibility Act. Automated checks catch a subset of barriers. A person still has to test the keyboard and assistive technology.

Measures we take

  • Run automated WCAG checks on public pages and fix machine-testable failures in source HTML, CSS, and templates.
  • Do not rely on overlay widgets as a substitute for source fixes.
  • Accept feedback and iterate when people report barriers.

Known limitations

Some third-party embeds, PDFs, and older archive pages may not yet meet the target. We document issues as we find them and prioritize high-traffic templates.

Feedback

Email [accessibility contact email] if you find an accessibility barrier. We aim to reply within five working days.

Last reviewed: [date of last review].

<h2>Accessibility statement</h2>
<p>[Organization] wants [website URL] to be usable by as many people as possible. The target we are working toward: WCAG 2.2 Level AA. Naming a target is not a claim that the site conforms.</p>
<p>This statement describes intent, contact, and known limits. It is not a certificate, and it is not a finding that the site meets WCAG, the ADA, Section 508, or the European Accessibility Act. Automated checks catch a subset of barriers. A person still has to test the keyboard and assistive technology.</p>
<h3>Measures we take</h3>
<ul>
  <li>Run automated WCAG checks on public pages and fix machine-testable failures in source HTML, CSS, and templates.</li>
  <li>Do not rely on overlay widgets as a substitute for source fixes.</li>
  <li>Accept feedback and iterate when people report barriers.</li>
</ul>
<h3>Known limitations</h3>
<p>Some third-party embeds, PDFs, and older archive pages may not yet meet the target. We document issues as we find them and prioritize high-traffic templates.</p>
<h3>Feedback</h3>
<p>Email [accessibility contact email] if you find an accessibility barrier. We aim to reply within five working days.</p>
<p>Last reviewed: [date of last review].</p>

What a statement should include

The W3C guide Developing an Accessibility Statement asks for a commitment, the standard you are working toward, and a contact. It also recommends known limits and the measures you take. The same page says a statement is not a technical assessment or a declaration of conformity. Write the limits in plain language, such as “older PDFs have no tags,” rather than a success-criterion number.

  • Who to email when a page blocks someone
  • The standard you are working toward, only if you can say what you have tested
  • Limits you already know: embeds, PDFs, archived pages
  • A last-reviewed date you will actually update

A published statement is not a finding

Pasting this HTML does not show that a page meets WCAG, the ADA, Section 508, or the EAA. A checker loads the URL. This generator does not. Use the website accessibility checker for machine-testable failures, and the WCAG checklist for what a person still has to test. If the worry is a demand letter, the ADA compliance checker is the scan, not this draft. Do not rely on overlay widgets as a substitute for source fixes.

Questions

Check a public URL

Free scan, up to 25 pages and a branded PDF. No account. A Pro account saves the site and schedules the next run.