Test a website before launch using complete customer journeys

Choose representative journeys

For an illustrative service website, test discovering a service, reading a blog article, switching language, and requesting a quotation. Include at least one long page, a page with images, and a form. Check navigation from a direct link rather than always starting at the homepage. Record the expected result for each step so another reviewer can repeat the same journey without guessing.

Check behaviour as well as appearance

Use real test information, clearly marked as a test, and confirm receipt through the intended delivery route. Inspect contact links and form error messages. Review keyboard use, visible focus, page titles, and headings as preliminary accessibility checks. W3C’s Easy Checks resource is useful for a first review, while explicitly describing the limits of such a review; it does not establish complete accessibility on its own.

Make the release decision visible

Classify findings by whether they block a customer task, misstate information, or affect presentation. Assign an owner and retest the exact failed action after a correction. Document any accepted limitation and its follow-up date. Avoid replacing a failed test with an optimistic note that it probably works on the live server; if the environment differs, plan the corresponding live verification.

• Read contact details and service descriptions in both languages.
• Confirm submitted requests reach the expected recipient.
• Review important pages on phone and desktop.
• Record who approved launch and what remains to check.