KALACALA · Creative Technology

KALACALALet's talk

Service — Web accessibility (EAA)Mandatory since June 2025

Web accessibility you can prove

Audit and remediation of websites, online shops and apps to EN 301 549, the standard behind the European Accessibility Act, enforceable since 28 June 2025. Not a report listing the failures: the site fixed, in design and in code.

Reviewed on

Terms

Timing
Audit in one or two weeks; remediation depending on what it finds.
Price
Fixed before we start, by scope.
Method
Automated and manual review, with a screen reader and a keyboard.
Book the audit

The European Accessibility Act (Directive 2019/882) requires, since 28 June 2025, that e-commerce and other digital services —banking, transport, e-books, electronic communications— be usable by people with disabilities. It applies to any company selling to consumers in the EU, wherever it's based. The technical reference is EN 301 549, which points to WCAG 2.1 level AA.

Most work sold as accessibility is a report: a long list of failures that someone has to fix later. Here accessibility is design and code, so it gets fixed. And documented, because compliance also means being able to show it.

Who it's for

  • Online shops selling to consumers in the EU — including from the UK, the US or anywhere else.
  • Digital services covered by the Act: banking, transport, communications, e-books.
  • Companies bidding for public contracts, where accessibility is written into the tender.
  • Any site that wants to reach everyone: according to the WHO, one in six people lives with a disability.

What's included

Audit

Automated and manual. Tools catch part of the problems; the rest are found by using the site with a screen reader, keyboard only and zoomed in, the way people who need it use it.

Remediation

In design and in code. Contrast, structure, forms, keyboard navigation, alternative text, components. Fixed, not flagged.

Statement

What the law asks you to publish. The information on how the service meets the accessibility requirements, written and published.

Content

So the team doesn't break it. Guidelines and training so what gets published later stays accessible.

Monitoring

Periodic re-checks, because every change to the site can break what was working.

What you get

  • The audit report: each issue, where it is and who it affects.
  • The site remediated, or the remediation plan if your team does it.
  • The accessibility statement, ready to publish.
  • Guidelines for the people who publish content.

What people ask us

Does the European Accessibility Act apply to my company?
If you sell to consumers online in the EU or provide one of the services it lists, yes, since 28 June 2025. Microenterprises providing services are exempt: fewer than ten people and no more than €2 million in turnover or balance sheet.
Does it apply to companies outside the EU?
Yes, if they sell to consumers in the EU: the obligation follows the market, not the headquarters. Each member state enforces it through its own national law.
Will an accessibility overlay or plugin make us compliant?
No. Toolbars and overlays promising automatic accessibility don't fix structure or forms, and often get in the way of screen-reader users. Accessibility lives in the design and the code.
Which technical standard do we need to meet?
EN 301 549, which for websites and apps points to the WCAG 2.1 guidelines at level AA. It's the reference used to check compliance.

How it's bought

Every service follows the same path: a short diagnosis, the build with weekly deliveries and, if you want it, ongoing maintenance.

Let's talk

Tell us what you're building.

We use what you write only to reply to you. How we handle your data

Or write straight to hola@kalacala.com