Accessible website
For public bodies, federally linked companies, providers with EU customers and anyone who wants a website for everyone.
Updated: 2026-11
We audit existing websites against WCAG with automated and manual tests, fix the reused components, support content and PDFs and write the accessibility statement. New websites are built to WCAG 2.2 level AA from the start, compatible with eCH-0059 and the requirements of the European Accessibility Act.
Many websites exclude people without anyone noticing: forms unusable with a screen reader, contrast that becomes unreadable in poor light, menus that only work with a mouse, PDFs without structure.
For authorities that breaches the law, for providers with EU customers it has too since June 2025, and for everyone else it is lost reach. Retrofits often fail because pages are fixed one by one instead of at the building blocks.
What you get
WCAG audit
Automated and manual review of key pages and flows with prioritised findings.
Component fixes
Navigation, forms, dialogs and colour system fixed where they originate.
Content and PDFs
Guidance and support for text alternatives, link texts, structure and accessible documents.
Accessibility statement
Status, known limitations and contact option, as required.
Review routine
A short check for new content and features.
How it runs
- 01
Audit
Review, findings, priorities.
- 02
Implement
Components first, then pages and content.
- 03
Re-test
Test fixes with assistive technologies.
- 04
Statement and handover
Documentation and review routine for the team.
Price framing
Effort depends on the technical base, number of templates and volume of documents. Audit and implementation can be commissioned separately; you receive a fixed proposal after the audit.
Indicative, not a binding quote — the frame is confirmed during scoping.
What drives the price? → Cost guide
Parent service: Website Development
FAQ
Is an overlay tool enough?
No. Scripts that promise accessibility after the fact do not fix the causes in the code and can even interfere with assistive technologies.
Which standard do you implement?
WCAG 2.2 level AA. That covers WCAG 2.1 AA under eCH-0059 and matches the practical yardstick of EN 301 549.
Must our website be accessible?
It is mandatory for public bodies and for providers offering certain services to consumers in the EU. For others it is voluntary but beneficial.
Does accessibility help visibility?
Often yes. Clean structure and text alternatives also help search engines and AI systems understand content.
Accessible website
For public bodies, federally linked companies, providers with EU customers and anyone who wants a website for everyone.