Accessibility statement

Last updated: 29 October 2026

Onda Dev wants Trovaso to work for everyone, including people who use a keyboard instead of a mouse, a screen reader, zoom, or a phone. This statement says what we aim at, what is in place, what we know is not right yet, and how to tell us when something is in your way.

1. What we aim at

We aim at WCAG 2.1 level AA for the website (trovaso.com), the app, and the pages creators see when they sign a contract or confirm a payment. Today Trovaso is partially conformant: most of it meets level AA, and the parts that do not are listed in section 3.

2. What is done

• Keyboard: everything you can click you can reach with Tab and use with Enter or Space, in a sensible order, and the focused control shows a visible outline.
• Labels: form fields have labels, icon-only buttons have a text alternative, and images that carry meaning have a description.
• Colour and contrast: text and controls use a set of colour tokens chosen for AA contrast, in light and dark mode, and colour is never the only signal — a status pill also says its status.
• Motion: animations and the looping product clips respect the “reduce motion” setting of your system.
• Phones and zoom: every screen reflows to phone width without horizontal scrolling, and the pages stay usable at 200% zoom.
• Structure: pages declare their language, use headings in order, and work with the browser back and forward buttons as you would expect.

3. Known limitations

• Data tables on small screens: on a phone, the roster, results and payments tables turn into stacked rows, and some column names are then not announced by a screen reader. On a desktop the full table, with its headers, is available.
• Third-party parts: Stripe's checkout and billing portal, Google's reCAPTCHA and the video players of TikTok, Instagram and YouTube are built by those companies; we cannot change how accessible they are.
• PDF contracts and payment confirmations: the PDFs Trovaso generates are not tagged, so a screen reader may not read their structure. The same content is on the signing or confirmation page as accessible HTML, and we can provide a tagged copy on request.
• Charts: some charts in Results and Revenue have no text alternative yet; the figures they show also appear as numbers on the same page.
• AI assistants: the Trovaso cards shown inside ChatGPT or Claude run in those apps, so part of their accessibility depends on the assistant you use.

4. How we check

We go through new screens with the keyboard only, at 200% zoom, on a phone and with reduced motion on before they ship, and we fix what people report. This statement is reviewed when the product changes and at least once a year.

5. Tell us what is in your way

If something in Trovaso is hard or impossible for you to use, email team@trovaso.com with the page, what you were trying to do, and the browser or assistive technology you use. We answer within 10 business days, with a fix or a way around the problem in the meantime.

6. Changes

We update this statement as limitations are fixed or found. The date at the top says when.

Contact

Onda Dev · team@trovaso.com