Evidence type: [evidence]
Time horizon: Before launch
Files: frontend/src/pages/Dashboard.tsx:1, frontend/src/pages/Messages.tsx:1, frontend/src/pages/Services.tsx:1
What's happening: These five page components contain zero <h1> elements, while the other 28 pages each open with exactly one. Dashboard, Messages, and Services are the three highest-traffic destinations in the app.
Why it matters: Screen-reader users navigate by heading; landing on a page with no top-level heading gives no orientation. WCAG 1.3.1/2.4.6.
Recommendation: Add a single <h1> to each, matching the existing pattern.
Expected impact: Consistent heading hierarchy across all 33 pages.
Effort estimate: S
Finding ID: UX-M6
Source: docs/agents/pre-launch-report.md
Evidence type: [evidence]
Time horizon: Before launch
Files: frontend/src/pages/Dashboard.tsx:1, frontend/src/pages/Messages.tsx:1, frontend/src/pages/Services.tsx:1
What's happening: These five page components contain zero
<h1>elements, while the other 28 pages each open with exactly one. Dashboard, Messages, and Services are the three highest-traffic destinations in the app.Why it matters: Screen-reader users navigate by heading; landing on a page with no top-level heading gives no orientation. WCAG 1.3.1/2.4.6.
Recommendation: Add a single
<h1>to each, matching the existing pattern.Expected impact: Consistent heading hierarchy across all 33 pages.
Effort estimate: S
Finding ID: UX-M6
Source: docs/agents/pre-launch-report.md