Accessibility compliance
We help you achieve WCAG and European Accessibility Act (EAA) compliance
Since 28 June 2025, accessibility requirements for many covered products and services in the EU are enforceable under the European Accessibility Act (Directive (EU) 2019/882), which extends accessibility obligations beyond the public sector into private-sector products and services: e-commerce, consumer banking, e-books, electronic communications, transport ticketing and more.
For websites, web apps and mobile apps, the harmonised European standard EN 301 549 currently builds heavily on the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA (and is being updated towards WCAG 2.2) — though the EAA's functional requirements go beyond a single conformance level. The obligations can also affect non-EU providers offering in-scope products or services into the EU market.
- WCAG 2.1 AA
- WCAG 2.2
- EN 301 549
- EAA — Directive (EU) 2019/882
What the law actually asks for:
-
Level AA is the usual reference point
WCAG defines three conformance levels — A, AA and AAA. For web and software, EN 301 549 currently builds heavily on WCAG 2.1 AA, while Level A alone is generally insufficient and AAA is typically not expected as a general product-wide target.
-
Two regimes, not one
The Web Accessibility Directive (Directive (EU) 2016/2102) covers public-sector bodies' websites and apps; the EAA adds accessibility obligations for many private-sector digital products and services. The two overlap, but they aren't identical.
-
Conformance has to be evidenced
A detailed public accessibility statement is a classic Web Accessibility Directive duty for the public sector; for EAA-covered services, accessible public-facing information and documentation on how the service meets the requirements are part of demonstrating conformance.
We're a software house, not an overlay vendor. We don't bolt a widget onto your site and call it accessible — we test against the standard, fix the underlying code and design, and build accessibility into the products we deliver so compliance holds up under scrutiny.
From audit to a defensible compliance position:
-
Conformance audit
Automated and manual testing against WCAG 2.1/2.2 AA and EN 301 549 — including keyboard-only navigation and screen-reader testing — with every issue mapped to a success criterion and rated by severity and effort.
-
Remediation in the codebase
We fix the real causes: semantic markup, keyboard and focus handling, colour contrast, form labelling, captions and transcripts — changes in your front-end, not a third-party overlay.
-
Accessible by default in new builds
For products we design and engineer, accessibility is part of the build from day one, rather than something retrofitted later.
-
Compliance documentation
We help you put the evidence in place — the accessibility statement or service information your case calls for, plus conformance documentation mapped to EN 301 549 — so you can show where you stand.
-
Ongoing monitoring
Automated and manual regression checks on each release, so new features don't quietly reintroduce barriers you've already paid to remove.