Skip to content
Interface language: English
Design / Signal

Website acceptance checklist: from first visit to enquiry

Check a business website before launch: test user journeys, contact forms, accessibility basics, language versions and fixes.

Article language: English

Sunlight falls across pale stone steps leading to an arch with a view of water and mountains.
In this article

“It works for me” is the start of a website check, not an acceptance record. Open the service page on your phone, find the terms of working together, move to contact and deliberately make a mistake in the form. Can you correct it? Checking real tasks reveals more than a tour of attractive screens. It also leaves a useful record of what works, what needs fixing and how to check the result again.

Prepare the plan before the project ends. It should identify the site version, environment, devices and people accepting the work. Visual design, technical SEO and code handover each have their own conditions. Here, the question is whether the finished site lets people complete the agreed tasks.

How do you choose scenarios instead of clicking at random?

Turn goals from the brief into short tasks. For example: find out whether the company takes on a particular kind of project, find a way to make first contact, read an article and return to a related service. The person taking part should know what they are looking for without being directed to a particular button.

Record the starting state and expected endpoint for each scenario. Arriving from an advert, through a referral or directly on an article are different journeys. Don’t start every test on the home page if visitors are also expected to land elsewhere.

Check the signed-in and signed-out versions where relevant. A project author’s permissions can conceal a problem with a public link or form. The test should reflect the access an ordinary visitor has.

What should you check on a phone and a larger screen?

Use real content, long titles and at least one narrower screen. Look for horizontal scrolling, overlapping elements and buttons obscured by a fixed header. Check the page after changing the screen orientation and enlarging the text, too.

Check whether images reserve space before they load and whether text remains readable across an image. Scroll down and back up, open the menu, then move quickly between several pages. You may catch behaviour that a static preview cannot show.

If animation is part of the design, check it with reduced motion enabled as well. Establish whether delays prevent people from reaching the essential content. The five-second test examines first impressions; completing a task calls for a longer test. See also the article on the five-second test (in Polish).

How should you test the contact form for acceptance?

Send an enquiry with valid details and confirm that it reaches the right destination. A success message on the site does not check the inbox or the system used to handle enquiries. Record who saw the message and whether it contained everything they needed.

Then test errors: leave a required field empty, enter an invalid address and try with the connection unavailable. The message should identify the problem and let the visitor return to the task. Check that entered details do not disappear unnecessarily and that clicking again does not create several identical enquiries.

If contact leads to an external calendar or email, open the actual destination. Check the language, time zone and accessibility of the route being used. Each link from the service page should lead to the step its label promises.

How do you check basic use without a mouse?

Move through the site using a keyboard. See which element has focus, whether the order makes sense and whether you can close a menu or window. Forms need clear labels, and visitors should be able to find an error message without guessing.

W3C publishes preliminary accessibility checks covering titles, headings, contrast, enlargement, keyboard use and forms, among other things. The resource makes the limits of these checks clear. Passing a short test is not a full accessibility assessment of the site.

Record the scope of the checks in the acceptance record. If the project needs a wider audit, agree on it separately. That way everyone knows what was actually checked and which barriers may still need investigation.

How do you check language versions and edge cases?

Follow the same journey in every published language. Check menus, errors, contact and the materials linked from each version. If an article is available only in Polish, tell visitors clearly instead of presenting an apparent translation.

Aeneia conceptual photography

Open a nonexistent address, an old link and an empty search result. Check whether the visitor has a way to continue. Assess response codes and indexing with your technical SEO checklist: the appearance of an error page alone does not tell you what response the server sends. For context, see the article on technical SEO checks before publication (in Polish).

How do you report a bug someone can reproduce?

Record the address, starting state and steps taken. Include the expected result and what actually happened. A screenshot helps show the layout, but a form error also needs a description of the test data and when the problem occurred.

For a working example, imagine opening an article on a phone from an external link, expanding the menu and choosing contact. If the menu stays over the content, record that exact sequence. A test starting on a different page may not reveal the fault. Once it is fixed, repeat the same scenario and record the result with the issue so the team knows what was accepted.

