Accessibility

Accessibility commitment for the public-site foundation

Accessibility is part of the public-site build standard now, not a cleanup task for later.

Last updated July 26, 2026

What this slice aims for

The current release aims for clear structure, readable copy, keyboard-reachable navigation, mobile-ready layouts, and sensible contrast across the public site shell.

  • consistent navigation and footer patterns
  • semantic headings across public routes
  • buttons and links that go somewhere real
  • forms that remain understandable as real lead-capture flows on the starter-resource routes

Known limitations in the current release

The starter-resource flow now submits real data, but other public-site routes still have lighter or more limited form behavior while later slices add fuller follow-up workflows.

What changes later

As the site adds real checkout, booking, and lead capture, accessibility review should expand with those flows instead of treating the current public shell as the whole job.