Accessibility

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 a richer accessibility behavior than the web equivalent, we follow the platform’s stronger pattern.

That target is a target, not a certificate. What backs it day to day is the checking described below: some of it automatic and run on every change, some of it manual and done by a person when a surface changes. This page separates the two, because the difference matters to anyone deciding whether to trust it.

What works today

• Every change is scanned before it ships. An automated accessibility scan runs against the site’s pages in our build pipeline, at both desktop and phone widths and in both light and dark themes. A failure blocks the release.
• Color contrast is tested, not asserted. The color tokens this site is built from are checked by an automated test against the WCAG contrast ratios: 4.5:1 for body text, 3:1 for large text and for the non-text parts of interactive components. Both themes are covered by the same test. The app is designed to the same targets.
• Everything is reachable by keyboard, and you can see where you are. Every interactive element on the site is operable by keyboard and carries a visible focus ring, including quiet inline links.
• Images carry real alt text. Product screenshots and illustrations have descriptive alternative text written for them. Decorative images are marked as decorative so screen readers skip them.
• The one form on this site announces itself. The waitlist form has a programmatic label, and its result, success or failure, is announced rather than shown only in color.
• Motion respects your setting. Every animation on the site checks the reduced-motion preference. When you ask for less motion, the ambient movement stops rather than merely slowing down.
• Long-form content is structured content. Legal documents, help articles, and this page are real headings, lists, and tables, with a table of contents built from the headings on every screen size.

Known gaps

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

• Screen-reader testing is manual and occasional. We check flows with the screen readers built into iOS and Android when a surface changes materially, not on a fixed schedule and not before every release. We would rather say that plainly than promise a cadence we do not hold to.
• No end-to-end screen-reader audit of the long-form pages. The help articles, the legal documents, and this page have not been walked start to finish with a screen reader. Automated scanning covers a great deal, but it is not the same thing, and we have not done the walk yet.
• The bank connection screen is not ours. The screen where you sign in to your bank is rendered by the connection provider inside our app. We follow their accessibility documentation, but we cannot fix issues inside that screen.

When we find a gap, it goes on this list and a fix goes on a reasonable release. When one closes, it comes off, and the date at the top of this page moves.

Tell us when something is broken

If anything about Lefover is hard to use because of an accessibility barrier, tell us. A specific report (“the focus ring disappears on the pricing table at this width”) is worth more to us than a general one, but send whichever you have.

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