Page titles are clear and descriptive

WCAG 2.2 Success Criterion 2.4.2 requires that web pages have descriptive titles that identify their purpose — this is a Level A requirement, meaning it applies to all conformance levels including Section 508 compliance. Vague page titles like "Home" or framework defaults like "Create Next App" break screen reader navigation (users tab through open tabs by title), degrade search engine indexing, and prevent bookmark identification. For government sites with dozens of service pages, non-descriptive titles make the site unusable for the blind users who rely on page title as their primary navigation landmark.

Export a metadata object from every page file. Use the pattern "Page Name | Agency Name" so titles are unique and scannable. Target under 70 characters total.

// app/about/page.tsx
export const metadata = {
  title: 'About the Department of Example | Agency Name',
  description: 'Learn about our mission, leadership, and organizational structure.',
}

// app/services/benefits/page.tsx
export const metadata = {
  title: 'Benefits Programs | Agency Name',
}

Avoid generic titles on any page: "Page", "Home", "Services", or any framework default are all failures. Run a title audit across all routes by grepping for title: in page files and confirming each is unique and descriptive.