Skip to content
Beta

Accessibility

Every parent should be able to use KIZGO. Here is what we do about that, and how to tell us when we fall short.

Last updated July 8, 2026

Our standard

We build KIZGO against the Web Content Accessibility Guidelines (WCAG 2.1, Level AA) and treat accessibility as part of the design system, not an afterthought.

What that looks like here

  • Full keyboard navigation with a visible focus indicator on every interactive element.
  • Touch targets at least 44px on phone-sized screens.
  • Text and interface colors that meet AA contrast ratios.
  • Semantic HTML with labeled forms, landmarks, and dialog semantics for overlays.
  • A full list alternative to the map: every place shown on the map is also reachable through the place list and search, with the same details — nothing lives only on the map canvas.
  • Alternative text on photos, and honest text descriptions where data is unknown.

Known limitations

The interactive map itself (panning, pin hovering) is a visual, pointer-oriented surface. All of its information is available through the list view; we keep improving the map’s own keyboard support.

Tell us

If anything on KIZGO is hard to use with assistive technology, email support@kizgo.app — a person reads it, and accessibility reports get fixed with priority.