You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
404 Not Found page lacks document title metadata, falling back to generic site title #61
Website baseline: ac81655f4ac3aa1250023a3a9a5e3a93c00ac059 (website branch), checked locally on 2026-10-28.
Observed behavior
The 404 Not Found page component (src/app/not-found.tsx) does not export a Next.js metadata object or render a <title> tag.
When a user visits a non-existent URL (e.g. /404/ or any broken route), the document title remains the generic root layout fallback: OWASP Hunting — Security Testing Documentation
This violates WCAG 2.4.2 Page Titled (Level A) and creates disorientation for screen reader users and users navigating browser history or open tabs, as there is no document title indication that a 404 error occurred.
Reproduction
Navigate to /404/ or any non-existent page like /docs/nonexistent-route/.
Inspect document.title or observe the browser tab title text.
Observe that the title does not mention "404" or "Page Not Found", remaining identical to the site homepage.
Expected behavior
Export metadata in src/app/not-found.tsx:
exportconstmetadata={title: "404 - Page Not Found",description: "The requested page could not be found.",};
This ensures the page title renders as 404 - Page Not Found — OWASP Hunting according to the title template in src/app/layout.tsx.
Note: This is distinct from #43, which addressed static export validator link checking; this report concerns the document title accessibility metadata of the 404 error page.
Marked screenshot
Red boxes, numbered callouts and AUDIT ANNOTATION panels were added temporarily in the browser to identify the observation/request. They are not implemented website features. Capture notes.
Issue report only; no PR or website code changes. AI assistance: Google Antigravity (Gemini); browser investigation via Playwright, evidence annotations and report drafting. Checks were executed locally; payload examples remained inert text; no target testing was performed.
Activity
Rishini-Dharan commentedon Nov 5, 2026
/take-pr
Rishini-Dharan commentedon Nov 5, 2026
/take-pr
github-actions commentedon Nov 5, 2026
@Rishini-Dharan is now assigned to this issue.