Acceptance Testing a Delivered Website: A Sign-Off Checklist for Owners
Short answer: Acceptance testing is your structured check that the delivered website does what the contract and the agreed scope said it would, before you sign off and pay the final invoice. Work through a written test script by area: content, navigation, forms and integrations, devices and browsers, speed, accessibility basics, legal pages, SEO settings, and account ownership. Record each item as pass or fail with a note and a screenshot. Report failures in one shared list using a consistent format, separate genuine defects from new requests, and agree in writing which handover items you must receive before payment.
What acceptance testing is for
User acceptance testing, or UAT, is not the developer's own quality check. It is you, the client, confirming the result against what you agreed. Its value comes from being systematic: an owner clicking around for ten minutes finds the obvious things, while a script finds the ones that cost money later, such as a quote form that only fails on iPhones.
Set aside real time for it. For a small business site of 15 to 30 pages, plan for half a day of testing plus time to retest fixes.
Before you start
- Get the scope document, proposal or statement of work, and note every page and feature promised.
- Ask the developer for the test environment link, or confirm testing will happen on the live domain before announcement.
- Prepare a shared spreadsheet with columns: ID, area, test, expected result, actual result, pass/fail, severity, screenshot link, status.
- Decide who tests: ideally you plus one colleague who did not work on the project.
The test script by area
1. Content
- [ ] Every page in the sitemap exists and has final copy, not placeholder text.
- [ ] Prices, opening hours, phone numbers and addresses are correct.
- [ ] Team names, photos and job titles are current.
- [ ] No spelling mistakes in headings and buttons.
- [ ] Images are the agreed ones, properly cropped, not blurry.
2. Navigation and links
- [ ] Main menu, footer and mobile menu reach every intended page.
- [ ] No internal links lead to 404 pages.
- [ ] External links open the right destination.
- [ ] Logo returns to the home page.
3. Forms and integrations
- [ ] Each form submits successfully with valid data.
- [ ] Required fields show clear error messages when left empty.
- [ ] Notification emails arrive at the agreed addresses, not the developer's.
- [ ] Customer autoresponders arrive and read correctly.
- [ ] Data reaches the CRM, booking tool or mailing list as agreed.
- [ ] Spam protection works without blocking real users.
- [ ] Payments, if any, complete in test mode and the receipts look right.
4. Devices and browsers
Test the key pages and one full form submission on:
- [ ] iPhone in Safari
- [ ] An Android phone in Chrome
- [ ] A desktop in Chrome and in one other browser (Edge, Firefox or Safari)
- [ ] A tablet, if your customers use them
Look for overlapping text, buttons that are hard to tap, and horizontal scrolling on phones.
5. Speed
- [ ] Home page and a key service page load reasonably on a mobile connection.
- [ ] PageSpeed Insights shows no glaring issues such as huge uncompressed images.
- [ ] Videos do not autoplay large files on mobile.
6. Accessibility basics
You do not need to be an expert to catch common issues. The W3C's easy checks guide walks through quick tests.
- [ ] Every image that carries meaning has alt text.
- [ ] You can tab through the page with a keyboard and see where focus is.
- [ ] Text has enough contrast against its background.
- [ ] Form fields have visible labels, not only placeholder text.
- [ ] Headings follow a logical order.
7. Legal and trust pages
- [ ] Privacy policy is present and mentions the tools actually used (analytics, forms, chat).
- [ ] Cookie consent, if required for your audience, works and respects choices.
- [ ] Terms of service or terms of sale, where relevant.
- [ ] Business name and contact details as required for your type of business.
This is not legal advice; have someone qualified review the text itself if you are unsure.
8. SEO settings
- [ ] Each page has a unique title and meta description.
- [ ] The site is not blocked by robots.txt or a noindex setting left from staging.
- [ ] An XML sitemap exists.
- [ ] Redirects from old URLs are in place, if this replaces an existing site.
- [ ] Analytics and Search Console are installed and owned by your business.
9. Account ownership
- [ ] Domain registered in your business's name.
- [ ] Hosting account in your name or with a written arrangement.
- [ ] Admin login for the CMS with full rights.
- [ ] Analytics, Search Console and tag manager accounts with you as owner.
Reporting issues so they get fixed
One issue per row. For each:
- Where: page URL and device.
- Steps: what you did, in order.
- Expected: what should happen according to scope.
- Actual: what happened.
- Evidence: screenshot or short screen recording.
"Contact form broken" is hard to act on. "On iPhone 14 Safari, /contact, submitting with all fields filled shows a spinner that never stops; no email received" gets fixed the same day.
Defect or change request?
This distinction decides who pays.
| Defect | Change request |
|---|---|
| Something in the agreed scope does not work as described | Something new, or different from what was agreed |
| A form fails to send | Adding a new form field you have just thought of |
| The mobile menu overlaps the logo | Changing the menu order after approving the design |
| Wrong phone number supplied by you was entered correctly | Wanting a new page not in the sitemap |
Defects are fixed within the project. Change requests are quoted separately or scheduled after launch. Mark each row with one label and agree on disputed items in a short call rather than long email threads.
Handover items before final payment
Agree these in writing and tick them off:
- [ ] All logins listed above, transferred to your accounts
- [ ] A full backup of the site files and database, or confirmation of where backups are stored
- [ ] Short documentation or a recorded walkthrough of how to edit content
- [ ] List of plugins, services and licences used, with renewal dates and who pays
- [ ] Source files for designs and any custom code, if included in the contract
- [ ] Support terms: what happens if a bug appears after sign-off, and for how long
FAQ
How long should we have to test?
Agree a window in the contract, often one to two weeks. Silence after that window may be treated as acceptance, so put the dates in your calendar.
Can we sign off with minor issues open?
Yes, if both sides list them with a fix date. Many owners pay most of the final invoice and hold back a small portion until the remaining items are closed.
Who tests the payment flow?
You should run a test transaction yourself in test mode, then one small live transaction you refund, to confirm the real payment account is connected.
What if the developer disagrees that something is a defect?
Go back to the written scope and approved designs. If the document is silent, treat it as a negotiation and record what you agree.
If you would like an independent acceptance test of a site someone else has built for you, let us know and we will run the checklist with you.