OUR APPROACH

Find. Understand.
Fix. Prevent.

A finding becomes useful when it leads to an informed decision, a verified improvement, and a stronger way of working.

These four stages connect evaluation with delivery. The starting point and depth depend on your product, existing evidence and the support agreed with your team.

Our approach: find and record barriers; understand their impact on users; correct and verify improvements; prevent recurrence through reusable patterns, team guidance and repeat checks.

BEFORE THE REVIEW

Agree what the work needs to establish.

Start with the product and the tasks people need to complete. Define the scope and expected outputs before selecting methods or interpreting results.

A focused component check and a broader accessibility audit answer different questions. The review should state which question it addresses.

Establish the working context

  • Products, journeys and important states to review.
  • Relevant standards, versions and target levels.
  • Devices, browsers and assistive technologies in scope.
  • Access, dependencies, responsibilities and deliverables.

THE FOUR STAGES

What happens at each stage.

The stages can overlap and repeat. A change may reveal another barrier, and an established team may already have evidence that lets us begin further along the workflow.

FIND

Identify barriers in context.

Review the agreed journeys and states using appropriate automated, manual, keyboard and assistive-technology checks. Examine errors, confirmations and interactions as well as the initial screen.

What you take forward

Reproducible findings with locations, evidence, testing conditions and relevant requirements. Coverage notes make the review’s boundaries explicit.

UNDERSTAND

Connect findings to decisions.

Explain how the barrier affects the task. Examine patterns across shared components, clarify the expected behaviour, and discuss priorities with the team responsible for the work.

What you take forward

A reasoned view of impact, affected journeys and dependencies, with questions or uncertainties identified before changes are planned.

FIX

Support the change. Check the outcome.

Provide remediation guidance or agreed implementation support. When a change is ready, repeat the original test and check the surrounding task for unintended effects.

What you take forward

Documented retest outcomes: what is resolved, what remains, and any new issue found. Retesting a finding does not by itself establish whole-product conformance.

PREVENT

Make improvements repeatable.

Turn recurring findings into component guidance, acceptance criteria, authoring practices or role-focused learning. Decide where checks belong in the team’s existing workflow.

What you take forward

Agreed practices and responsibilities that help future work retain the improvement, supported by proportionate review as content and technology change.

CHOOSE AN ENTRY POINT

Use the evidence you already have.

An existing audit can provide a starting point for understanding findings and supporting fixes. A new feature can bring prevention into requirements and design before implementation begins.

We agree whether existing findings need confirmation and which additional checks are necessary. You do not need to purchase every service or follow a fixed sequence.

How this connects to our services

Our five services support different parts of this approach—from identifying barriers to guiding fixes and building your team’s skills.

Choose the support that fits your current needs. We can combine services where useful.

Find the service that matches your work

PLAN THE WORK TOGETHER

Start with your product and the evidence available.

Tell us what has been reviewed, what your team is changing, and where support would be useful.