Accessibility & WCAG compliance

So we do both. Automated scanning finds the mechanical problems quickly: missing alternative text, contrast failures, absent form labels, invalid ARIA. Then a person works through the site with a keyboard and a screen reader, which is where the problems that actually block people tend to appear.

The obligation is no longer theoretical in most markets. The European Accessibility Act has applied since June 2025 to a wide range of consumer-facing digital services sold in the EU. In the United States, ADA-based litigation over inaccessible websites continues at volume. Public-sector bodies in the UK and EU have had statutory requirements for years.

We test against WCAG 2.2 Level AA, which is the standard those regimes point at. Version 2.2 added criteria that matter on modern interfaces — visible focus that is not obscured by sticky headers, targets large enough to hit reliably, and not forcing people to re-enter information they have already given you.

Screen reader testing is done on the combinations people actually use: NVDA and JAWS on Windows, VoiceOver on macOS and iOS, and TalkBack on Android. A page that works in one does not automatically work in the others.

You receive an audit that names each issue, the specific success criterion it fails, where it occurs and how severe it is — followed by the remediation itself. We fix the markup rather than handing you a list and wishing you luck.

We will not sell you an overlay widget. The accessibility community is close to unanimous that overlays do not achieve compliance, and in several documented cases their presence has featured in litigation rather than preventing it.

Building something new? Accessibility costs very little when it is designed in and a great deal when it is retrofitted. We build to AA as standard on every service line.