What goes in a website accessibility statement?
An accessibility statement says how accessible your site is, what does not work yet and why, how people can report a problem, and when you last checked. The EU model statement sets the required parts for public sector sites, and it is a good template for any business that has to publish accessibility information under the European Accessibility Act.
The EU model statement recommends that the claims in an accessibility statement are reviewed for accuracy regularly, and at least once a year.
Who has to publish one
- Public sector bodies in the EU must publish an accessibility statement under Directive (EU) 2016/2102, using the model set by the Commission in Implementing Decision (EU) 2018/1523.
- Businesses in scope of the European Accessibility Act must publish information on how their service meets the accessibility requirements, “in the general terms and conditions, or equivalent document” (Directive (EU) 2019/882, Annex V). The law does not use the word statement, but a statement page is a practical way to publish it.
What the EU model statement requires
Section 1 of the model lists the mandatory content:
- A commitment and a scope: which websites or apps the statement covers.
- A compliance status, one of three: fully compliant, partially compliant, or not compliant, with the standard you measured against. “Fully” is only for when every requirement is met without exceptions.
- Non-accessible content: what does not work, and why. Either it fails the requirements, or a disproportionate burden exemption is being used, or the content is out of scope. Describe it in plain words, and point to accessible alternatives where there are some.
- How the statement was prepared: the date, and the method, either a self-assessment or a third-party assessment.
- Feedback and contact: how people report a problem or ask for content they cannot reach, and who answers.
- Enforcement procedure: where people can go if your answer is not good enough.
Optional content worth adding
- What you are doing about the issues, and by when.
- The date of the last big update to the site.
- A link to the evaluation report, which the model suggests in particular when you claim full compliance.
- Extra help for people with disabilities, such as phone support.
What the European Accessibility Act asks of businesses
Annex V lists what the information should contain, where applicable:
- A general description of the service, in accessible formats.
- The descriptions and explanations needed to understand how the service works.
- How the service meets the accessibility requirements in Annex I.
Where to put it
The model statement asks for a link on the home page or on every page, for example in the footer. A short, standard address such as /accessibility helps. The statement itself has to be in an accessible format, so a plain HTML page is the safe choice.
Mistakes to avoid
- Claiming full compliance with nothing behind it. The model expects the statement to be based on an actual evaluation, and to say which method was used.
- A statement with no date. Without one, nobody can tell if it still describes the site.
- A contact address nobody reads. A report that sits unanswered for three months tells people more than the statement does.
- Writing it once and never touching it again. Review it at least once a year, and after any big redesign. The site will have changed even if the statement has not.
Start from a real review
A statement is only as honest as the review behind it. My 14-day Trial for accessibility, $995, one time, checks the key pages of your site against WCAG 2.2 AA, fixes what can be fixed in the 14 days, and includes a draft statement built on what it found. It is technical work, not legal advice.