Table of Contents
- Is an Accessibility Statement Required?
- What to Include in an Accessibility Statement
- Where to Post Your Accessibility Statement
- What to Leave Out
- Sample Accessibility Statement
- Fill-in-the-Blank Accessibility Statement Template
- Keep Your Statement Current
- Frequently Asked Questions
- Need Help With Your Accessibility Statement?
An accessibility statement is a short, public page that tells visitors how accessible your website is, what you’re doing to improve it, and how to get help when something doesn’t work. For many public entities it’s also a legal requirement.
The good news: a strong statement is usually one page. Below, we cover what to include, where to post it, what to leave out, and a sample statement and fill-in-the-blank template you can adapt today.
Is an Accessibility Statement Required?
It depends on who you are and where you operate.
- Colorado state agencies and local governments: yes. Under Colorado HB21-1110 and the OIT Technology Accessibility Rules, every public entity, including special districts, must post a technology accessibility statement in a conspicuous place on its website. The 2025 rule amendments made it even more central: posting a statement is one of the ways a government entity shows it is complying while it improves accessibility over time.
- State and local governments nationwide: strongly recommended. The DOJ’s ADA Title II rule requires WCAG 2.1 Level AA but doesn’t name a statement outright. In 2026 the DOJ pushed compliance to April 24, 2027 for entities serving 50,000 people or more, and April 26, 2028 for smaller entities and special district governments. A statement with a clear way to request help is still one of the first things a reviewer looks for.
- Private businesses and nonprofits: not legally required, but it’s a best practice. It shows good faith and gives frustrated visitors a path to you instead of a lawyer.
What to Include in an Accessibility Statement
Every accessibility statement should cover these seven things. In Colorado, the first four are the core of what the OIT rules expect.
- Your commitment. One or two sentences saying you’re committed to making your website usable by everyone, including people with disabilities.
- At least two ways to report a problem. Give an email address and a phone number at minimum. A form alone isn’t enough, because the form itself may be the barrier.
- A response time. Commit to a timeframe, such as acknowledging reports within two business days. Then meet it.
- The steps you’re taking. Name the real work: audits, staff training, accessible procurement, remediation. Be specific, not aspirational.
- The standard you’re aiming for. Name it: WCAG 2.1 Level AA, which is what both Colorado and the DOJ rule use, or WCAG 2.2 AA if that’s your target.
- Known limitations. List areas you know aren’t fully accessible yet, like older PDFs or a third-party payment portal, and how people can get that content another way.
- The date it was last reviewed. An outdated date tells visitors, and reviewers, that nobody is watching.
If you also have a digital accessibility policy, link to it. The policy is your internal commitment; the statement is the public-facing version.
Where to Post Your Accessibility Statement
Put a link labeled “Accessibility” or “Accessibility Statement” in your site footer so it appears on every page. That’s the simplest way to meet Colorado’s “conspicuous place” requirement. You can see how we do it on our own accessibility statement.
Make sure the statement page itself is accessible: real headings, descriptive links, and plain language. If someone can’t read your statement, it isn’t doing its job.
What to Leave Out
- “Fully compliant” or “100% accessible” claims. No site with ongoing content stays perfect, and an overstated claim invites scrutiny.
- Overlay widget promises. Saying a toolbar makes your site compliant can backfire. Accessibility overlay widgets are not the solution.
- Legal jargon. Write it for a resident trying to pay a bill, not for an attorney.
- Dead ends. An unmonitored inbox or a contact form that only works with a mouse defeats the purpose.
Sample Accessibility Statement
Here’s a complete example for a fictional special district. Notice how short it is.
Accessibility Statement
Sample Valley Water District is committed to making our website accessible to everyone, including people with disabilities. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.
What we’re doing
- Testing our website with automated tools and manual keyboard and screen reader checks
- Training staff who publish content on creating accessible pages and documents
- Requiring accessibility information from vendors before we buy new technology
- Fixing issues found in our most recent accessibility audit, starting with the most serious
Known limitations
Some board meeting PDFs posted before 2024 may not be fully accessible. Our online bill payment portal is provided by a third party and has known keyboard issues. If you need any of this content in another format, contact us and we’ll provide it.
Report a problem or request help
If you have trouble using any part of our website, please let us know:
- Email: [email protected]
- Phone: 555-555-0100 (Monday to Friday, 8 a.m. to 5 p.m.)
We will respond within two business days.
This statement was last reviewed on January 5, 2025.
Fill-in-the-Blank Accessibility Statement Template
Copy this template and replace everything in brackets. Delete any bullet that isn’t true for your organization yet. A shorter, honest statement is better than a longer, aspirational one.
Accessibility Statement
[Organization name] is committed to making our website accessible to everyone, including people with disabilities. We aim to meet the Web Content Accessibility Guidelines (WCAG) [2.1 or 2.2] Level AA.
What we’re doing
- [How you test, such as automated scans and manual testing]
- [Staff training, such as accessible content training for website editors]
- [Purchasing, such as requiring accessibility information from vendors]
- [Current remediation work, such as fixing issues from a recent audit]
Known limitations
[Content you know isn’t fully accessible yet, such as older PDFs or a third-party tool.] If you need any of this content in another format, contact us and we’ll provide it.
Report a problem or request help
If you have trouble using any part of our website, please let us know:
- Email: [monitored email address]
- Phone: [phone number and hours]
- [Optional: mailing address, accessible online form, or TTY/relay number]
We will respond within [number] business days.
This statement was last reviewed on [date].
Tips for filling it in:
- Use an email address that more than one person monitors, like accessibility@, not one staff member’s inbox.
- Pick a response time you can actually meet. Two to five business days is common.
- Not sure what your known limitations are? That’s a sign it’s time for an audit. Our phased approach to testing your website for accessibility is a good place to start.
Keep Your Statement Current
An accessibility statement isn’t a one-and-done page. Review it at least once a year, and update it whenever something changes: you finish an audit, fix a known limitation, switch vendors, or change who handles reports. If you’re working through audit results, see how to prioritize accessibility issues after an audit.
Frequently Asked Questions
Does an accessibility statement make my website compliant?
No. A statement shows your commitment and gives people a way to get help, but your site still needs to meet WCAG. In Colorado, a statement is required alongside your progress toward accessibility, not instead of it.
Can I use an online accessibility statement generator?
Yes, as a starting point. The W3C accessibility statement generator is free and solid. Just make sure the result includes at least two contact methods and reflects what your organization is actually doing.
Should I list every known accessibility issue?
No. List the significant gaps a visitor is likely to run into, like inaccessible PDFs or a third-party portal, and tell them how to get that content another way.
Accessibility requirements and enforcement can vary by jurisdiction. This article reflects general WCAG best practices and is not a substitute for legal or regulatory guidance.
Need Help With Your Accessibility Statement?
We’ll help you write a statement that’s honest, complete, and backed by real progress, from the audit that identifies your known limitations to the remediation that removes them. Learn more about our accessibility services → or see our WCAG-compliant websites for special districts, municipalities, and state agencies →
