REDESIGN AND LAUNCH
How to test a business website before acceptance
Website testing should follow customer tasks and the agreed scope. A screenshot can confirm appearance, but it cannot establish whether links, forms and downloads work.
Build a short test plan
List the supported browsers and devices agreed for the project. Choose representative journeys: find a service, open a download and contact the business. Include every agreed feature, even if it appears on only one page. Ask who performs each check and what evidence is retained.
Check content first
Read names, prices, contact details and service boundaries against approved records. Verify the correct versions of downloadable files. Check titles and headings describe the actual pages. Remove visible draft content and clearly label any illustrative design concept.
Exercise the interface
Open menus and expandable sections using a keyboard and touch where appropriate. Check visible focus, readable text and mobile layout. W3C recommends evaluating accessibility throughout a project; these initial checks can identify issues but are not a full conformance assessment.
Test the functions
Verify enquiry delivery using authorised test data. Check error messages and the alternative contact route. Use provider test modes for payments or bookings rather than creating unintended real transactions. Confirm external links reach the correct business and service.
Log defects precisely
Record page, device, steps, expected result and observed result. Example: “Contact on phone: entering invalid email gives no explanation; show a clear correction message.” Assign severity according to the customer task affected, not according to how striking the screenshot looks.
Retest after corrections and mark the outcome. Critical defects that block an agreed task should remain visible in the acceptance decision. Keep minor agreed follow-up items in a separate list with an owner. The final report should say which features and environments were checked, so “tested” does not imply coverage you never performed.
Sources and further detail
Technical references checked on 8 October 2026. Provider features can change.
Practical guidance with illustrative examples. Read our editorial standards or send a correction.