Two laws that are easy to mix up
The public-sector web accessibility law, lov nr. 692 af 8. juni 2018, covers public authorities and bodies governed by public law, not private companies. Digitaliseringsstyrelsen puts it plainly: “Private aktører er ikke omfattet af webtilgængelighedsloven” (private parties are not covered).
Private companies fall under the Accessibility Act, lov nr. 801 af 7. juni 2022 (tilgængelighedsloven), for services provided from 28 June 2025. It covers only certain services to consumers; for most small businesses that means e-commerce. Selling only to other businesses is outside it , and micro-enterprises are exempt for services. Whether it applies to you: Am I covered?
Who has to do what
Public bodies
Lov 692/2018. An accessibility statement made in Digitaliseringsstyrelsen’s WAS-Tool. The agency supervises and can issue orders.
Private services to consumers
Lov 801/2022. An explanation of how the service meets the requirements, in your terms of sale. Webshops: Sikkerhedsstyrelsen (part of Erhvervsstyrelsen since January 2026) supervises on behalf of Konkurrence- og Forbrugerstyrelsen.
Business-to-business only
Not covered by the Accessibility Act. Accessibility still helps, but that law does not require it.
Does a private company need an accessibility statement?
People search for “tilgængelighedserklæring”, but the law for private companies never uses the word. It belongs to the public-sector law. Before providing the service, a covered private company must prepare the information in annex 4 (bilag 4) and explain how the service meets the requirements, in its terms and conditions or an equivalent document. It must be published in writing and orally, also in a form accessible to persons with disabilities, and stay up as long as the service is offered.
WAS-Tool is for the public sector only. Private companies may write their own statement, but it must not be mistakable for one made in WAS-Tool. So do not copy the public format, such as a page at the address /was that public bodies are advised to use.
Webshops must also pass on the accessibility information manufacturers give about their products, and make login, security and payment usable by everyone, even when an outside provider supplies them. The information must be there before the customer buys. The seller is responsible, even if an agency or a platform built the shop.
WCAG 2.1 AA: the practical yardstick
The Act does not mention WCAG. It says that following harmonised standards published in the EU’s Official Journal gives a presumption of conformity. No such standard is confirmed for e-commerce yet. The public-sector standard, EN 301 549, bases its chapters on web, documents and software mainly on WCAG 2.1. So WCAG 2.1 level AA is the practical yardstick: not written into the law, but the shared language of developers and testing tools.
How far does an automated test get?
In 2017 the UK government’s Government Digital Service ran automated tools against a page with 142 known barriers. The best found about 40 percent, WAVE 30 percent and axe 29 percent. Treat it as an order of magnitude. A machine sees that an image has no alt text. It cannot see whether the alt text makes sense.
What our check reports
Check the accessibility of your front page
The check runs the Lynbro Accessibility Checker rules on your front page’s HTML as the server sends it. It lists up to twelve kinds of problem, most serious first, with the number of places and the WCAG criterion. Errors show as Fix, warnings as Check, and items a person must judge as Unclear. The rules include:
- page title, language, and whether zoom is blocked on phones
- heading order, a main region and a skip link
- images without alt text, and links or buttons with no text
- vague link text such as “read more”
- form fields without a label, and personal-data fields without autocomplete
It also looks for a link to accessibility information.
What it cannot see: contrast from stylesheets (only colours written straight into the HTML), whether focus is visible, the size of buttons, keyboard traps, and pages other than the front page. A clean report is a start, not proof.
Four tests you can do yourself
- Keyboard. Put the mouse away and Tab through the page. Can you see where you are, and reach the menu, the form and the basket?
- Zoom 200 %. Zoom the browser to 200 percent. Is everything readable, with no overlapping text?
- Screen reader. Listen to the front page with VoiceOver (Mac, iPhone) or NVDA (Windows). Do images, links and buttons make sense?
- Contrast. Run a contrast tool on light grey text, text over images and buttons.
Web accessibility questions
Do we need an accessibility statement on our website?
Only public bodies do, and WAS-Tool is theirs alone. A covered private company instead describes how its service meets the requirements, in its terms of sale or an equivalent document.
Is WCAG 2.2 required now?
A new version of EN 301 549 with WCAG 2.2 was reportedly published in September 2026, but it is not confirmed as cited under the law. WCAG 2.1 AA remains the safe yardstick.
We only sell to other businesses. Does this apply to us?
No. The Act sets no requirements for services between businesses.
Fixed price, no commitment
Get it fixed
Tell us which website it is and what the check showed. A person answers with a fixed price before any work starts.
- A fixed price before we start
- An answer by e-mail, no calls
- Your details are used only to answer you