Accessibility

A site about disability that you can't use is a contradiction.

Waypoint is read by disabled parents and by disabled young people. So this page doesn't claim we're accessible — it tells you precisely what gets tested before every deploy, what has never been tested, and how to report the parts we got wrong.

Conformance status

Partially conformant with WCAG 2.2, Level AA

Partially conformant is the honest label, and it is a defined one: it means most of the site meets the standard, but we cannot yet claim all of it does. Our target isWeb Content Accessibility Guidelines (WCAG) 2.2, Level AA, across every page of waypointchild.com.

We do not claim Level AAA. Some AAA criteria are worth aiming at for content like ours — the reading-level one especially, which is why every guide carries a plain-language summary — but claiming a level we don't audit against would be the same kind of borrowed authority we refuse everywhere else on this site.

What is tested, automatically, before anything ships

Every deploy has to pass these

These run in continuous integration. A failure blocks the merge — it doesn't file a ticket for later.

  • axe-core on every page, not a sample. Every page of the built site is scanned and any serious or critical violation fails the build. As ofSeptember 8, 2026, the scan reports zero violations at any severity across the whole site.
  • Scanned twice, in both builds. Some components render differently depending on whether a linked page is published yet. We scan the draft build and the real production build, because a component can pass in one and ship broken in the other — which is exactly how a card of unreadable grey text once reached a live page here.
  • A real keyboard walk. A browser presses Tab through the home page, both tools, a guide, the start-here checklist, and search. It fails if the skip link isn't the first stop or stays invisible when focused, if any control can't be reached, if focus gets trapped, or if a focused control paints no visible focus ring.
  • Both tools must be completable without a mouse. The keyboard walk actually runs the SSI deeming calculator and the Regional Center finder with the keyboard alone and requires a real answer back. A tool you can Tab across but never run is still a mouse tool.
  • Under the real security policy. The scans replay the deployed Content-Security-Policy, so a policy change that silently kills a control fails here instead of in front of a parent.
What has not been tested

The gaps we know about

Automated testing catches roughly a third of real accessibility barriers. It cannot tell you that a heading is misleading, that a reading order is confusing, or that an error message makes no sense out loud. So this list matters more than the one above.

  • No screen-reader testing by a screen-reader user. Nobody has sat down with NVDA, JAWS, or VoiceOver and worked through this site end to end. This is the largest untested area, and it is the one we most want to fix.
  • No independent third-party audit. Everything above is self-testing. We have not paid for an outside accessibility audit, and we will say so on this page until we have.
  • No testing with switch access, voice control, or screen magnification beyond browser zoom.
  • Spanish pages are not separately audited. Spanish content is still being released page by page behind a credited bilingual reviewer; its accessibility testing will follow the same gates once it ships.
  • Cognitive accessibility is a design intention, not a tested claim. Plain language, short steps, and a summary box atop every guide are deliberate — but we have not user-tested them with people with cognitive or learning disabilities.

If you are an accessibility tester, a screen-reader user, or a disabled parent willing to tell us what breaks, we would genuinely rather hear it than not. Write toprivacy@waypointchild.com.

Reporting a barrier

Tell us, and we'll treat it as a bug

Email privacy@waypointchild.com. If you can, include the page address, what you were trying to do, and what happened instead — plus your browser and any assistive technology you were using. Any of those details helps; none of them are required, and "this page doesn't work with my screen reader" is a perfectly good bug report.

What we commit to:

  • We reply within 5 business days, even if the reply is "we're still on it."
  • Accessibility reports go to the front of the queue, ahead of new features and new content.
  • If we can't fix something quickly, we tell you what we're doing instead — and, where it matters for your child, we'll get you the information another way.
⚠ If you need the content and can't reach it:Don't wait on a fix. Email privacy@waypointchild.com and say what you were trying to find. We will send you the same information in whatever format works — plain text in an email, read to you over the phone, whatever gets it to you today.
Technical notes

The details, for anyone checking our work

  • Standard: WCAG 2.2, Level AA. Status: partially conformant.Scope: all of waypointchild.com. The Waypoint app at app.waypointchild.com is a separate product and is not covered by this statement.
  • Last tested: September 8, 2026, and again automatically on every deploy since.
  • Method: automated testing (axe-core) plus scripted keyboard-only testing in a real browser. No manual assistive-technology audit yet — see the gaps above.
  • Technology relied upon: HTML, CSS, and JavaScript. Pages are built as static HTML and the content is readable with JavaScript disabled; the two calculators need JavaScript to compute, and each links to the underlying agency source so you can reach the same answer without them.
  • No PDFs. We publish letters and guides as web pages, not downloads, so they stay readable, resizable, and translatable.
  • Motion: the site honors prefers-reduced-motion. There is no autoplaying video, no carousel, and nothing that flashes.
Why this page is this blunt

Most accessibility statements are written to be defensible. This one is written to be useful — because the people most likely to read it are the people most likely to be locked out, and they have been told "we are committed to accessibility" by enough organizations already. You deserve the list of what we actually haven't done.