Accessibility statement
Accessibility Statement: What Goes In It and How to Write One
An accessibility statement shows how accessible your website is and what you are improving. You will read who needs a statement, what belongs in it and how to write one in five steps and keep it up to date.
What is an accessibility statement?
An accessibility statement is a public page on which an organisation describes how accessible its website or app is. You state which standard you assess against, which problems remain and when you will fix them. Visitors also read how to report a problem.
For visitors with a disability, the statement shows that you take them seriously. For your organisation, it is a clear overview of where you stand and what your next step is.
Who needs an accessibility statement?
Government organisations
The Dutch Digital Accessibility Decree for government (Besluit digitale toegankelijkheid overheid) requires public bodies to publish a statement for every website and app, following a fixed model. The statement is added to the accessibility register of DigiToegankelijk.
Businesses under the European Accessibility Act
Web shops and other consumer services that fall under the EAA provide information on how their service meets the accessibility requirements, for example in their terms and conditions or on a separate page. Many businesses use a page in the form of an accessibility statement for this.
Organisations that choose to publish one
Even without an obligation, a statement shows customers, clients and partners that you take accessibility seriously. That is a strong signal in tenders and for clients who ask about accessibility.
Read what the European Accessibility Act requires of your website
What goes in an accessibility statement?
Dutch government organisations use the fixed model of DigiToegankelijk. For other organisations, that model is a good guide, so your statement is complete and recognisable.
| Part | What you describe |
|---|---|
| Website or app | Which website or app the statement covers, with the web addresses. |
| Standard and status | Which standard you assess against, for example WCAG 2.2 level AA, and to what extent your website meets it. |
| Research | When and how you researched the accessibility, with a link to the research report. |
| Known problems | For each problem: what is going on, which success criterion it affects, when it will be fixed and which alternative you offer until then. |
| Contact and complaints | How visitors report a problem and where they can turn with a complaint. |
| Date and signature | The date of the statement and the name and role of the person responsible within your organisation. |
Read DigiToegankelijk's explanation of the accessibility statement (in Dutch)
The statuses A to E
Statements in the Dutch accessibility register get a status from A to E. You only get status A or B with a full study of your website or app. Such a study is valid for three years, and you update the statement every year with your progress.
Status C is valid for six months and does not yet require a study. If a statement stays at C for longer or the study expires, the status automatically changes to D. Status E means there is no statement yet. With status A, B or C, a government organisation complies with the law.
How to write an accessibility statement
Five steps from the first study to a statement you keep up to date every year.
Decide what you research
Choose the website or app and the pages and processes visitors use most, such as the home page, search, a form and the ordering process.
Research the accessibility
Combine automated tests and AI content analysis with manual research. A full study by an accessibility expert, following a fixed method, supports your statement.
Tip: An automated scan is a good starting point: you immediately see which problems recur on many pages.
Make an improvement plan
Order the problems you found by impact and give each problem a date by which it is fixed. Also name an alternative while a part does not work yet, such as help by phone or email.
Write and publish the statement
Fill in the statement, have the person responsible sign it and publish it on a fixed page, with a link in the footer of your website. Dutch government organisations use the form assistant on toegankelijkheidsverklaring.nl.
Keep the statement up to date
Update the statement when you fix problems or your website changes. Government organisations with status A or B do so at least once a year.
Tip: With weekly scans you see every week which problems have been fixed. That way you have the progress for your next update at hand.
Automatic tests and AI content analysis
AccessRadar combines automatic tests with AI content analysis. You see not only technical errors, but also which texts truly help your visitors.
The AI analysis reads the text of your pages and gives suggestions, for example for:
- Alternative text: does the text say something meaningful, or is it 'image', a file name or 'click here'?
- Link text: do the link text and the text around it make clear where a link leads?
- Headings and labels: do they describe the topic or the field, or are they empty words such as 'Info' or 'Field 1'?
- Page titles and forms: is it clear what a page is about and what a field expects?
You get concrete suggestions for better texts, which you pick up directly in your weekly improvement plan. This way your website moves closer to WCAG 2.2 AA suitability every week and reaches more customers.
Read how tests and AI analysis work together in the improvement plan
Read also
Practical explanations of WCAG and digital accessibility.
European Accessibility Act: What Does It Mean for Your Website or Web Shop?
What does the European Accessibility Act mean for your website or web shop? Read who falls under it, since when it applies and what to do now.
Testing Website Accessibility: a Step-by-Step Approach
How to test your website's accessibility: step by step with an automatic scan, keyboard test, screen reader and the most common problems.
The Dutch Accessibility Law for Web Shops: What Do You Need to Arrange?
Does your web shop fall under the Dutch accessibility law? Read which requirements apply since 28 June 2025, which parts matter and how to improve step by step.
Check your website for WCAG for free
Request the free WCAG check from AccessRadar and receive the results of an automatic scan by email, as a starting point for your improvements.
Want to keep going every week afterwards? The WCAG improvement plan adds weekly scans and AI content analysis.
A WCAG scan supports your assessment. An automated WCAG scan cannot establish full WCAG 2.2 AA compliance. Combine regular WCAG scans with manual evaluation and feedback from people with disabilities.
Frequently Asked Questions About the Accessibility Statement
Is an accessibility statement mandatory?
For Dutch government organisations it is, for every website and app. Businesses under the European Accessibility Act provide information about the accessibility of their service, and a statement is a clear way to do so. For other organisations a statement is voluntary and a strong signal to customers.
Where do I place the accessibility statement?
On a fixed page of your website, with a link in the footer, so visitors find it from every page. Dutch government organisations also publish it in the accessibility register and show the accessibility label on their website.
How often do I update the statement?
As soon as you fix problems or your website changes significantly. For government organisations with status A or B: update it at least once a year, and the underlying study is valid for three years.
Can I publish a statement if my website does not fully comply yet?
Yes. That is exactly when you show which problems exist, when you will fix them and which alternative you offer. An honest statement with a concrete plan builds trust.
Can I use an automated scan as evidence?
An automated scan with AI content analysis gives you a strong basis and shows where to improve. For status A or B in the register, a full study is required, which also includes manual testing.