Learning AI · Practical guide

Review a reader’s journey before publishing the website.

A page window with navigation, content and review checklist.
Image: Eric Muriel · © Eric Muriel

Organise a manual review of a content site in its test environment. This does not replace every technical check; it helps identify visible problems and record what was actually inspected.

What you will find

  • Start at the homepage
  • Check reading and controls at two sizes
  • Follow translations and external links
  • Leave a checklist someone else can repeat

01Start at the homepage

Choose a specific task: find a guide, read its example and reach the next resource. Use navigation rather than typing direct URLs. This reveals pages that exist but are difficult to discover.

Check titles, descriptions and links against the content. A link promising a template should lead to that template or clear instructions for obtaining it. A responding destination is not automatically the right destination.

[2] GOV.UK Service Manual

02Check reading and controls at two sizes

Inspect narrow and wide screens. Look for clipped text, horizontal scrolling, overlapping buttons and hard-to-read paragraphs. Open menus and expandable controls encountered along the journey.

Also move through links with the keyboard and check that focus is visible. This is an initial check, not a declaration of complete accessibility compliance.

[1] W3C · Web Accessibility Initiative

03Follow translations and external links

On a bilingual site, switch language from an article. Check that it reaches the equivalent article rather than just the homepage. Verify that text and labels match the selected language.

Inspect contact and service links without submitting forms or creating real operations during review. If an action needs a complete test, agree on an appropriate environment and data first.

04Leave a checklist someone else can repeat

Record page, task, screen size, outcome and evidence. Separate issues blocking reading or action from later improvements. List unreviewed pages so “review completed” does not imply broader coverage than you achieved.

Repeat affected journeys after fixes. Keep the project’s automated route and metadata checks too. Manual review and those tests answer different questions.

Frequently asked questions

Does checking the homepage establish that everything works?

No. Review the page types and actions in your chosen scope and state that coverage. A correct homepage does not establish that its destinations work.

Sources (2)

  1. Content Structure · W3C · Web Accessibility Initiative — Semantic structure of headings, sections and lists.
  2. Using moderated usability testing · GOV.UK Service Manual — Check journeys through specific tasks.

Editorial approach and corrections