Accessibility statement
xsibility's accessibility statement: our WCAG 2.2 AA conformance target, how we test this website, known limitations, and how to report a barrier.
Do it yourself: websites
An accessibility statement tells visitors how accessible your website is, what you’re doing about it, and how to get help. DOJ settlement agreements require one, the European Accessibility Act requires service providers to publish equivalent information, and it gives people with disabilities a direct line to you instead of a lawyer.
Copy, adapt, and make every bracketed item true before you publish.
Accessibility statement for [Organization]
[Organization] is committed to making [website/app name] usable by
everyone, including people with disabilities.
Standard
We aim to conform to the Web Content Accessibility Guidelines (WCAG)
2.2 Level AA.
Status
[website] is [partially] conformant with WCAG 2.2 Level AA.
[Partially conformant means some parts of the content do not fully
conform.]
Known limitations
- [Older PDF documents published before (date). Contact us for an
accessible version, which we will provide within (X) business days.]
- [Third-party booking widget — we are working with the vendor and
you can book by phone at (number).]
Feedback and help
If you have trouble using any part of this site, contact us:
- Email: [address]
- Phone: [number]
We aim to respond within [2] business days.
How we assess accessibility
[Independent audit by (company) in (month year); ongoing internal
testing with automated tools, keyboard and screen readers.]
This statement was prepared on [date] and last reviewed on [date].
See our own accessibility statement for an example.
The statement is only as good as what happens when someone uses it. Make sure messages reach a person who can act, track response times, and treat every report as a free bug report.
Send us a few URLs or sample PDFs. Within two business days you get a free, plain-English snapshot of your biggest accessibility risks and what it takes to fix them.