Prepare a documented decision

Website acceptance log: checks, issues and evidence

Choose a status for each check and record what was observed. A successful check needs evidence; an unchecked item stays unchecked.

A working record for your team

These proposed checks organise a review. They do not establish legal compliance, accessibility conformance, security certification or approval to publish. Adapt the scope and assign a person to make the release decision.

Critical markers identify checks to examine before release. Explain every not-applicable status. Record a URL, steps, expected and observed behaviour, date and evidence reference without entering passwords, keys or personal details.

Your entries stay in this tab; they are not sent to the website. Download a JSON copy to keep them, then import it to resume. Closing or reloading the tab loses work that has not been exported.

Content and evidence

Decision-relevant claims Critical

Check prices, capacity, dates and terms against approved references; record source and period.

Method : Verify sources and evidence in web content

Data and entries

Images and media

Rights and representation Critical

Find permissions; distinguish illustrative scenes, actual teams and attributable work.

Method : Plan original photography for a website

Journeys and forms

Complete enquiry Critical

Using an authorised address, follow a valid enquiry through handling; distinguish receipt from response.

Method : Design a contact form that genuinely helps

Accessibility

Languages

Operations

Decision and rollback Critical

Name the decision owner, blocking defects and rollback procedure; plan post-release verification.

Method : Prepare a response to a website incident

What to do with findings

Assign unresolved issues, prioritise their effect on visitors and repeat the relevant checks after fixes. A passed status without observations is not independent proof. Keep exports with the tested version and agreed decision, and repeat essential journeys after deployment.