Skip to content

Legal · Last updated August 20, 2026

Accessibility Statement

We are building Vibely to meet WCAG 2.2 Level AA. We are not there yet, and this page says plainly how far along we are, what we know is broken, and how to reach a person who will do something about it.

1. What this statement covers

This statement covers the Vibely marketing site and the Vibely web app, both at vibely.sh. It does not cover api.vibely.sh, which has no user interface.

It does not cover the apps you build with Vibely. Those run on subdomains of vibelyagent.com, on custom domains you connect, or as native apps you submit to the App Store and Google Play under your own developer account. See "Apps you build are yours" below.

2. The standard we are working toward

We are working toward the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That is the target we design and build against. It is not a claim that we have reached it.

3. Where we stand today: partial conformance, self-assessed

We have not had an independent accessibility audit. Nobody outside the company has tested Vibely against WCAG 2.2 AA, and we have not published a VPAT or an Accessibility Conformance Report.

So the honest status is: partially conformant, by our own assessment, with parts of the product untested. We would rather say that than publish a conformance level we cannot evidence.

4. What works today

These are things we build in deliberately and can point at in our own code:

  • A "Skip to content" link as the first focusable element on every page.
  • Interactive components — dialogs, menus, tabs, switches, sliders and the like — are built on Radix UI primitives, which handle keyboard interaction, focus trapping and ARIA roles rather than leaving them to us.
  • Animation and motion respect the prefers-reduced-motion setting in your operating system.
  • Pages are built from semantic HTML with real headings, real buttons and real links.

5. Known limitations

We list what we know is weak or untested rather than staying quiet about it:

  • No independent audit, no VPAT, no Accessibility Conformance Report. Every statement here is self-assessed.
  • Colour contrast has not been verified page by page across the whole product.
  • The build surface — the chat panel, the code view and the live preview side by side — is the least tested part of the product with a screen reader.
  • The live preview pane renders an app that the agent wrote. Its accessibility is whatever that app is, and we do not correct it.
  • Third-party surfaces we embed or redirect to — the Razorpay checkout, and the consent screens of connectors you authorise — are built by those providers and are outside our control.
  • Anything not listed under "What works today" should be read as unverified, not as passing.

6. Apps you build are yours

You are responsible for the accessibility of the apps you build and publish with Vibely, including any legal obligation that attaches to them. We do not audit generated code for accessibility, and the agent can produce markup that fails WCAG. Check it before you ship.

What the starting templates do give you: semantic HTML, and a component library built on Radix UI primitives, so dialogs, menus, form controls and navigation come with keyboard interaction, focus management and ARIA roles already wired. That is a floor, not a pass — colour choices, alt text, form labels, heading order and anything the agent writes on top are yours to check.

7. Tell us what is broken

Email [email protected] with "Accessibility" in the subject line. Tell us the page URL, what you were trying to do, what happened, and the browser and assistive technology you were using if you know them.

We will acknowledge your message within 5 business days and tell you what we plan to do and roughly when. If we decide not to fix something, we will say so and say why rather than let it go quiet.

8. Alternative formats and help getting something done

If a page of ours is unusable for you, ask and we will get you the content another way — as plain text or as an email — or walk through the task with you directly. Email [email protected] with the page URL and what you need. Same 5 business day acknowledgement.

9. What we are not claiming

We do not claim WCAG 2.2 AA conformance. We do not hold an accessibility certification, we have not been audited by a third party, and we have not published a VPAT. If any of that changes we will say so here, on the date it becomes true.

10. Contact

Questions about this statement? Email [email protected]. Vibely is operated by Mana Intelligence Private Limited, incorporated in India.

Questions about this document? Email[email protected].