LEELALU Accessibility: where we stand, in plain language

What works today

Built in from the first page, not bolted on.

Structure and navigation

Semantic HTML with a skip link and landmark regions on every page, so screen readers and keyboards can jump straight to content.
Every interactive element is reachable by keyboard, and the navigation has a no-JS fallback: if scripts fail to load, the menu still works.
Every image carries alt text. Decorative images are marked so assistive tech skips them.

Comfort and readability

prefers-reduced-motion is respected. If your system asks for less motion, Lu's breathing animation stops.
Color contrast is tuned on our cream palette so text stays readable, not just pretty.
Browser text zoom is respected. Enlarge the text and the layout adapts instead of breaking.

Not done yet

The part most accessibility pages leave out.

No formal audit yet

We have not run a formal WCAG audit. The practices above are our own engineering discipline, checked by us, not yet verified by an independent review.

Target: WCAG 2.2 AA

Our target is WCAG 2.2 AA conformance before launch. It is a launch requirement on our checklist, not a someday item.

App preview in progress

Screen-reader passes on the app preview are still in progress. The preview shows designed behavior, and its assistive-tech experience is not finished work.

Tell us what is broken

If something gets in your way, we want to know.

Report an accessibility barrier

Email us at hello@leelalu.com and tell us what you were trying to do, what device and assistive technology you used, and where it failed. The team reads every email and replies within two business days.

Want to help us test with your setup once cohorts open?

Join Founding Families

A tired parent at 3 a.m. is our baseline user.