Accessibility Statement Generator

Generate a professionally structured, WCAG-compliant accessibility statement for your website in under 5 minutes. Follows the official W3C model required by EU law and global best practices.

Free, no login required. Download as plain text or HTML and publish directly to your site.

Accessibility Statement Generator

Answer a few questions to generate a WCAG-compliant accessibility statement for your website.

1
2
3
4
5
Step 1 of 5

Organization & Website

Legal Requirements by Region

Accessibility statement requirements vary by jurisdiction. Here is an overview of the key requirements:

MANDATORY

European Union (EN 301 549 / Web Accessibility Directive)

Public sector bodies must publish an accessibility statement and review it annually. The statement must follow the W3C model and include a feedback mechanism.

MANDATORY

United Kingdom (Public Sector Bodies Accessibility Regulations)

UK public sector organizations must publish an accessibility statement and respond to accessibility requests within 20 working days.

RECOMMENDED

United States (Section 508)

Federal agencies must provide an accessibility conformance report (ACR/VPAT). An accessibility statement is strongly recommended for all government and many private sector sites.

RECOMMENDED

Canada (AODA / ACA)

Ontario's AODA and the federal Accessible Canada Act require accessibility plans and progress reports. An accessibility statement supports compliance documentation.

RECOMMENDED

Private Sector (all regions)

While not always legally mandatory, publishing an accessibility statement demonstrates good faith and significantly reduces legal risk in ADA/AODA/EAA lawsuits and complaints.

What Every Accessibility Statement Must Include

Based on the W3C Accessibility Statement Generator model and EU Web Accessibility Directive requirements, a complete statement must include:

  • 1
    The scope of the statement (which website or product it covers)
  • 2
    Conformance status (fully conformant, partially conformant, or non-conformant)
  • 3
    Which WCAG version and level you target (e.g., WCAG 2.2 Level AA)
  • 4
    Known accessibility limitations and available workarounds
  • 5
    Contact information for reporting accessibility barriers
  • 6
    A feedback mechanism and expected response time
  • 7
    Date of the last accessibility assessment
  • 8
    How users can request accessible alternatives for inaccessible content

Frequently Asked Questions

Know Your Conformance Status Before You Publish

An honest accessibility statement requires knowing your actual conformance level. Run a full WCAG audit to identify real issues before writing your statement.