Free accessibility statement template

The 7 sections every accessibility statement needs

Whether you're writing to EU European Accessibility Act (EAA) expectations, US ADA practice, or both, a credible accessibility statement covers the same ground. Skipping one of these is the single most common reason a statement looks thin to an auditor, a procurement reviewer, or a plaintiff's attorney doing due diligence before sending a demand letter.

1. A conformance statement

Name the standard you're testing against — almost always WCAG 2.2 Level AA today — and state your conformance status honestly: fully conformant, partially conformant, or not conformant. "Partially conformant, with known gaps and an active remediation plan" is a completely normal, defensible status. A vague claim of "we are accessible" with no standard named is not.

2. How and when the statement was prepared

State the date the statement was written, whether it's based on a self-audit or a third-party audit, and when it was last reviewed. Statements without a date look abandoned — reviewers read "no date" as "no ongoing program."

3. Scope

Say exactly what the statement covers: your marketing site, your app, both, or specific subdomains — and call out anything explicitly excluded (a legacy knowledge base, third-party embedded widgets, PDFs not yet remediated). Unscoped statements invite the question "does this cover the page I'm complaining about?"

4. Known limitations

List the specific barriers you know about, ideally tied to the WCAG success criterion each one relates to, with a short note on why it isn't fixed yet and when you expect it to be. This section is the one businesses most often want to leave blank — resist that instinct. An honest, specific limitations list is more credible than a claim of full conformance that a five-minute manual check would disprove.

5. Feedback and contact information

Give a real, monitored channel — at minimum an email address, ideally a phone number too for US-facing statements, where courts have shown a preference for a real-time contact option over email-only. State a target response window, even a loose one ("within 5 business days").

6. Enforcement / escalation procedure

For EU statements, this means naming the national enforcement or market surveillance body a visitor can escalate to if unsatisfied with your response — each EU member state designates its own, so this section is country-specific. US statements don't have a direct equivalent regulator to name, but should still describe an internal escalation path.

7. Technical specifications

A short, standard note on the technologies your accessibility relies on (HTML, WAI-ARIA, CSS, JavaScript) and that experience may vary by browser and assistive-technology combination. This section is boilerplate but expected — its absence is a minor tell that the statement was written in a hurry.

What the full kit adds

The two excerpts above cover roughly a third of a complete, publish-ready statement. The full AccessibleDocs Kit gives you the entire document, twice over — one version written to EU EAA / EN 301 549 conventions, one to US ADA practice — plus the pieces a template alone can't give you:

• Full section 3–5 and 7–8 language (scope, non-accessible content, disproportionate-burden framing, technical specifications) — not just the two sections shown here
• A WCAG 2.2 AA self-audit checklist to fill in your actual "known limitations" section honestly, instead of guessing
• A remediation plan template so your statement's "we're fixing it" claim has a real tracked plan behind it
• An EAA scope-assessment worksheet to confirm which sections even apply to you
• Pro tier: a country-by-country EU enforcement cheat-sheet, so section 6 names the right national authority instead of a placeholder