Accessibility

Last reviewed September 2, 2026. Problems to support@lantern.family.

We want Lantern to work for every parent and every child, including people who use a screen reader, keyboard, or switch device. We aim for the Web Content Accessibility Guidelines (WCAG) 2.2, level AA, and we build with them in mind rather than retrofitting: the child's wall uses large touch targets, icon-and-word buttons a non-reader can learn, real browser back and forward, and visible keyboard focus; the parent pages use plain words and honest headings.

Known limitations

We would rather list these than claim them away. The child's wall is built for taps and large targets, and works best on a touch device. The join flow uses a QR code; the same invite always carries a plain link as well. Captions on videos are YouTube's own: whether a given video has good captions is up to its creator, and Lantern cannot add them. The admin and report surfaces are being reviewed against WCAG 2.2 as the alpha matures.

Tell us what we missed

If any part of Lantern is hard for you or your child to use, write to support@lantern.family and a person will read it. Accessibility reports go to the front of the queue.