Approving the website design does not mean approving every detail of the working site. Actual text lengths, image loading, and form behavior in the browser may present different issues than the design file. Before going live, the control responsibilities of the employer, freelance designer and developer should be determined.
Perform visual control with real content
Try the longest service title, low-quality source image, and empty description. The height of the cards, the position of the buttons and the readability of the text must also be preserved in these conditions. The narrow screen, horizontal phone and enlarged text should also be evaluated as well as the wide view on the desktop.
Can you see which connection you are on when navigating with the keyboard? Does the focus stay on a meaningful place when the menu is closed? These questions are part of accessibility check. Automated checking tools are useful, but will not find all usability problems on their own.
Try the client's basic task from start to finish
Follow the path to find a service, move on to the sample job, and request a quote. Verify not only the empty error status of the form but also its successful submission in the test environment. Plan with the responsible person so that test messages do not interfere with the actual customer record.
- Are internal links and legacy URL redirects going to the correct destination?
- Do the cover, favicon and sharing image belong to the relevant page?
- Do the title, description and canonical describe the correct page?
- Does the missing page provide a meaningful 404 and return path?
- Does content that fails to load remain on hold forever?
Set explicit acceptance condition for publication decision
Record the importance, culprit and final check result for each issue. Don't equate a non-working application flow with a small gap difference. The technical team should prepare the return plan and available backup. After going live, the operation of the domain name, server and external services in the real environment is also verified.
With Selçuk Aker we can predetermine which screens and statuses will be checked in the delivery of website design. This checklist is not a substitute for security testing or a comprehensive software audit.
Frequently asked questions
Is seeing the design file enough?
No. The implemented interface must be checked against real content and interaction.
Can everything be verified locally before publishing?
Many content and interface controls can be made. Domain name, live services, and server-related operations also require post-broadcast verification.
Who should be in charge of testing?
Designate separate responsibilities for design, technical operation and content accuracy and collect the results in a single list.
