Accessibility Statement Generator

Written by Rembrand Le Compte on 11 June 2026 (Average reading time: 2 minutes)

An accessibility audit has been completed, and the next question is: “What exactly needs to be included in the accessibility statement?” For specialists who run checks every day, that may feel routine, but drafting a statement is something many people still struggle with.

Our solution

In practice, we notice that a statement from another website or an older project is often copied. At Eleven Ways we also have our own starting point, which we use as a basis for a dialogue with the client.

To make our lives easier, we’ve now turned that knowledge and expertise into our own fill-in assistant. We’re happy to share a preview with the accessibility community.

What makes our tool better?

Here’s a small selection of features:

Live preview: view your statement with real-time updates
Trilingual: generates the text in Dutch, French, and English
Legally compliant: includes all mandatory sections for public-sector bodies and is also perfect for private companies that must comply with the European Accessibility Act
HTML and Markdown export: copy or import and edit the text in your own CMS
Local saving: save your work to a local file for long-term storage
Autosave: your progress is also stored in a browser session
Relevant information and context: clear guidance for sections and fields, e.g. what “partially compliant” really means
Predefined options and examples: so you don’t have to start from scratch
Dark mode: a calmer, more readable interface

Test the generator

We’re currently in a beta phase. The foundation is there, but we still have plenty of plans to expand (for example, making the interface itself multilingual as well). We’d love your input: what refinements or changes would you suggest? All feedback is welcome!

Try our statement generator here

Latest articles

Multi-level navigation: the challenge of identifying parent sections for screen readers

Many guides show you how to build an accessible navigation menu, but they overlook the "you are here" complexity. How do we translate an "active parent" visual highlight into something a screen reader user actually understands?
Tooltips that work for everyone

Here at Eleven Ways, we often get asked for “the correct, accessible tooltip pattern”. Building accessible tooltips is a minefield — especially when you mix in rich content and screen reader quirks. Let’s examine the issues and go in search of a tooltip pattern that truly covers all our bases.