Accessibility statement
Accessibility Statement
VINDEXAI HOLDINGS LLC (“VindexAI,” “we,” “us”) operates vindexai.io. This statement is effective 2026-08-25 and describes the accessibility target for this site, what we test today, and where the gaps still are.
Statement status
Effective 2026-08-25.
Operator and site
VINDEXAI HOLDINGS LLC (“VindexAI,” “we,” “us”) operates vindexai.io. This statement is effective 2026-08-25 and applies to that site.
Our target
We are building vindexai.io to meet WCAG 2.2 Level AA. We say target deliberately: this statement describes what we test for and how, not a claim that every page has been independently audited and certified conformant. If you hit a barrier, we want to know about it and fix it.
What we actually do today
Checks that run on every code change.
Automated scanning in continuous integration
Every code change runs automated accessibility scanning with axe-core, using the rule sets tagged for WCAG 2.0 A and AA, 2.1 A and AA, and 2.2 AA. That scan currently covers a representative set of public pages — the privacy policy and the boards, product, industry, method, and book pages — plus both conversion flows: the starting-point tool and the Request a Quote form. It does not yet run on every page. Expanding it to all public routes is on our roadmap.
Keyboard operability, verified by scripted tests
We run scripted browser tests that check specific keyboard interactions actually work: reaching the skip-to-content link and moving focus into main content, tabbing through primary navigation and opening the compact menu from the keyboard, completing the starting-point tool with the keyboard alone, focus landing on the result and returning to the first choice on reset, and focus moving to the first invalid field when a quote submission has errors. These are not generic checks; they verify the exact interactions a keyboard-only visitor relies on.
Structure on every public page
Every public page is checked by an automated browser test for exactly one page heading and for its landmark regions — banner, primary navigation, main content, and footer — which is what matters most for people who navigate by heading or landmark rather than reading top to bottom.
What we do not yet do
Stated honestly.
One browser engine
Automated scanning currently runs in Chromium only. We do not yet test against other browser engines or against real mobile assistive-technology configurations.
No manual assistive-technology testing yet
We have not yet completed manual testing with a screen reader or other assistive technology. Automated tools catch a meaningful share of accessibility issues, but not all of them. Manual testing is the next step we are planning, not something we have already done.
Contrast coverage is partial
Automated color-contrast checking covers the sanctioned brand color pairs and the pages in the automated scan set. It is not yet applied consistently to every component in every state.
Downloadable materials
The site does not currently offer downloadable files; the Move the Needle book page is an informational landing page, not a download. If and when we publish downloadable materials, we will review them for accessibility — tagging, reading order, and alt text for images — before publishing, and note their status here.
Feedback and contact
Tell us what you hit.
Report a barrier
If you encounter an accessibility barrier anywhere on this site, tell us. We want to fix it. Email info@vindexai.io with the page and a description of what happened.
What happens next
We acknowledge accessibility feedback within 5 business days.
Changes to this statement
We will update this page as our testing coverage and practices change, and update the effective date above when we do.