Legal

ADA Disclaimer & Accessibility Statement

Veridian BI is committed to making our financial intelligence platform usable by everyone, including people with disabilities.

Last updated: September 18, 2026

1. Our commitment

Veridian BI believes that financial clarity should be available to every business owner, regardless of ability. We are working to ensure that our website and platform — including veridianbi.com and start.veridianbi.com — are accessible to people with visual, auditory, motor, and cognitive disabilities.

Accessibility is an ongoing effort rather than a one-time project. As we add features and update our reporting tools, we continue to review and improve how those features work with assistive technology.

2. Conformance status

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. We use WCAG 2.1 Level AA as our design and development target.

Veridian BI is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means that some parts of the content do not yet fully conform to the accessibility standard. We have not obtained a third-party accessibility certification or independent audit, and we do not claim that every page or feature currently meets every Level AA success criterion.

We publish this statement so that our actual status is clear, and so that anyone who encounters a barrier knows how to reach us and what to expect.

3. Measures we take

Steps we take to keep accessibility part of how we build Veridian BI:

  • Using semantic HTML structure, page landmarks, and a logical heading order so screen readers can navigate our pages.
  • Providing text alternatives for meaningful images, and marking decorative graphics so assistive technology can skip them.
  • Designing text and interface colors with contrast in mind against our dark and light themes.
  • Honoring the operating system's Reduce Motion setting, so animated backgrounds, typewriter effects, and transitions are disabled for users who request reduced motion.
  • Supporting keyboard navigation, with a visible focus indicator and a "skip to main content" link.
  • Building responsive layouts that remain usable when zoomed or viewed on small screens.
  • Considering accessibility when we review new features and page changes.

4. Known limitations

Despite our efforts, some limitations remain. Below is a list of known issues, along with what we are doing about them. If you encounter something not listed here, please tell us — see Feedback.

  • Dense financial tables and charts. Some report visualizations convey information primarily through layout and color. We are working to pair every figure with a clear text equivalent.
  • Interactive dashboard controls. Certain dashboard inputs and toggles may not yet expose complete labels or state information to screen readers.
  • PDF and printed report output. Reports exported or printed from the platform may not carry full tagging and reading-order information.
  • Older archived content. Pages and materials published earlier may not meet our current standards until they are revised.

5. Third-party content and integrations

Veridian BI connects to outside financial services, including QuickBooks, Xero, and Stripe. When you connect an account, part of that process takes place on screens hosted and controlled by those providers.

We do not control the design, code, or accessibility of third-party screens, embedded content, or external websites we link to, and we cannot guarantee their conformance with any accessibility standard. If a third-party step prevents you from completing something on Veridian BI, contact us and we will help you complete it another way.

6. AI-generated report content

Veridian BI reports are generated with AI and are provided for informational and planning purposes only. Figures are estimates based on the data you enter or connect. Our reports do not constitute financial, legal, accounting, tax, or investment advice, and you should consult a licensed professional before making material business decisions.

Because this content is generated for each request, its structure can vary between reports. We aim to keep generated output readable with assistive technology, and we treat any report that cannot be read by a screen reader as a defect worth reporting to us.

7. Requesting assistance or an accessible alternative

If any part of Veridian BI is not accessible to you, we will work with you to provide the information or complete the task in another way, at no additional cost. That may include walking you through a connection step, providing report contents in an alternative format, or assisting with account and billing actions directly.

To request help, email veridianbi@gmail.com. It helps if you can tell us the page or feature involved, the assistive technology and browser you use, and what you were trying to do.

8. Feedback and how we respond

We welcome your feedback on the accessibility of Veridian BI. Reports of barriers are one of the main ways we find and fix them.

Contact: veridianbi@gmail.com

We aim to acknowledge accessibility feedback within one business day, and to respond with a substantive answer or a plan within five business days. If an issue will take longer to resolve, we will tell you what we are doing in the meantime and offer an alternative way to get what you need.

9. Disclaimer

This statement describes our accessibility goals, the measures we take, and the limitations we currently know about. It is provided for informational purposes and is not a warranty, guarantee, or certification that the website or platform conforms to WCAG 2.1 Level AA, the Americans with Disabilities Act, or any other accessibility standard, law, or regulation.

We make no representation that every page, feature, or piece of generated content is free of accessibility barriers, and accessibility may vary by browser, device, and assistive technology. Nothing in this statement creates any right or cause of action against Veridian BI, nor does it constitute legal advice.

We may update this statement as the platform changes. The date at the top reflects the most recent revision.

Ran into a barrier?

Tell us what happened and we will help you get what you need another way — and fix the underlying issue.