Opens in a new tabSkip to content
Agent LighthouseAgent Lighthouse

    Searches the text of every published page. The evidence sources themselves are not in this index — search all of them on the trusted sources page.

    GitHub ↗
    Browse checks and page contents
    operability-safety/document-title

    Page has a non-empty <title>

    What it checks

    The document title is the page’s identity in the accessibility tree and in agent context windows. A missing/empty title leaves the page unnamed.

    Why it matters

    The <title> element is the document’s name. A browser tab list exposes it, assistive technology announces it on page load, and Google uses it as a source for the title link in search results. A page with a missing or empty title is therefore unnamed in every consumer that identifies a page by name rather than by URL.

    Evidence

    • Google: title links are generated from several sources, first among them “Content in <title> elements” — developers.google.com/…/title-link (verified 2026-08-21)
    • MDN: the title “defines the document’s title that is shown in a browser’s title bar or a page’s tab”. It adds that “A common navigation technique for users of assistive technology is to read the page title and infer the content the page contains”, and gives the guidance to “make titles unique to every page” — developer.mozilla.org/…/title (verified 2026-08-21)
    • WCAG 2.2 documents the page-title expectation as a Level A requirement (2.4.2 Page Titled) — referenced from the failure/technique set at w3.org/…/F41 (verified 2026-08-21)
    • Agent tool-chains address pages as tabs. Playwright MCP browser_tabs will “List, create, close, or select a browser tab”, and chrome-devtools-mcp list_pages will “Get a list of pages open in the browser”. On that surface a document’s title is the only identifier a human or a model can read — github.com/…/playwright-mcp and github.com/…/tool-reference.md (both verified 2026-08-21)

    Limits

    Neither Playwright MCP nor Chrome DevTools MCP documents the page title as part of the accessibility snapshot the model reasons over. A tree-driven agent can therefore complete tasks on an untitled page. The documented dependence is on identification and citation surfaces, not on action. The check is also presence-only. A site shipping the same generic title on every page — the actual disambiguation failure — passes. And JS-assigned titles in a CSR SPA fail here, while every real consumer that executes JS sees a title.

    How it scores

    Documented consumer behavior (Google states it generates title links from <title> content) plus a ratified Level A success criterion (WCAG 2.4.2 Page Titled) with universal browser/AT implementation.

    Sources