Accessibility audit and remediation

Accessibility audit and remediation is testing a web application against WCAG 2.2 level AA, with automated checks and manual testing by keyboard, screen reader, zoom and contrast, then fixing the issues in your code and adding the tests that keep them fixed. It is for products sold to consumers in the EU that may fall under the European Accessibility Act, B2B software asked for an accessibility conformance report during procurement, and teams that fixed issues once and watched them come back.

This site runs axe checks against WCAG 2.2 AA and best-practice rules on every template in CI.

The audit covers the journeys that matter most, sign-up, search, checkout, the core task of your product, rather than a sample of random pages, because an issue that stops someone completing a task matters more than ten cosmetic ones. The audit is fixed-price; the fixes are quoted after it, in stages, blockers first.

Automated tools catch part of the problem: missing labels, contrast failures, invalid ARIA, missing alternative text. Manual testing catches the rest: whether every control works by keyboard alone with a visible focus, whether a screen reader announces things in a sensible order, whether content survives zoom and narrow screens, whether errors are explained, and whether motion can be reduced. I test with NVDA on Windows and VoiceOver on macOS and iOS.

Each finding is mapped to the WCAG 2.2 success criterion it fails and ranked by impact on users. Fixes go into your codebase, reviewed with your team, and the guard rails go into CI: axe checks on each template and keyboard tests on the key journeys, so regressions fail the build. The report also gives input for a conformance report (VPAT) and a draft accessibility statement.

The European standard for ICT accessibility, EN 301 549, reflects WCAG 2.1 in version 3.2.1 and is aligned with WCAG 2.2 in version 4.1.1, published in September 2026; an audit at WCAG 2.2 AA covers both.

It is not a certificate without fixes, and it is not an overlay widget. Overlays don't change the underlying code, can get in the way of assistive technology, and don't make a site conform. It is also not legal advice about whether the Act applies to you.