Guide · 202627 pages9 chaptersFree PDF
Accessible Websites with WCAG
How to make your website accessible to everyone, meet legal requirements, and avoid common pitfalls from the start.
- Legal Requirements Two laws, same level: WCAG 2.1 AA
- Contrast Twelve color pairs tested against AA
- Procurement Requirement formulations to use
About the guide
Since June 28, 2025, digital accessibility is a legal requirement for many private companies, not just for public authorities. Both the DOS law and the accessibility law are practically based on WCAG 2.1 level AA, and the responsibility always lies with the service provider, even when an agency has built the website.
The guide explains what WCAG is, who is covered, and what levels A, AA, and AAA mean. It then goes through the five areas where deficiencies most often occur: language, color contrasts, navigation, code, and media, with checklists you can tick off directly.
Finally, it discusses accessibility as a business issue and procurement: ready-made requirement formulations to use and how to follow up to ensure the website maintains the level even after launch.
For you who
- orders, owns, or is responsible for a website
- needs to know if the accessibility law applies to you
- is procuring a website and wants to set accessibility requirements
From the guide
- June 28, 2025
- when the accessibility law came into effect, including for e-commerce and banking services
- WCAG 2.1 AA
- the level that both the DOS law and the accessibility law practically require
- 4.5:1
- minimum contrast for normal text at level AA
- 78 criteria
- distributed across 13 guidelines and four core principles in WCAG 2.1
Contents
- Chapter 01
WCAG and Legal Requirements
What WCAG is, who is covered, and the difference between the DOS law and the accessibility law. Plus the three levels, the exception for micro-enterprises, and what WCAG 2.2 adds.
- Chapter 02
Accessible Design in Practice
The five building blocks that determine if the website works for everyone, with concrete examples of actions within each area.
- Chapter 03
Language
Plain language, heading hierarchy, alt texts, descriptive links, and language indication in the code. A checklist to tick off.
- Chapter 04
Color Contrasts
Contrast requirements for text and interface, and twelve common color pairs tested against AA and AAA. Half do not meet the requirement for normal text.
- Chapter 05
Navigation
Keyboard control, visible focus, meaningful link texts, and the link that jumps directly to the content.
- Chapter 06
Code
Semantic HTML, correct heading order, ARIA with care, custom-built components, and accessible forms, with code examples.
- Chapter 07
Media
Subtitles, audio description, transcripts, accessible players, and rules for automatic playback and flashing content.
- Chapter 08
WCAG as a Business Issue
Five ways accessibility strengthens the business, from a larger market and higher conversion to visibility in search and AI. And how responsibility is divided between the client, editorial team, and agency.
- Chapter 09
Requirement Setting in Procurement
Ready-made requirement formulations for level, testing, reporting, and accessibility statement, and how to follow up with tools, keyboard, and screen readers.
Frequently asked questions
Does the accessibility law apply to our company?
Since June 28, 2025, the law applies to products and services to consumers, including e-commerce, banking services, telecom, media services, and passenger transport. Micro-enterprises providing services, with fewer than ten employees and a turnover of up to 2 million euros, are generally exempt. The guide is not legal advice, so consult legal expertise for your specific case.
What WCAG level does the law require?
Both the DOS law and the accessibility law are based on the standard EN 301 549, which practically means WCAG 2.1 level AA. WCAG 2.2 AA is a reasonable ambition for those who want to be secure in the long term.
Who is responsible if an agency has built the website?
The service provider. Responsibility cannot be contracted away to the agency, but the work is practically shared between the client, content managers, and web agency.
Is a single accessibility tool or overlay sufficient?
No. The requirements apply to the actual code and content of the website. Automated tests only capture some of the deficiencies, so complement with manual tests using a keyboard and screen readers.
Download
Get the guide in your inbox
Accessible Websites with WCAG