# Website launch checklist Use this worksheet for an AI-built website or any other small website. Record evidence for the journeys your customers actually use. This is a practical review aid, not a complete security or accessibility certification. **Website and environment:** ____________________ **Reviewer and date:** ____________________ **Release/version:** ____________________ **Main customer journey:** ____________________ **Business owner for follow-up:** ____________________ ## How to record a result Use **pass**, **fail**, **unverified** or **not applicable**. A pass needs an observed result. For “not applicable”, explain why the feature is outside this website's scope. Use authorised test accounts and harmless test records. ## 1. Customer promise - [ ] The main action and expected result are written down. - [ ] Service details, contact information and next steps are accurate. - [ ] Every important link and button reaches its intended destination. - [ ] Demonstration content is removed or clearly labelled. ## 2. Forms and notifications - [ ] One uniquely labelled submission is traceable from the form to its intended destination. - [ ] The success wording matches what the system has actually accepted or completed. - [ ] Required fields and invalid values produce useful feedback. - [ ] A failure preserves useful input and offers a next step. - [ ] Repeat clicks and uncertain retries do not create unintended duplicates. - [ ] The receiving system validates the input as well as the browser. - [ ] A notification problem can be investigated using an identifier or timestamp. ## 3. Storage and environments - [ ] The actual read and write paths are identified. - [ ] Records reach the intended development, staging or production service. - [ ] The test record exists in the intended backend and, when sharing is expected, is retrievable from a separate browser profile or another device using an authorised account. - [ ] Browser-only storage, caching and any demo mode are understood. - [ ] Empty and unavailable-data states do not silently display fabricated activity. ## 4. Mobile and accessibility - [ ] The main journey works on a phone with the keyboard visible. - [ ] Content and controls remain reachable in a narrow view and when enlarged. - [ ] Keyboard navigation has a usable order and visible focus. - [ ] Menus and dialogs can be opened, used and closed with the keyboard. - [ ] Form controls have meaningful labels and useful instructions. - [ ] Errors and dynamic outcomes can be discovered with assistive technology. - [ ] Any automated findings have been reviewed alongside manual checks. ## 5. Permissions and configuration - [ ] A qualified reviewer has checked the applicable access rules with test accounts. - [ ] Private records remain unavailable to accounts without the required access. - [ ] Hiding interface elements is not the sole protection for restricted operations. - [ ] Private credentials are kept out of public code and shared diagnostic material. - [ ] Public keys or identifiers are understood according to their intended permissions. - [ ] The review's scope and unresolved questions are recorded. ## 6. Failure and recovery - [ ] Slow and unavailable dependencies have been exercised in a controlled environment. - [ ] The business can access the domain, hosting, email and deployment accounts. - [ ] An owner is assigned to important operational failures. - [ ] There is an actionable route for finding stored enquiries and failed notifications. - [ ] A previous working release and rollback procedure are known. - [ ] Important data has a documented backup and restore procedure. - [ ] An isolated test restore makes the expected records readable; the result and limitations are recorded. Recovery remains unverified if only documented. - [ ] Recovery accounts for database changes as well as application code. - [ ] The main journey will be rechecked after deployment. ## Findings and release decision | Check or issue | Result | Evidence/location | Owner | Next action | | --- | --- | --- | --- | --- | | Main journey | | | | | | Permissions | | | | | | Recovery | | | | | **Issues that must be resolved before launch:** ____________________ **Accepted limitations and reasons:** ____________________ **Decision and responsible person:** ____________________ **Next review date or trigger:** ____________________ Read the [website readiness walkthrough](../articles/02-ai-website-readiness.en.md) for the reasoning behind these checks. Technical references include [W3C's form guidance](https://www.w3.org/WAI/tutorials/forms/notifications/) and [OWASP's authorisation guidance](https://cheatsheetseries.owasp.org/cheatsheets/Authorization_Cheat_Sheet.html). Prepared 13 November 2026.