By Genesis AI Services · April 21, 2026 · 7 min read · Policy
Accessibility Statement Template
Why you need one: An accessibility statement demonstrates good faith compliance effort, provides a feedback mechanism for users to report barriers, and is required by the EU Web Accessibility Directive and expected under the ADA Title II final rule.
An accessibility statement is a page on your website that explains your commitment to accessibility, your current conformance status, and how users can report issues. It's not just good practice — it's increasingly legally expected.
What to Include
Conformance status — which WCAG version and level you conform to (or aim for)
Scope — which parts of your site or app are covered
Known limitations — what doesn't yet meet the standard, with timeline for remediation
Contact information — email/phone for users to report accessibility barriers
Response commitment — how quickly you'll respond to accessibility feedback
Last audit date — when the site was last tested
Enforcement/escalation — where users can escalate if you don't respond (for EU: national authority)
Sample Template
Accessibility Statement for [Your Organization Name]
[Your Organization Name] is committed to ensuring that [yourwebsite.com] is accessible to people with disabilities. We continually improve the user experience for everyone and apply relevant accessibility standards.
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. We believe our site [fully conforms / partially conforms / does not yet fully conform] to these standards.
Known Limitations
Despite our efforts, some content may not yet meet WCAG 2.1 AA standards. Known issues include:
[Example: Some older PDF documents may not be fully tagged. We are working to remediate these by [date].]
[Example: Some third-party embedded content may not be fully accessible. We are working with our vendors to address this.]
Technical Specifications
Accessibility of [yourwebsite.com] relies on the following technologies: HTML, CSS, JavaScript, and WAI-ARIA. These technologies are relied upon for conformance.
Assessment Approach
We assessed accessibility by:
Self-evaluation using automated tools including Accessalyze and axe DevTools
Manual testing with keyboard navigation
Testing with NVDA screen reader on Windows
[Optional: Third-party audit by [firm], [date]]
Feedback and Contact
We welcome feedback on the accessibility of [yourwebsite.com]. If you encounter an accessibility barrier or have any difficulty using this site, please contact us:
Email: [accessibility@yourorganization.com]
Phone: [phone number]
We try to respond to accessibility feedback within [2 business days].
Formal Complaints (EU)
[For EU entities:] If you are not satisfied with our response to your accessibility feedback, you may contact the relevant national supervisory authority: [authority name and link].
This statement was last reviewed on [date].
Conformance Status Language
The W3C recommends using one of these standardized conformance phrases:
Fully conforms — all WCAG 2.1 AA success criteria are met
Partially conforms — some success criteria are not met (name the exceptions)
Does not conform — more failures than conformances
Don't claim "fully conforms" unless you have tested thoroughly. Courts and regulators can fact-check claims. "Partially conforms" with a specific list of known issues and remediation timelines is more honest and defensible.
Where to Place Your Accessibility Statement
Link in the site footer (required by EU Web Accessibility Directive)
URL: /accessibility (standard and expected)
Also link from the Contact or About page
Keeping It Current
Review and update your accessibility statement:
After significant website redesigns or updates
After formal accessibility audits
At least annually for EU Web Accessibility Directive compliance
When known limitations are remediated
Audit Before You Publish Your Statement
Know your actual conformance status before claiming it publicly. Accessalyze gives you an instant WCAG 2.1 AA baseline report.
