Service

Accessibility and quality assurance

Meeting WCAG because people use your site with a keyboard and a screen reader — with automated checks and manual testing to back it up.

What you get

  • WCAG 2.2 AA audit with prioritised findings
  • Component-level accessibility fixes
  • Automated axe checks in CI
  • Behat and Playwright regression suites
  • Keyboard and screen-reader test pass
  • Client testing checklist

For public-sector and higher-education clients accessibility is a legal requirement, and treating it as a pre-launch audit is how it becomes an expensive one. Most findings in a late audit trace back to a handful of components, which is where they should have been fixed.

So the checks run continuously: an accessibility addon in Storybook while components are being built, axe in the pipeline, and a manual keyboard and screen-reader pass before launch, because automated tools catch perhaps half of what matters.

Questions we get asked

No, and be careful of anyone who says they can. We can audit against WCAG 2.2 AA, fix what we find, give you the evidence and tell you plainly what is still outstanding. Compliance is a claim you make about your site; our job is to make it a true one.