Accessibility
We aim to make this site usable for everyone. If you hit an accessibility barrier, please tell us.
We’re working toward strong semantic structure, keyboard navigation, visible focus, and reduced-motion support.
Accessibility (WCAG 2.1 AA) checklist
We treat accessibility as a measurable standard, not a vibe. Each item below has an explicit status.
- Text & UI element contrast meets WCAG 2.1 AA: 0+ (audit pending) Verify contrast ratios: ≥ 4.5:1 for body text; ≥ 3:1 for large text and essential UI.Evidence: Lighthouse report (once published)
- All interactive elements reachable by keyboard: 0+ (audit pending) Test tab order, visible focus states, and skip-link behavior across all pages.Evidence: Lighthouse report (once published)
- Semantic landmarks used consistently: Published (baseline implemented) Use <header>, <nav>, <main>, <footer>; ensure exactly one <main> landmark per page.
- Meaningful alt text for non-text content: 0+ (review pending) Ensure images/logos/icons have appropriate alt text (or aria-hidden when purely decorative).
- Forms have labels and clear error states: 0+ (as forms are added) If a form exists, every input needs a <label for>, and errors must be announced to assistive tech.
Status meanings: Published = implemented and documented; 0+ = planned or in progress; “audit pending” means a repeatable test run has not yet been published.
Accessibility verification evidence
Published receipts live here as we generate and ship them.
- Lighthouse accessibility audit (generated locally, then uploaded)
- Axe / manual screen-reader notes — 0+ (coming soon)
- Keyboard navigation walkthrough — 0+ (coming soon)