How do you build a small test matrix before the acceptance meeting?

Pair tasks with screen types and site states. You do not have to test every combination on every device. Choose journeys where a fault would prevent contact: landing directly on a service, moving from an article to the offer, opening the menu on a phone and sending a form. For each, record separately the result the visitor expects and how the company will confirm it.

Imagine a buyer opens an article on a phone, moves to a service and wants to ask about its scope. The test should end with the enquiry reaching the right person. Clicking the button is an intermediate step. If information about the service is missing along the way, review the information architecture of a B2B website before adding another contact button. More detail is available in the article on B2B website information architecture (in Polish).

Leave room for dependencies beside each task. A form can work correctly even though the inbox is assigned to someone who no longer owns it. The fix then involves the handling process as well. The record should name someone on each side of that handover rather than close the issue as “outside the website”.

What if someone interrupts or repeats an action?

Test a slower connection and a return to an unfinished task. See what happens after refreshing, reopening the tab or activating a button twice. Agree on the expected behaviour for the solution in use; not every field should retain its data after the browser closes. What matters is whether the visitor understands the state and can continue safely. For a shop, also test changing quantities and correcting the cart (in Polish), checking its current state after going back, removing an item and retrying.

When designing a B2B contact form, establish which details are needed for a first reply and what a submission confirmation means. Further guidance appears in the article on B2B website contact forms (in Polish). For acceptance testing, prepare a fictitious enquiry clearly labelled as a test. Do not use real client documents to test attachments. If the form accepts files, include a separate state, correction and confirmation for each attachment (in Polish) in the tests.

When moving between pages, check the interface state as well: whether the menu closes, the scroll position and focus—the element currently operated with the keyboard. The article on website microinteractions (in Polish) covers how to signal waiting and completion. A success animation should correspond to a confirmed event, and a waiting state should be distinguishable from an error.

How do you decide which defects block launch?

We suggest three working categories, agreed before acceptance. A blocker prevents the main task or displays materially incorrect content. A significant defect makes the task harder, but a clear alternative route exists. A minor fix changes neither the meaning nor the accessibility of the agreed action. This is a way to organise a project, not a platform standard or an automatic legal classification.

If contact cannot be operated with a keyboard, identify and fix the specific barrier. Do not treat it as less significant simply because the form works with a mouse. The business website accessibility guide (in Polish) helps define the scope of a broader assessment. A wrong company name in the footer will need a different person to sign off on it than a broken integration.

How do you keep evidence and avoid reopening the same issues?

Identify the exact version the team is accepting, for example by deployment ID and date. When a fix is made, retain the original steps to reproduce it, the new result and the name of the person who checked it. If the change affects a shared header, repeat the affected journeys on several types of page. You do not need to retest the whole project, but you do need to cover the effects of the fix.

Finish acceptance with a list of closed and outstanding issues. For every defect left open, add the agreed decision and deadline. Approval to launch then has a defined scope, and whoever maintains the site later knows the starting point. After acceptance, give the team the outage response plan agreed for this site and establish who is responsible for maintenance (in Polish). When drafting the plan, you can use the guide to preparing a website outage response plan (in Polish).

How do you close acceptance with a concrete checklist?

For each scenario, record the result, device, browser and date. Add reproduction steps and expected behaviour to each bug report. Name the person making the fix and the person confirming its acceptance. Repeat the task after the change is deployed.

  • The offer is understandable and leads to a working way to make contact.
  • The form or calendar leads to a confirmed result.
  • Scenarios pass on a phone, with a keyboard and in the language versions.
  • Errors offer a clear way back.
  • Open issues have owners and agreed deadlines.

Keep functional acceptance separate from the handover of code, accounts and documentation (in Polish). Both should be in scope. You can agree on them as part of the Aeneia Design offer before the project goes live.

Add long names and real copy (in Polish) to the test set. A short label in a mock-up will not test what happens to the full name of a service or a detailed error message. You are accepting a site for your actual offer, not for obliging placeholder text.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear