Accessibility statement

Built for everyone navigating this — not most of us, all of us

Many of the families we serve already navigate the world with assistive technology. The site has to work for them, not despite them. Accessibility bugs are priority bugs here, never nice-to-haves.

Our commitment

We aim for WCAG 2.2 Level AA across every page, and we push for AAA wherever we can. axe-core runs in continuous integration on every route, on every pull request. We also do keyboard-only passes and screen-reader passes (VoiceOver on macOS and iOS, NVDA on Windows, TalkBack on Android) before each release.

What works today

  • Full keyboard navigation across all marketing pages, the parent guide flow, and the dashboard.
  • Drag-and-drop in the goal builder works with a keyboard alone (arrow keys to move, space to pick up and drop).
  • A skip-to-content link as the first focusable element on every page.
  • Visible focus rings on every interactive element, with at least 4.5:1 contrast.
  • Proper landmark regions on every page: <header>, <nav>, <main>, <footer>.
  • Form inputs with associated labels and error messages announced to screen readers.
  • Live-region announcements when dashboard widgets update.
  • Color is never the only signal — every state has an icon or text label.
  • Reduced-motion preference is respected for every animation.
  • A larger-text setting that scales typography 1.0×, 1.15×, or 1.3× without breaking layout.
  • A high-contrast palette toggle for users who need it.

What's not yet here

We're honest about the gaps:

  • Audio narration of the guide flow — coming with our content milestone.
  • Full Spanish translation — first language we'll commission.
  • Tagalog, Vietnamese, Chinese (Simplified), and Korean translations — to follow.
  • A paid third-party audit (Fable or similar) — planned before our first major content milestone.

Assistive tech we test with

  • VoiceOver on macOS (Safari, Chrome).
  • VoiceOver on iOS (Safari).
  • NVDA on Windows (Firefox, Chrome).
  • TalkBack on Android (Chrome).
  • Keyboard-only navigation across all browsers.
  • Browser zoom up to 400%.

We do not yet test with JAWS, Dragon NaturallySpeaking, or switch-control input devices. If you use any of these and run into a problem, please tell us — your report goes straight to the top of the queue.

Telling us about a problem

You can reach us at hello@slscompass.org with the subject line "Accessibility". Tell us what you were trying to do, what device and assistive tech you were using, and what got in your way. We treat accessibility bugs as priority bugs — we'll respond within two business days and tell you a fix timeline.