Accessibility Statement

This Accessibility Statement is published by the Company. The Company's full identity, address, and legal contact details appear at the bottom of this page.

> In short: we aim to make the Service usable by as many people as possible, including those who navigate by keyboard, who use a screen reader or other assistive technologies, or who have particular needs regarding contrast or readability. Our goal is to reach WCAG 2.1 Level AA. We are not there yet in every respect, we say so openly, and we are working to close the gaps with each update. If you run into a barrier, we want to know about it — contact details appear at the bottom of this page.

Table of Contents

  1. Introduction
  2. Our Commitment
  3. Measures Taken
  4. Known Limitations and Ongoing Work
  5. How to Report an Accessibility Difficulty
  6. Reference Standard

1. Introduction

This statement describes the Company's approach to digital accessibility for the Platform, which allows client organizations to deploy artificial-intelligence-based conversational agents, in both text and voice mode, to their own users. We believe that a service designed to converse with people must first be designed to be usable by all people, regardless of their abilities or the technologies they use to access the Web. This statement applies to the web interfaces of the Service operated by the Company; it does not necessarily cover content or configurations specific to each client organization, nor third-party sites or applications the Service may link to.

This statement complements our other legal documents, in particular our Privacy Policy, which describes how your personal information is handled when you interact with the Service through an assistive technology, and our Security Overview, which describes the security measures applicable to the Service as a whole.

2. Our Commitment

We aim for conformance with Level AA of the Web Content Accessibility Guidelines (WCAG) 2.1, an industry-recognized standard. This is a goal we actively pursue in the design and development of the Service, not a certification we hold or a state of conformance we claim to have fully achieved to date. To our knowledge, no formal independent accessibility audit has been conducted and published for the Platform as a whole; our internal assessments are used to guide our improvement priorities, not to attest to certified conformance.

We treat accessibility as ongoing work, built into how we design new features, rather than as a one-time after-the-fact correction exercise.

3. Measures Taken

Where reasonably possible, we seek to build the following accessibility principles into the design and development of the Service:

  • Keyboard navigation — the interface's core functions are designed to be accessible without relying exclusively on a mouse or touchscreen, including moving between interactive elements and activating controls.
  • Color contrast — we pay attention to the contrast between text and its background to facilitate reading, including for people with reduced vision or color sensitivity.
  • Semantic page structure — pages are organized using a heading hierarchy, navigation landmarks, and a logical structure intended to facilitate understanding of the content, whether visually or through an assistive technology.
  • Compatibility with common assistive technologies — we seek to ensure that interface components convey their role, state, and label in a way that remains understandable to screen readers and other common assistive tools.
  • Thoughtful component design — interactive interface elements (forms, buttons, error messages, dialog windows, including those specific to text and voice conversational exchanges) are designed with accessibility in mind from the outset, rather than added afterward.

4. Known Limitations and Ongoing Work

We are honest about the fact that some parts of the Service may, at present, not fully meet WCAG 2.1 Level AA. An evolving platform, updated frequently and incorporating relatively recent features such as voice conversational agents, inevitably has areas where accessibility has not yet reached the same level of maturity as in the more established sections of the interface. This can include, for example, voice or conversational interactions whose textual or visual equivalent is not yet fully developed, or recent components whose behavior with assistive technologies has not yet been fully validated.

We are committed to continuously improving the accessibility of the Service, to correcting known issues progressively, and to taking accessibility into account in our future development priorities. This statement will be updated as progress is made.

5. How to Report an Accessibility Difficulty

If you encounter a barrier while using the Service, or if a feature does not seem sufficiently accessible to you, we want to know. You can reach us through the contact details displayed at the bottom of this page.

We are committed to reviewing every report seriously, acknowledging receipt within a reasonable time, and assessing appropriate fixes based on the nature of the issue reported. Your feedback directly helps us guide our continuous improvement efforts.

6. Reference Standard

The reference standard used to guide our accessibility efforts is WCAG 2.1 Level AA, published by the World Wide Web Consortium (W3C). This standard is widely recognized as a best-practice benchmark for digital accessibility, and it is the standard toward which we orient our design and development choices.