Lefover Join the waitlist

Accessibility

Built to be used by everyone.

We aim for WCAG 2.2 AA across the app and the website. Here's what that means, where we are, and how to tell us when we fall short.

Last updated · May 2026

Standards we follow.

Lefover targets Web Content Accessibility Guidelines (WCAG) 2.2, level AA, for the website and the in-app surfaces. Where iOS or Android offer richer accessibility behaviors than the web equivalent, we follow the platform's stronger pattern.

We design with color contrast, semantic structure, keyboard and screen-reader operability, and reduced-motion respect in mind from the start. We don't bolt accessibility on at the end.

What works today.

  • Every page is navigable by keyboard with visible focus states.
  • Color contrast meets 4.5:1 for body text and 3:1 for large text and interactive components.
  • Every image and product illustration has descriptive alt text. Decorative images are marked as such.
  • Forms have programmatic labels; errors are announced with aria-live regions.
  • Light and dark modes both meet the contrast targets. System preference is detected and respected.
  • Animation honors prefers-reduced-motion. The cycle bar drift and other ambient motion stop when you ask for less motion.
  • The mobile app supports Dynamic Type on iOS and large-text settings on Android.
  • Voice-over and TalkBack flows are tested on the highest-traffic mobile screens before each release.

Known gaps.

We try to be honest about where we fall short, because pretending we are perfect helps nobody.

  • Some long-form content on the marketing site has not yet been screen-reader audited end-to-end.
  • A few interactive components on the admin dashboard rely on hover-only affordances that we are migrating to keyboard-equivalent patterns.
  • The screen where you connect your bank is rendered by a third-party provider. We follow their accessibility documentation but cannot fix issues in that screen directly.

When we discover a gap, we add it to this list and put a fix on the next reasonable release.

Tell us when something is broken.

If anything about Lefover is hard to use because of an accessibility barrier, please tell us. We will respond within five business days with either a fix, a workaround, or an honest timeline.

Write to [email protected], or use the in-app support flow and mention accessibility in the topic line. We read every message.

Visit the help center