← Solutions
ApplicationTrending

Accessibility audit and remediation

Audit your website or app against WCAG 2.2 AA, fix what fails and keep it fixed — now a legal requirement for many services sold into the EU.

Typical timing
4–10 weeks
Engagement
Fixed scope
Delivery framework
User researchDiscoveryAlphaBetaLive
Discuss this solutionApplication capability →

Objective

Make digital services usable by everyone and demonstrably compliant. The European Accessibility Act has applied since June 2025 to many consumer-facing digital services sold in the EU, and public sector bodies in the UK must already meet WCAG. This package finds the barriers, fixes them and puts checks in the pipeline so they do not return.

You may need this if

  • You sell digital services to consumers in the EU
  • You have no accessibility statement, or it is out of date
  • A complaint, a procurement questionnaire or a failed audit
How it runs

Activities, step by step

The plan follows our delivery framework. Steps that do not apply to this kind of work are left out rather than padded.

  1. 01 · User research1–2 weeks

    Testing with disabled users

    • Sessions with screen reader, magnification and keyboard-only users
    • Top tasks tested end to end
    • Assistive-technology coverage agreed
  2. 02 · Discovery1–2 weeks

    WCAG 2.2 AA audit

    • Automated scanning across all templates
    • Manual expert audit of representative pages and journeys
    • Issues prioritised by user impact and legal exposure
  3. 03 · Alpha2–6 weeks

    Remediation

    • Fixes to components, templates and content
    • Design system updated so fixes propagate
    • Retest with assistive technology
  4. 05 · LiveOngoing

    Keep it compliant

    • Automated accessibility checks in CI/CD
    • Accessibility statement published and maintained
    • Content editor training

Deliverables

What you keep at the end.

  • WCAG 2.2 AA audit report with prioritised issues
  • Remediated components and templates
  • Accessibility statement
  • Automated regression checks in the pipeline
  • Editor and developer guidance

Outcomes

What it is built to change.

  • Services usable by disabled customers
  • Reduced legal and procurement risk
  • Accessibility that holds as the product changes

Often combined with

Every engagement starts with a 45-minute working session with the SME who would own the work. No deck.

Discuss this solution