Skip to content

Digital Accessibility

How to Publish a WCAG Accessibility Statement

If you run a website or app in the EU, UK, or Canada, an accessibility statement isn't optional — it's the law. Even where it isn't legally required, publishing one is the single cheapest way to reduce your ADA litigation risk and signal to users that you take inclusion seriously.

An accessibility statement is a public declaration of your conformance level, what you've done to meet it, and how users can contact you if they encounter barriers. This guide covers what to include, which jurisdictions require one, and how to keep it from going stale (which is where most organisations fall down).

WCAG: Web Content Accessibility Guidelines

If you run a website, app, or digital service, you're probably already required to comply with WCAG — even though it isn't a law itself. The Web Content Accessibility Guidelines (WCAG) are the global standard for digital accessibility, and they've been incorporated into legal frameworks across the EU, UK, US, Canada, and Australia. You don't have a choice about whether to follow them; you only have a choice about whether you comply proactively or reactively after a complaint.

Developed by the W3C's Web Accessibility Initiative, WCAG covers visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities. It's the closest thing to a universal accessibility rulebook the world has.