An accessible digital solution for everyone

An accessible website or online store is easy for everyone to use: people with disabilities, older users and those browsing with different devices or assistive technology. Since 2025 the European Accessibility Act (EAA) has made accessibility mandatory for many online stores and e-services.

We bring digital solutions in line with WCAG, both new projects and websites and online stores that are already live.

Ask for an accessibility audit

Why does accessibility matter?

Accessibility is not just a requirement to tick off. For you, it means three things.

More customers

People with disabilities and older users can use an accessible solution too. Every obstacle in a form or the cart is a lost sale.

Meeting the requirements

The European Accessibility Act has applied since 2025. We help you meet its requirements before they become a problem.

Better user experience and visibility

A clear structure, sufficient contrast and proper headings make the page easier for everyone and help search engines understand the content better.

How do we ensure accessibility?

  1. Audit

    We check the solution against the WCAG 2.1 AA criteria: automated tests and manual checks with a keyboard and a screen reader.

  2. Report and priorities

    You get a list of the issues found, with their impact and how hard they are to fix, so we can start with what matters most.

  3. Fixes

    We fix the code, design and content: contrast, focus order, form labels, alternative text and heading structure.

  4. Retesting

    We check the fixes again to make sure they work with real assistive technology.

  5. Maintenance

    We add accessibility checks to the development process, so new changes don't bring the issues back.

What do you get from the audit?

An audit is not just a verdict. You get the materials the fixes can start from straight away.

Audit report
The issues found, each with its WCAG criterion, location and a recommended fix.
Priority plan
What needs fixing first and what can wait.
Fix guidelines
Clear guidelines that our developers or your own can follow to make the fixes.
Accessibility statement
A publishable description of how accessible the solution is and how to report problems.

Where to start?

It depends on whether the solution already exists or is still to come. Building accessibility in from the start is always cheaper than fixing it later.

FeatureAuditAudit and fixesNew solution
Right for you ifyou want to know where you standan existing solution has to meet the requirementsyou are starting a new website, store or app
Resulta report and a priority plana compliant solution and a retestaccessibility in the design and code from day one
What we doautomated and manual checksaudit, fixes, retestchecks in the prototype, design and development
Costlowestdepends on the issues foundlowest in the long run

Making an existing website or online store accessible

Most existing solutions don't need rebuilding from scratch to become accessible. We start with an audit and first fix the places that block users the most, such as the cart, the checkout and forms.

We can also make the fixes in a solution built by another team.

Accessibility in a new project from the start

In a new project we consider accessibility as early as the prototype: we check contrast, focus order and form logic before we write a single line of code.

That way there are no costly fixes later, and the finished solution meets the requirements on launch day.

Prototyping

Frequently asked questions

  • Does the European Accessibility Act apply to our company?

    The act mainly covers online stores and digital services such as banking, transport and e-books. For services, microenterprises with fewer than 10 employees and an annual turnover of up to 2 million euros are exempt. If you are not sure, we'll help you find out.

  • What is WCAG?

    WCAG (Web Content Accessibility Guidelines) is the international guideline on making web content accessible. The European requirements rest on the EN 301 549 standard, which in turn refers to WCAG 2.1 level AA.

  • Is an automated test enough?

    No. Automated tools find only some of the issues. That is why we also check the solution manually, with a keyboard and a screen reader.

  • How long does an audit take?

    It depends on the number of pages and user journeys. We usually pick the key views, such as the home page, a product page, the cart and the checkout. We give an exact timeline after the first conversation.

  • Will accessibility change our design?

    Usually not noticeably. The changes concern contrast, focus visibility, form labels and structure, which most users simply experience as easier use.

  • What is an accessibility statement?

    A public description of how accessible your solution is, which shortcomings are known and how users can report problems. We help you write it.

Get in touch

Want to know how accessible your website or online store is? Write to us, and we'll look at where to start together.

Aleksei Latõnin

Aleksei Latõnin

Chief Operating Officer