What changed after the audit.

An online retailer with 400 product pages

Shopify · Starter audit and remediation support · Completed September 2026

The problem

The retailer's product pages shared a small set of templates. Keyboard users could not reliably operate variant selectors, and checkout validation did not clearly associate messages with the fields that needed attention. The team needed to prioritise changes before its next seasonal campaign.

What we did

We agreed a Starter audit of 10 representative pages covering product selection, the basket and checkout in one language. Manual testing and automated checks recorded 28 distinct issues. We grouped recurring template findings so developers could see where one shared change would address several occurrences.

The team received the report, captioned walkthrough and debrief. We then provided eight hours of separately commissioned remediation support, reviewing pull requests for keyboard operation, labels and error feedback. The developers implemented and released the changes. The included focused retest was requested within 30 calendar days of the debrief.

The outcome

At retest, 24 of the 28 recorded issues were resolved within six weeks of kickoff; four lower-priority content issues remained in the retailer's backlog.

This result covers the agreed sample and issues. We did not individually test all 400 product pages or measure a change in sales.

A regional bank's customer portal

Custom web application · Full audit and remediation support · Completed October 2026

The problem

Customers using a keyboard or screen reader encountered unclear field labels and unexpected focus changes in a multi-step portal. The bank's development team needed evidence it could reproduce in a controlled environment.

What we did

We scoped a full audit of 14 screens across three journeys: signing in, updating contact details and requesting a statement. Work took place in a staging environment with synthetic customer records and agreed test accounts.

We documented 31 distinct findings, including 9 classified as critical or high priority. Following the debrief, we provided 12 hours of separately commissioned pairing and pull-request review. The developers corrected shared field components, error summaries and focus handling. The engagement included four additional retest hours, charged at the agreed hourly rate, beyond the audit's two-hour allowance.

The outcome

At retest, all 9 critical or high-priority findings in the agreed scope were resolved within eight weeks of kickoff; 6 of the remaining 22 findings stayed open with assigned owners.

The retest recorded technical issue status. It did not certify the portal or establish the bank's legal compliance.

Bring us a journey that needs attention.

Whether it is a checkout, account area or enquiry form, we can help you define a useful scope and a practical next step.