The page exists because somebody said the organization should have one. It says the association is committed to accessibility, that the site aims to conform to WCAG, and that anyone experiencing difficulty should get in touch. It has not been edited since it was published. Nobody can tell you who wrote it.
Read it the way a stranger would. That page is doing less than nothing. A statement with no date, no standard version, no method and no known issues tells a reader that the organization has not tested anything, and it tells a plaintiff's attorney the same. A commitment is not evidence, and an accessibility statement is supposed to be evidence.
Where this comes from. This post covers what belongs in the statement, what to leave out, and how to write one you can still defend in eighteen months.
What the Statement Is Actually For
Three different audiences read this page, and the reason most statements fail is that they are written for none of them.
A member with a disability reads it first. They want to know whether they can complete the task they came for, and if not, how to get help from a human. They are not interested in your commitment. They want the contact route and they want it to work.
A procurement reviewer reads it second. If your association responds to RFPs from public entities, federal grantees or larger member organizations, somebody is checking whether you can substantiate what you claim. A statement that cites findings gets you through. A statement that cites a commitment invites a follow-up question you may not want.
Counsel reads it third, usually after a demand letter. Under a notice-and-cure regime, and increasingly in ordinary practice, evidence that you assessed your site and acted on what you found is the difference between a conversation and a settlement. The statement is where that evidence lives in public.
The Six Things That Belong
A statement that would survive any of those three readers is short. It is six items, and none of them takes long to produce once the work behind them is done:
- The standard you are conforming to. Named with a version and a level. Write WCAG 2.1 Level AA, not accessible, not compliant, not fully accessible. The last one is a claim almost nobody can support and it is the sentence most often quoted back at organizations.
- When it was assessed, and by whom. The date of your most recent evaluation and who performed it. A statement without a date is a statement about a website that no longer exists. If it was an internal review, say so. Internal review honestly described beats an external audit implied.
- How it was assessed. Automated scan, manual review, keyboard testing, screen reader testing, and which pages. Say the site was tested and a reader assumes everything. Say the join, renew, register and resource library templates were tested and you have described reality.
- What you know is not conforming yet. This is the item organizations resist and the one that does the most work. A statement listing no known issues reads as a site nobody tested, and it reads that way to exactly the people you least want reading it that way. List what you know is wrong, with a remediation date beside it.
- How to report a barrier. A named route to a person who will answer, with a response commitment you can actually meet. Not a generic contact form that lands in an unmonitored inbox.
- What is out of scope, and why. Third-party embeds, archived documents, content from a vendor platform you do not control. These are legitimate limits when stated openly and a problem when discovered by somebody else.
What to Leave Out
Three things appear in most statements and make them worse.
Absolute claims. Fully accessible, fully compliant, and meets all requirements are claims that cannot be maintained on a site that publishes new content weekly. Accessibility is a moving target and an absolute claim ages badly between the day it is written and the day it is read.
Overlay language. Some vendors supply a statement template alongside a widget. That template describes the vendor's product rather than your site, and pointing at a tool as evidence of conformance invites the obvious question of what the tool actually fixed. If you use one, describe what it does and does not do.
A wall of commitment language. A statement that opens with three paragraphs about the organization's values before reaching anything checkable is telling the reader that the checkable part is thin. Lead with the standard and the date.
A Statement Is Not a VPAT
These get conflated in procurement conversations, and they answer different questions.
The distinction in practice. An accessibility statement is a public page describing your site, when it was assessed and what is known to be wrong with it. A VPAT, and the accessibility conformance report produced from one, is a structured evaluation of a product against specific criteria, normally supplied by a vendor to a buyer. Associations meet VPATs when purchasing an AMS or an LMS, and occasionally get asked for one when selling access to a member platform.
Which matters when somebody asks for the wrong one. If a procurement office asks for a VPAT and you send a statement, you have not answered them. If they ask how your site handles accessibility and you send your CMS vendor's VPAT, you have also not answered them, because the vendor's conformance says nothing about what your team built on top of it.
The Version You Can Write This Week
Most organizations do not have a recent audit, and waiting for one is why the statement never gets updated. There is an honest interim version.
An honest small assessment beats an implied large one. Run an automated scan on your main templates, test the join and renew flows with a keyboard, and write down what you find. That is a real evaluation, it takes an afternoon, and it lets you write a dated statement with a named method and a short list of known issues. It is not a substitute for a proper audit and the statement should say which one it is.
Why this works. A statement that says we ran an automated scan and keyboard-tested our membership flows in October, found these four issues, and are fixing two of them by January is stronger than any amount of commitment language. It shows a process. A process is what the three readers above are all actually looking for.
Keeping It True
The statement goes stale the moment the site changes, which is continuously, so it needs an owner and a review interval like anything else.
Twice a year is enough for most associations, tied to something already in the calendar so it does not depend on anyone remembering. Re-run the assessment, update the date, close the issues you fixed, add the ones you found. The document should get shorter over time. If it is getting longer, that is information too.
Send Us the One You Have
Send us your current accessibility statement and the accessibility language from your last RFP response. What comes back is a marked-up version: which claims are supportable as written, which are not, which of the six items above are missing, and a draft replacement paragraph for each gap. We will also tell you which of your claims we would expect a procurement reviewer to question. If your statement already carries a date, a method and a known-issues list, it will be a short letter and you are ahead of most of the sector.