Free Tool

Accessibility Statement Generator

Generate a WCAG 2.1 / ADA / EN 301 549 aligned accessibility statement for your website. Required by law in the UK, EU, and US public sector — and good practice everywhere else.

Compliance + Inclusion

Why Publish an Accessibility Statement

UK Public Sector Required

The Public Sector Bodies Accessibility Regulations 2018 require UK public-sector websites to publish a conforming statement.

EU Web Accessibility Directive

EU public bodies and entities providing public services must comply with EN 301 549 and publish a statement.

European Accessibility Act

From June 2025, private companies selling products and services in the EU must meet accessibility standards.

ADA Lawsuits in the US

4,000+ ADA web-accessibility lawsuits filed annually. A statement demonstrates good-faith effort and reduces litigation risk.

Reach More Customers

1 in 5 people have a disability. Inaccessible sites lose 20% of potential customers — and the disposable income that comes with them.

SEO Benefits

Accessibility best practices (alt text, semantic HTML, clear headings) overlap heavily with SEO. Better access = better rankings.

FAQ

Frequently Asked Questions

What is WCAG?

WCAG (Web Content Accessibility Guidelines) is the international standard for web accessibility, published by the W3C. WCAG 2.1 is the current standard most laws reference. WCAG 2.2 was published in 2023 and adds 9 new criteria — both are widely accepted.

What is the difference between Level A, AA, and AAA?

Level A is the minimum (basic accessibility), AA is the legally required level for most regulations (the "real" standard), AAA is the highest level (rarely required, sometimes impossible without compromising design).

How do I know if my site is accessible?

Run an audit with axe DevTools, WAVE, or Lighthouse for automated checks (catches ~30% of issues). Then test manually with a screen reader (NVDA, VoiceOver), keyboard-only navigation, and high-contrast modes. Our Color Contrast Checker is a good starting point.

Is "partial conformance" acceptable?

Yes — being honest about known issues is more credible than overclaiming. List specific issues, why they exist (legacy content, third-party tools), and your timeline for fixing them.

Where should I publish the statement?

Most regulations require a link from every page (usually footer) to a dedicated /accessibility/ page. Don't bury it in a sub-page of legal stuff — visibility matters legally.