Accessibility Statement

1. Our commitment

We build Terano AI so that the people who use it — and the audiences our creators publish to — are not excluded by our design choices.

In practice that means native HTML semantics first, with ARIA used only where HTML has no equivalent; every interactive control reachable and operable by keyboard; a visible focus indicator wherever focus can land; colour never used as the only carrier of meaning; and motion that honours your system's reduce-motion setting.

Accessibility defects are triaged in the same queue as functional defects, at the same severity. We do not keep a separate, slower list for them.

2. The standard we measure against

We measure Terano AI against the Web Content Accessibility Guidelines (WCAG) 2.2 at conformance level AA, published by the World Wide Web Consortium. WCAG 2.2 is the current version and contains everything in WCAG 2.0 and 2.1.

The reference text is published at https://www.w3.org/TR/WCAG22/

WCAG 2.2 level AA is also the technical basis of EN 301 549, the European standard referenced by the European Accessibility Act, and it is aligned with JIS X 8341-3, the Japanese Industrial Standard for web content accessibility. We hold ourselves to one bar rather than three separate ones.

3. Conformance status

Terano AI is partially conformant with WCAG 2.2 level AA.

"Partially conformant" means most of the product meets the standard, but some parts do not. We use that term deliberately rather than claiming full conformance: at the time of writing we know of specific success criteria we do not yet meet, and they are listed in the next section.

We do not claim conformance for third-party content shown inside the product — for example video thumbnails, titles, descriptions and comments retrieved from YouTube, TikTok or Instagram, or media a creator has uploaded. We are responsible for how that content is presented, labelled and structured; we do not control the content itself.

4. Known limitations

The following parts of Terano AI are known not to meet WCAG 2.2 level AA. Each one is tracked as a defect. We list them because a statement that omits its failures is of no use to the people it is written for.

Form field borders. The border marking the edge of a text input, select or text area falls below the 3:1 contrast ratio required by success criterion 1.4.11 (Non-text Contrast), in both the light and dark themes. Fields remain correctly labelled, focusable and operable, and the focus indicator itself meets contrast; it is the resting boundary that is too faint. A fix is in progress.

Captions on video. Video played inside the product does not carry captions or a transcript track (1.2.2, 1.2.4). This affects media a creator has uploaded or imported.

The research map. The three-dimensional map on the Research screen conveys its structure visually. A partial non-visual equivalent exists — selecting a video reports the same figures as text in the detail panel — but the overall spatial arrangement is not exposed to assistive technology (1.1.1).

Small-screen reflow. We have not finished verifying that every screen reflows without two-dimensional scrolling at a 320 CSS-pixel viewport width (1.4.10). Some data-dense screens are likely to fail this today.

Text resizing. Type sizes are currently expressed in absolute units, so text does not respond to a browser's minimum-font-size preference (1.4.4). Browser and operating-system page zoom works normally and scales the whole interface as expected.

Assistive-technology testing. Our assessment so far has been code-level and automated. We have not yet completed structured manual testing with screen readers such as NVDA, JAWS, VoiceOver and TalkBack. Until that is done, this statement should be read as our best assessment rather than a verified result.

5. How we assessed this

This statement is based on a self-evaluation carried out in August 2026 by our own engineering team. It has not been reviewed by an independent third party.

The evaluation covered a criterion-by-criterion review of the application source against WCAG 2.2; computed colour-contrast measurement of every colour token in our design system, in every theme we ship; and a review of keyboard operability, focus management, page structure and dialog semantics.

Several of those checks now run automatically in our test suite, so a regression fails the build instead of reaching you. Colour contrast is one of them: every text colour is measured against the surface behind it, in each theme, on every run.

We intend to commission an independent audit and to complete structured assistive-technology testing. We will update this statement, and the date on it, when we do.

6. Compatibility

Terano AI is built for current versions of Chrome, Edge, Firefox and Safari on desktop, and Chrome and Safari on mobile. It requires JavaScript; there is no non-JavaScript fallback.

We have verified keyboard operability and page structure. We have not yet verified behaviour against specific screen-reader and browser combinations — see the final item under Known limitations.

If a particular assistive technology does not work with Terano AI, please tell us. A report naming the tool, its version and the screen you were on is the fastest route to a fix.

7. Feedback and contact

If you meet a barrier in Terano AI, or you need something we provide in a format you can use, contact us.

Email: execs@teranoai.com

Please include the page or screen, what you were trying to do, and — if you can — the browser and any assistive technology you were using.

We aim to acknowledge accessibility reports within five business days. Where a fix will take longer than that, we will tell you what we are doing and, where we can, offer another way to complete the task in the meantime.

Reporting a barrier costs nothing, and we will not ask you to identify yourself beyond giving us a way to reply.

8. If we do not put it right

If you contact us about an accessibility barrier and are not satisfied with our response:

In the European Union, the European Accessibility Act is enforced by a designated national authority in each member state. You may raise a complaint with the authority for the country you are in.

In Japan, Terano LLC is subject to the Act on the Elimination of Discrimination against Persons with Disabilities (障害者差別解消法), under which the provision of reasonable accommodation by private businesses became a legal obligation in April 2024.

In any jurisdiction, you are welcome to escalate to the company representative named in our legal notice.

9. Review and updates

This statement was prepared on 16 August 2026 and describes Terano AI as it stood on that date.

We review it whenever we ship a significant change to the interface, whenever we close one of the limitations listed above, and at least once every twelve months.

The date shown at the top of this page is the date of the most recent review, which is not necessarily the date of the most recent change to the product.