Generate Your WCAG Accessibility Statement in Minutes

An accessibility statement is a public page that says, in plain terms, how well a website works for people with disabilities and what the organization is doing about the parts that do not. It names the standard the site is measured against (WCAG, the Web Content Accessibility Guidelines, at Level A, AA, or AAA), states the current conformance level, lists known limitations, explains how and when the site was assessed, and gives a contact for reporting barriers.

It is not a certificate and it is not a badge. A statement that promises full conformance while the site fails basic checks is a public claim that anyone with a free scanner can test. The useful version is honest: this is where we are, here is what we know is broken, here is how to reach us.

Who publishes one

Organizations receiving federal funding, holding certain government contracts, or subject to Section 508, ADA Title II, or WCAG-referencing state laws frequently find a statement is required or expected. Some funders ask grantees to document their digital accessibility practices. Many nonprofits with no formal obligation publish one anyway, because it tells visitors with disabilities that barriers will be taken seriously and gives them a way to report one. Whether a particular rule applies to your organization is a question for counsel, not for a generator.

What a good one contains

• Scope. Which site, or sites, the statement covers.
• Conformance status. The WCAG version and level, and whether the site fully conforms, partially conforms, or does not conform.
• Known limitations. Specific issues, the criteria they break, and how many occurrences of each.
• Assessment approach. Automated scan, manual review, or both, and the date of the most recent one.
• Feedback and escalation. An email or form, an expected response time, and where to go if that response is unsatisfactory.

Why statements go stale

The site changes; the statement does not. A new plugin, a redesigned donate page, or a batch of uploaded PDFs can move the conformance level within a week. A statement written by hand stays accurate until the next deploy. A statement generated from scan data can be checked against the next scan and flagged when the two diverge.