Design acceptance: check results in real pages
Check content, mobile layouts, interactions, and actual receipt through real customer tasks, then record issues and approval scope.
A design system must work in actual pages. Before approval, try real content and customer tasks to find layout and interaction problems that a single design image cannot reveal.
First identify what you are approving: a visual direction, clickable prototype, or implemented website. Their checkable scope differs. A successful prototype demonstration does not establish working functionality.
Start with important tasks
| Area | What you can do |
|---|---|
| Content and brand | Check services, areas, conditions, photos, and contact details |
| Reading and layout | Try phones, long headings, both languages, and page zoom |
| Navigation and interaction | Find services, open and close menus, visit and return |
| Inquiries and booking | Send an agreed test and verify receipt |
| Recovery | Try missing information or no matches and understand the next step |
Add search, payments, or account tasks when the project includes them. A simple service website does not need tests for functions it does not offer. Detailed form checks are in the inquiry and booking guide .
Owners observe; teams complete technical checks
You are well placed to verify business facts, reading comfort, and practical difficulties. The team adds browser environments, keyboard and assistive-technology checks, data verification, and relevant technical tests. You can review problems together without becoming a testing specialist.
For a covered mobile booking button, record the page and screenshot. The team investigates the layout and repeats the original task after correction. Automated checks do not replace actual interaction or establish security or accessibility certification.
Keep a short, actionable record
Start with four items: the page, the problem, the intended result, and the responsible person . The team adds technical details, evidence, and recheck results. Mark unchecked areas as “not tested” rather than assuming they passed.
Address blocked customer tasks first, then smaller presentation changes. When shared rules change, check other uses rather than fixing just one page. Rechecking related behavior after a change is called regression checking.
State what approval covers
Record the version, accepted scope, and remaining items. Identify what must be completed before launch and what is agreed for later. If a prototype form is not connected, say so; visual approval does not complete the function.
For SiteMonk projects, use the handoff guide and website design process . W3C Easy Checks provides an accessibility starting point; a full assessment requires work appropriate to the project.
For a SiteMonk website project , we agree the pages and functions to deliver, then use those customer tasks to review completion with you. Bring business corrections and observed problems; we handle the implementation checks and follow-up.