Accessibility guides
Practical fixes for the problems automatic checks find most often. Written for web builders and content editors, in English, Dutch, French and German.
How to write an accessibility statement: steps and example
Draft a clear accessibility statement with the right sections, a practical HTML example, and real findings from your website.
Read the guide- Who needs an accessibility statement?
- Write the statement step by step
- Concise HTML example
- What an automated scan cannot decide
- Frequently asked questions
Building with AI tools
Instructions to paste into Lovable, Bolt, v0, Replit and coding agents, so the site they build works for everyone from the start.
- AI builders
Accessible sites with AI builders and coding agents
Five habits that prevent most accessibility problems in AI-built sites, one set of instructions for any tool, and a simple routine to check and fix the result.
- Lovable
Accessible sites with Lovable
What Lovable generates, the accessibility problems that often come with it, where to put permanent instructions, and how to publish and check the result.
- Bolt
Accessible sites with Bolt
What Bolt generates, the accessibility problems that often come with it, where to put permanent instructions, and how to publish and check the result.
- v0
Accessible sites with v0
What v0 by Vercel generates, the accessibility problems that often come with it, how to save instructions it follows in every chat, and how to publish and check the result.
- Replit
Accessible sites with Replit
What Replit Agent builds, the accessibility problems that often come with it, how to use replit.md for standing instructions, and how to publish and check the result.
- Coding agents
Accessible code with Cursor, Claude Code and other coding agents
Where to put accessibility rules for Cursor, Claude Code, GitHub Copilot, Windsurf and AGENTS.md, a rule block for developers, automated checks in CI, and how to check the deployed preview.
Guides by topic
Every issue in your report links to its guide.
- Usually critical
Describe meaningful images
Give images a short text alternative when they communicate information or perform an action.
- Usually critical
Give every button a clear name
Make the action of every button understandable in text, including buttons that only show an icon.
- Usually serious
Give every page a useful title
Write a unique browser-tab title that identifies the current page before the website name.
- Usually moderate
Keep headings in a logical order
Use headings to create a clear content outline instead of choosing levels for their visual size.
- Usually critical
Label every form field
Place a visible label beside each field and connect it directly to the input.
- Usually serious
Make text easy to read
Improve text and background colours so more people can read your content comfortably.
- Usually serious
Set the language of each page
Tell browsers and assistive technology which language the page uses.
- Usually serious
Write links that explain their destination
Replace vague or empty link labels with wording that tells people where the link will take them.