Review a reader’s journey before publishing the website.

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.

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.

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.

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.