An Accessibility Statement for Your Website: What to Write
Short answer: An accessibility statement tells visitors which standard your website aims to meet, which parts are hard to use, how to flag a barrier and how quickly you will reply. Write it honestly, because a statement that claims full compliance on a site with known gaps is more damaging than one that admits them. Use the Web Content Accessibility Guidelines as the reference, name the version you aim for, list the known issues with a plan, and give a contact route that someone actually reads. Review the statement on a fixed date, and update it whenever the site changes significantly.
Why a statement is worth publishing
A statement is a public commitment, and it helps visitors who use screen readers, keyboards, magnifiers or voice control. It shows them where to go when something blocks them, and it gives your team a clear standard to measure against. Even a small business benefits, because most accessibility complaints arrive as direct messages that could have been answered with a link to a page.
A veterinary clinic in Calgary, Maple Paws in this example, receives an email from a client who cannot use the online booking form with a keyboard. The clinic's developer fixes the form, but the client had no page to explain where to send the report. A short statement with an email address and a reply promise would have routed the message correctly in the first place.
Step one: name the benchmark you work towards
The Web Content Accessibility Guidelines, published by the W3C, are the common reference. Name the version and the conformance level you are working towards, such as WCAG 2.2 at level AA. Avoid writing that the site "is compliant" unless you have tested every page against the criteria. A safer wording is "we aim to meet" or "we have tested the following pages".
Be specific about scope. Say which pages and features you have tested, such as the home page, the booking form and the online shop. If some parts of the site, such as old PDF files, are not yet covered, say so.
Step two: describe known gaps honestly
Visitors trust a statement that admits problems. List the known gaps in plain language. For example, "Some product photos do not have descriptive text yet. We are adding it to every product page by the end of next quarter." A specific gap with a date is much more useful than a general phrase about continuous improvement.
Organise gaps by how much they affect a visitor. A form that cannot be submitted by keyboard matters more than a decorative image without a description. Put the high-impact gaps first and give each one a status.
Step three: explain how to report a problem
Give at least one contact route, such as an email address and a phone number. If the team uses a form, make sure the form itself is accessible. Ask the person who reports a problem for the page address, the device or browser, and a short description of the problem. Let them know you will ask follow-up questions only if needed.
Say what you will do when a report comes in. For example: "We reply within three working days to confirm receipt and tell you what we plan to do." A promise you can keep is better than a fast promise you miss.
Step four: give fix times you can keep
Set a fix time for each category of problem. A reasonable structure might have a short target for faults that block a booking or a purchase, a longer target for content problems, and a note that some issues depend on third-party tools. Make sure the team has the capacity to meet those times before you publish them.
A sample structure you can adapt
Here is a short structure with sample sentences. Replace the bracketed text with your own details.
- Commitment. "We want everyone to be able to use this website. We aim to meet WCAG 2.2 at level AA."
- Scope. "We have tested [list of pages or features] using [testing methods]. Other pages may have gaps."
- Known issues. "[Issue], affecting [who], will be fixed by [date]."
- Feedback. "If you cannot use any part of this site, email [address] or call [number]. Tell us the page and what you were trying to do."
- Response. "We reply within [number] working days and aim to fix reported barriers within [number] weeks."
- Review. "This statement was last reviewed on [date] and will be reviewed at least once a year."
Avoid overclaiming
Accessibility testing is partly automated and partly manual. Automated checks catch many issues, such as missing alternative text or low colour contrast, but they cannot judge whether a form makes sense to a screen reader user. A statement that relies only on an automated scan is overclaiming. Mention the methods you used, such as keyboard testing and testing with a screen reader, and be clear about what you have not checked.
Avoid promises about legal compliance in a specific jurisdiction unless you have taken advice. Describe your standard and your process, and let readers draw their own conclusions about the law.
Keep the statement alive
Put the statement in the site footer and link to it from the contact page. Record the date of the last review at the top, and set a reminder to revisit it. Each time you launch a new section, such as an online shop or a booking tool, check whether the statement still describes the site accurately.
FAQ
Do I need an accessibility statement?
Many jurisdictions expect businesses to make their sites accessible, and a statement is a common way to show your approach. Check the rules that apply to your sector and location, because they can differ.
Can I use an accessibility overlay tool instead?
Overlays do not replace fixing the underlying code, and they cannot make every page accessible on their own. Describe any tool you use honestly, and do not present it as the whole solution.
Who should write the statement?
Someone who understands the site and can answer feedback, usually with input from a developer. A statement written only by marketing often overclaims.
Publishing a statement is a good moment to test the pages it describes, and the enquiry form is open for that check.