Accessibility Statement

We design to WCAG 2.2 Level AA. In practice that means text and interface colours that meet contrast minimums in both the light and dark themes, controls you can reach and operate with a keyboard, visible focus, form fields with labels, and text that stays readable when you zoom or enlarge it.

Automated checks in our build catch a part of this (for example, colour tokens, minimum text size and nested interactive controls). Automated checks do not find everything, so we also test by hand and fix what people report.

We know of the following gaps. We are working on them in the order that affects the most people.

• Charts. Some charts convey their message visually and do not yet have a complete text description or a data-table alternative on the page. The same figures are available as structured data through the API, the Python SDK and the MCP server.
• Dense data tables. Wide financial tables can need horizontal scrolling on small screens or at high zoom, and some are hard to move through with a screen reader because of their number of columns.
• The Workspace. The Workspace (chat, reports, agents and signals) is a complex application. Some interactions, such as drag-based reordering, live-updating areas, the report editor and the agent builder, have not been fully tested with every screen reader and may need more keystrokes than they should.
• Generated and exported files. Reports, spreadsheets and documents that you or an agent generate and download (for example Excel and Word files) are not guaranteed to be accessible.
• Third-party components. Sign-in with Google or LinkedIn, the Cloudflare Turnstile bot check and Stripe Checkout are provided by other companies. We choose providers that support accessibility, but we do not control their pages.
• Content from public filings. Text taken from SEC filings is shown as filed. Tables and formatting inside a filing may not be accessible, and we link to the original document for that reason.

We build for current versions of Chrome, Firefox, Safari and Edge, on desktop and mobile. The site does not depend on any particular screen reader. We have not yet published a tested-combination matrix.

If something on Valuein is hard or impossible for you to use, please tell us. Email support@valuein.biz with the subject "Accessibility", the page address, what you were trying to do, and the browser and assistive technology you use if you know it. You do not need to explain more than that.

We aim to reply within 5 business days. If the barrier stops you from using something you need, we will say what we can do in the meantime, such as sending the information in another format. We keep a list of reports and fix them by how much they get in people's way.

We review this statement when we ship a large change to the site or the Workspace, and at least every year. The date at the top shows when it was last updated.