Blog

Finland’s accessibility law tightens: how to keep your web service accessible in 2025

We carry out thorough accessibility analyses of our clients’ web services, testing with automated tools, a keyboard and a screen reader, among other methods. These analyses matter more than ever now that, from 28 June 2025, the Finnish Act on the Provision of Digital Services covers more and more consumer-facing web services. In this article we explain what our accessibility analysis includes, who it suits and how it leads to a concrete report and an accessibility statement.

Author: Arto Hautanen, Senior Developer, CarePublished Updated 3 min read

Every web service should review and improve its accessibility, even where the changes in the law don’t apply.

What does the change to the Act on the Provision of Digital Services mean?

In short: Finnish national legislation based on the EU’s European Accessibility Act applies from 28 June 2025, through the Act on the Provision of Digital Services (306/2019). Its requirements cover consumer-facing web services, among others, with microenterprises exempt. These consumer-facing web services are:

  • online shops
  • e-books
  • some passenger transport and banking services
  • services providing access to audiovisual content, and communication services.

Making sure a web service is accessible is ongoing work, just like search engine optimisation or keeping the site’s content up to date.

The easiest way to look after your site’s accessibility is to have it analysed regularly and to carry out the actions the analysis identifies.

“Accessibility benefits all of us. Research shows it improves everyone’s user experience and makes sites easier to find in search engines. Most importantly, it improves digital accessibility for the people who need it in their daily lives.”

Emilia Pulkkinen, Digital Designer, Into-Digital

Accessibility analysis

So accessibility is a live issue again. Product owners of online shops in particular should add an accessibility analysis to their to-do list.

What does our accessibility analysis include?

Our analysis covers the following steps:

Automated visual testing

Automated accessibility tools check for things such as:

missing alternative text for images

contrast problems

an illogical heading hierarchy

unclear link text

form field labels.

The aim of this step is to find the most common accessibility gaps quickly and comprehensively.

Keyboard test

Some people use a web service with the keyboard only, without a mouse.

The test covers things such as:

navigating with the keyboard

using the various forms and features

whether keyboard focus moves logically and works.

Screen reader testing

Users with visual impairments in particular use websites read aloud.

In the analysis, we use screen reader software to test things such as:

the order in which content and headings are read

whether buttons and forms are understandable

whether ARIA roles and HTML semantics work.

Colour blindness test

In this step we test how the site works without colour. Does the information come across without colour, and are the contrasts sufficient?

HTML code validation

We check the site’s technical structure with HTML validation tools. This identifies issues such as:

incorrect or incomplete structure

conflicting attributes

incompatible or outdated markup.

The site without images

A site’s images may not load, for example because of technical problems or a poor connection. This step tests:

Is the content understandable without images?

Are the alt texts informative?

Does the text alone convey the content?

Report and actions

The report gives an overall picture of your web service’s current accessibility and a list of findings and issues to fix. We also provide effort estimates and descriptions of solutions for fixing the issues found and for creating an accessibility statement.

Keep in mind that accessibility is ongoing work. Individual findings almost always come up later, during use or testing. That’s why it’s best to approach accessibility with a long-term view.

Accessibility statement

An accessibility statement describes how well a website meets the accessibility requirements. We draft the statement together with the client and agree on a clear structure for it. We build the accessibility statement as a page in the web service that the client can update and maintain.

The statement includes, among other things:

  • Accessibility status: whether the requirements are met fully, partly or not at all. Based on a self-assessment and an external audit.
  • Inaccessible content: a list of the gaps, the reasons for them and the plans to fix them.
  • Alternative ways to use the service: other ways to access the service if accessibility falls short.
  • Feedback and contact details: feedback channels and instructions for requesting accessible content.
  • Enforcement procedure: what to do if feedback doesn’t lead to a result. The supervising authority is the Regional State Administrative Agency for Southern Finland.
  • Date of preparation and assessment method: the date and who carried out the assessment (internal or external).

“Accessibility isn’t just visual clarity. The technical build decides whether users can reach the content with assistive technology, such as a screen reader. Without thorough testing of the code base, accessibility easily ends up being only skin deep.”

Leevi Hyvärinen, Head Developer, Into-Digital

What does the analysis cost?

The price of an accessibility analysis depends on the size of your service:

  • Limited: EUR 800 excl. VAT (VAT 25.5%)
  • Extensive: EUR 1,600 excl. VAT (VAT 25.5%)

Our Care (Huolenpito) helps make your web service accessible. Tell us what you need.

Read more

All articles
  • Blog

    I built a website for five grand, but it would cost you 30 grand

    We are one of Finland's leading WordPress agencies. Yet our new website does not contain a single line of WordPress. Most of the site was built by me, the CEO, and I can't code. In this article I explain what that proves and what it doesn't.

    19 Nov 2026 · 8 min read

  • Blog

    WordPress security vulnerabilities: what is actually going on?

    July and August 2026 were a historically heavy stretch for the WordPress ecosystem. Within a couple of months we saw a critical vulnerability in WordPress core itself, more than a hundred plugin security fixes, an unpatched login bypass in a popular SSO plugin and a case where malicious code reached thousands of sites straight through the official plugin directory. The National Cyber Security Centre Finland at Traficom also issued its own warning. In this article we explain in plain language what happened, why and when.

    17 Aug 2026 · 13 min read

  • Blog

    The EU AI Act gets real: what does Article 50 mean in practice?

    The EU AI Act has been talked about for a long time. Now it finally means something. And it means something for all of us who build or use AI-based digital services. On 2 August 2026, the Act's transparency obligations in Article 50 started to apply. In practice, they affect every organisation that uses AI in its website, online service or content.

    9 Jun 2026 · 3 min read

Get a price estimate or tell us what you need

The estimate takes a few minutes and does not ask for your contact details. You can also describe your need. We will get back to you by the next working day at the latest.

Get a priceTell us what you need