Leadr Labs, Inc. wants LEADR to be usable by as many people as possible, including people who use assistive technology such as a screen reader, screen magnification, voice control, or keyboard-only navigation.
We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA across LEADR. Some parts of LEADR are delivered by third-party providers — for example account sign-in, checkout, and brokerage connection — and we do not control their code. Where one of those creates a barrier for you, we will raise it with the provider and, in the meantime, help you complete the same task another way (see "Reporting a Problem" below).
This is a target we build toward, not a certification: LEADR has not undergone a formal third-party accessibility audit. We would rather tell you that plainly than claim a compliance level we haven't verified.
LEADR is a data-dense financial terminal — dense tables, live charts, and multi-series visualizations are core to the product, and they're genuinely harder to make fully accessible than a simple page. We haven't finished that work, and we're not going to pretend otherwise. Some of what you'll find in LEADR is also delivered by third-party providers whose code we don't control. What we improve next is driven by the reports we get — see below.
If you encounter an accessibility barrier anywhere in LEADR, tell us — specifics help most (what page, what you were trying to do, what assistive technology you were using). Email hello@leadrlabs.com with the subject line "Accessibility."
If an accessibility barrier is preventing you from completing something in LEADR — creating an account, subscribing, connecting a brokerage account, or reading the data on a page — tell us and we will help you complete it another way where reasonably feasible: for example, walking you through it directly or providing the same information in an alternative format, at no extra cost to you. This commitment is made subject to, and does not create any obligation broader than, the liability terms in our Terms of Service (Sections 13 and 22).
We monitor this address and respond to accessibility reports as quickly as we can.
We'll update the effective date above when we make a material change to our accessibility target or practices.