How to Write an Accessibility Statement That's Actually Useful

An accessibility statement is a public declaration of your commitment to accessibility. Under the European Accessibility Act and the Web Accessibility Directive, publishing one is a legal requirement for many organizations. But beyond compliance, a good accessibility statement builds trust with users who depend on accessibility features.

What to include

• Conformance status — Are you fully conformant, partially conformant, or non-conformant with WCAG 2.1 AA?
• Scope — What parts of your site/app does the statement cover?
• Known limitations — Be honest about what doesn't work yet and why
• Remediation timeline — When known issues will be fixed
• Feedback mechanism — How users can report accessibility barriers
• Enforcement link — Link to the relevant national enforcement body
• Date — When the statement was last reviewed/updated
• Assessment method — How you evaluated accessibility (self-assessment, external audit, automated testing)

Common mistakes

Claiming full conformance when you're not. This is worse than not having a statement at all. Users will test your claims, and regulators will verify them. Be honest about your current status. Generic, copy-pasted statements. "We are committed to accessibility" means nothing without specifics. Users want to know: What's accessible? What isn't? When will it be fixed? No feedback mechanism. If a user encounters a barrier and can't report it, the statement has failed its purpose. Include an email address, form, or phone number. Never updating it. A statement from 2022 is a red flag in 2026. Review quarterly at minimum.

Template structure

Section 1: Commitment and scope "[Company name] is committed to ensuring digital accessibility for people with disabilities. This statement applies to [website/app URL]."

Section 2: Conformance status "This website is [fully/partially/not] conformant with WCAG 2.1 Level AA. [Partially conformant means most content conforms, but some exceptions exist as noted below.]"

Section 3: Known limitations "The following content is not fully accessible: [specific list of known issues with expected remediation dates]."

Section 4: Feedback "If you encounter an accessibility barrier on this site, please contact us: [email/form/phone]. We aim to respond within [timeframe]."

Section 5: Enforcement "If you are not satisfied with our response, you can contact [national enforcement body] at [link]."

Putting it all together

Your accessibility statement should live on your website at a consistent, findable URL — typically /accessibility — and be linked from your footer on every page. It should also be referenced in your trust center if you have one.

ShieldPage's accessibility module will generate and maintain your accessibility statement alongside your other compliance documentation, ensuring it stays current as your accessibility posture evolves.