Specify a short title that names what the page actually helps someone find or do, then read it without the page around it. If it could describe several neighbouring pages equally well, make the subject more specific. Keep uncertain wording as a proposal until the content owner has established the page’s purpose. A clear title cannot repair unclear content by guessing what it ought to say.
This matters outside the page itself. W3C’s explanation of Page Titled states the requirement: “Web pages have titles that describe topic or purpose.” It explains that a browser may display that title in its window title bar or as the name of a tab. People can identify their current location without first reading the page. [1]
Review the document title, not just the heading
For an HTML page, the document title is supplied through the title element. The visible main heading is part of the page content. A large heading saying “Opening hours” does not establish what the browser tab says: the document title could still be “Information”. Inspect the title separately rather than assuming the heading proves it is right. [1]
The two pieces of wording can agree without being identical. A page heading might say “Opening hours”, while its document title adds the studio name to make sense away from the page. Neither source makes identical heading and title wording a requirement. The important question here is whether the title accurately identifies this page’s topic or purpose.
W3C technique G88 recommends that a title identify the subject, make sense out of context and be short. It separately says that identifying the site and being unique within it may also be helpful. Those additional suggestions should not be presented as if each were a separate normative requirement. Techniques are examples of ways to meet WCAG, not mandatory methods. [2]
For this review, use G88’s three checks: the page has a title; the title is relevant to its content; and the page can be identified using the title. Comparing neighbouring titles is a useful way to expose ambiguity, not a substitute for checking the content. [2]
Example review card
Leila is the human website content owner in this fictional community repair-studio scenario. The following copy descriptions and current titles are illustrative inputs, not observations from a real website. No public site has been inspected. This MAJLS proposed review card is an editorial aid, not a W3C standard.
| Page/content evidence | Current title | Proposed wording | Check or unresolved point | Human owner |
|---|---|---|---|---|
| Illustrative page lists the repair studio’s opening hours | Information | Opening hours - Example repair studio | Names the subject; Leila must confirm that the actual page is about opening hours | Leila |
| Illustrative page explains how to bring a lamp for assessment | Information | Bring a lamp for assessment - Example repair studio | Use only if the actual copy explains this process, not merely a lamp service overview | Leila |
| Illustrative page mixes booking instructions with venue directions; dominant purpose unclear | Information | Held: no replacement proposed | Establish purpose and decide whether the content needs clarification before titling | Leila |
The first two proposals distinguish two different reader needs without adding an unsupported promise. In particular, “Bring a lamp for assessment” does not promise that the studio will repair every lamp. The held row is useful work too: it records a decision the owner needs to make instead of disguising uncertainty as polished wording.
In a real review, attach the page address or internal identifier, the relevant copy excerpt and the observed document title to each row. Keep the observation and proposed replacement in separate fields. Until someone inspects the rendered page, label that observation unverified; do not copy the proposal into it.
Prepare, approve, implement, verify
An assistant may prepare the comparison from supplied page copy and title observations, suggest concise alternatives, and identify duplicate or vague wording. Its handoff should include the content evidence for each suggestion and any unresolved purpose. That is preparation, not permission to change the website, and it assumes no MAJLS integration or website access.
Leila approves the final title wording and the proposed changes. She also resolves the mixed-purpose page: she may clarify its main job or commission a content change before approving a title. The web maintainer implements only the authorized changes and checks the rendered browser title against both the approved wording and the actual page. A saved content-management field alone is not that final check.
If the browser still shows the old wording, or the new wording no longer fits the content, record the mismatch and return it to the responsible person. Do not report a proposal as an implemented result.
Checklist for the next title review
- Read each title alone, without the heading, navigation or surrounding copy. Can you tell what the page is for?
- Compare sibling titles with their actual content. Replace repeated generic labels with supported distinctions, not arbitrary variations.
- Keep proposed wording separate from the observed rendered title and retain the evidence behind each.
- Hold pages whose purpose is unresolved; ask Leila to settle the content question before approving wording.
- After an authorized change, verify the browser title against the approval and page, and record any mismatch.
This is a focused title review. It does not guarantee search rankings, impose a fixed character limit or certify the accessibility of the whole website.
