Colquhoun.AI
← All guides

Research Guides

Map Page Regions Before Reusing a Research Template

· Colquhoun.shop editorial

A research page can have clear headings yet still make readers work through repeated navigation to locate the actual article. Headings organize an argument; page regions describe the surrounding structure. Review both before reusing a template across a growing research library.

This is a manual website-review worksheet, not an automatic Colquhoun.shop feature or an accessibility certification. It focuses on identifying page regions, rather than rewriting the article's outline.

1. Inventory the visible blocks

List the site header, primary navigation, article, related material and footer. Record what each block does, not merely its position or background color. A box on the right could contain essential evidence, an optional explanation or an advertisement; those are different purposes.

In an invented research template, the central article contains the method, results and limitations. A neighboring box links to three related guides. The limitations belong with the article even if the designer gives them a contrasting background; they are not optional simply because they look like a sidebar.

2. Compare purpose with the delivered structure

W3C's page-structure tutorial describes using HTML regions so browsers and assistive technologies can identify them. It presents main for main content, nav for navigation and aside for complementary material that is meaningful on its own. It also recommends identifying multiple navigation menus with labels. W3C: Page Regions

Inspect the rendered page rather than assuming the content editor's labels become the right HTML. Record the observed element or exposed role beside each block. Do not add landmark roles to every decorative wrapper just to increase a count. The goal is a recognizable map, not more markup.

A global menu and an article's table of contents answer different questions. Give them distinguishable names that explain their purpose. A reviewer should be able to tell which menu moves through the website and which moves within the current article without opening every link first.

Write a short task such as “Find the method section, then move to another research guide.” Check whether the exposed regions support that task. Keep this separate from testing the links themselves: a well-named menu can still contain a broken destination.

4. Review template variants separately

Repeat the inventory for an article with no related-links box, a long research report and a page with an additional contents menu. Shared styling does not prove that each variant has the same structure.

On a narrow screen, check where the article and complementary material actually appear. Record the reading order as well as the visual order. If assistive-technology testing is unavailable, say so; source inspection and a phone screenshot do not demonstrate how a screen reader announces the page.

5. Save a region-to-purpose record

Use precise completion language: “Main article and two navigation regions inspected; narrow-screen order reviewed; screen-reader behavior not tested.” A landmark review can make a template easier to navigate, but it does not establish that the research is accurate, that the whole site is accessible or that search engines will rank it differently.

This guide describes the built-in Web Reader and Keyword Density behavior verified for this publication. Available data depends on the page response; these tools do not measure visits or search rankings.