Knowledge Base

FAQ

How to use the KUDO Widget as a participant

This article will give you a brief overview of the Language Access Widget and how to select your preferred language during an event using this solution.

What is the KUDO Language Access Widget

The Language Access Widget is a language selector that can be embedded into 3^rd party platforms, such as Hopin, ON24, GlobalMeet Webcast and others.

The integration connects KUDO's Interpreter Console to these platforms, which allows the interpreters to access the event and interpret the language into the respective language channels.

The solution supports up to 32 languages per event, including spoken and sign languages.

How attendees can access interpretation via the KUDO Language Access Widget

1. Join the original event

Follow the instructions provided by the event organizer to join the meeting on the 3rd party platform, the website hosting the event.

2. Locate the KUDO Language Access Widget within the event page

If you would like the Language Selector to be displayed in a different language, click on the globe icon on the bottom of the Widget and choose from the 11 available languages. The default for the widget will be according to your browser language preference.

AR - Arabic (العربية)
DE - German (Deutsch)
EN - English (English)
ES - Spanish (Español)
FR - French (Français)
IT - Italian (Italiano)
JP - Japanese (日本語)
PT - Portuguese (Brazil) (Português)
ZH - Chinese simplified (中文(简体)

3. Choose your preferred language from the Select Language list

Follow the instructions provided by the event organizer to join the meeting on the 3rd party platform, the website hosting the event.

Watch an example of the KUDO Language Access Web Link combined with Microsoft Teams Live Event:

If your platform does not support this kind of integration, we also have a solution for you. Find out more about this Language access: Web Link here.

User Guides

Embed the KUDO Widget Beside a Livestream on Your Website

The KUDO Widget lets attendees access translated audio and captions alongside your livestream. Your video player provides the program video and original audio, while the Widget provides language selection and translation controls.

This guide is for web developers, content management system (CMS) administrators, and event producers.

Before you start

Have the KUDO Widget session URL for your event and access to edit the webpage or CMS module where the livestream will appear. Coordinate the implementation with the team responsible for your video player.

1. Add the Widget to your page

The Widget is embedded using an iframe. The following example uses a placeholder session ID:

<iframe
  name="KUDO Widget"
  title="KUDO translation and captions"
  src="https://audio-widget.kudoway.com/SESSION_ID"
  width="375"
  height="500"
  style="border: 0;"
  allowfullscreen>
</iframe>

Replace SESSION_ID with the session reference supplied for your event. If you have been given a complete Widget URL, use that URL as the src value.

The iframe contains the KUDO attendee interface. Your website or CMS controls its placement and the surrounding page design.

2. Check placement and sizing

On desktop, place the Widget beside the livestream player so attendees can watch the video while viewing captions and accessing language controls.

The example dimensions—375 pixels wide by 500 pixels high—are a starting point. Validate the final size within your page layout.

For smaller screens, consider placing the Widget below the player. Check that captions and controls remain readable and accessible without being clipped or overlapping other content.

3. Plan how attendees will hear audio

The livestream player and KUDO Widget are independent audio sources. If both play audio at the same time, attendees may hear the original speech and translated speech overlapping.

Define and test the listening experience:

For translated audio: Coordinate playback so the original player audio does not compete with the selected translation.
For original audio with translated captions: Check that attendees can retain the original player audio while using captions without additional translated audio playing.

KUDO’s Auto-Floor API can be used to coordinate muting between the player and the Widget. Adding the iframe alone does not establish that integration. Have your web team review the Auto-Floor API implementation guidance and test its behavior with your specific player.

4. Test the attendee experience

Before the live event, open the completed page and verify:

The Widget loads the correct event session.
The livestream and Widget fit the desktop and mobile layouts.
Attendees can select the available languages.
Captions display correctly and their controls remain accessible.
Translated audio plays through the intended output.
Original and translated audio behave as intended when changing languages.
Auto-Floor muting works as expected, if implemented.

Run the test with live source speech and the actual livestream player. A visual layout check alone does not verify audio behavior.

What to expect

Attendees should be able to watch your livestream and access KUDO translation within the same webpage. The surrounding layout remains controlled by your website or CMS.

Troubleshooting

Issue / Task	Possible Cause	Recommended Action
Original and translated voices overlap	Both the livestream player and Widget are playing audio	Check each audio source separately, then verify the intended muting behavior and Auto-Floor integration, if used.
Captions or controls are clipped	The iframe dimensions or surrounding layout provide insufficient space	Adjust the layout and retest at the affected screen size.
Desktop layout works but mobile is difficult to use	The page layout has not been adapted to smaller screens	Reposition or resize the Widget and verify access to captions and language controls.

Integrating with RingCentral

This guide walks through how to connect a KUDO Meeting with a RingCentral Stage or Session event so attendees can access multilingual interpretation directly from the RingCentral experience.

Audience: Hosts, Producers, Operators, AV technicians, and meeting organizers configuring multilingual interpretation workflows for RingCentral events.

Before You Start

Before configuring the integration, confirm that the KUDO meeting has already been scheduled with interpretation languages configured, the KUDO Mobile Link is available from the dashboard, and the RingCentral event has been created with the Host having access to its configuration settings.

For the best attendee experience, validate the integration before the live event, test multilingual audio playback in advance, and confirm the correct KUDO Meeting ID is entered into RingCentral. Testing the attendee access workflow before publishing the event is also strongly recommended.

Configuring the Integration

From the KUDO meeting dashboard, copy the Mobile Link URL. The 12-digit KUDO Meeting ID is embedded in this URL and is required for the RingCentral integration.
Inside RingCentral, open the webinar or event and go to the Basics section.
Scroll down to the Apps section, enable the KUDO integration, and paste the 12-digit KUDO Meeting ID into the configuration field. Click Save to apply the settings. Once saved, attendees will be able to access multilingual interpretation through the RingCentral event experience.

Known Limitations

The KUDO meeting must be scheduled and running before attendees can access interpretation. Languages should be finalized before the event begins, as AI translation quality depends on source audio quality and network stability. Integration behavior may also vary between RingCentral Stage and Session workflows.

Troubleshooting

Issue	Possible Cause	Recommended Action
KUDO integration doesn't appear in RingCentral	Integration not enabled	Verify the KUDO integration is enabled in the RingCentral Apps section
Attendees can't access interpretation	Incorrect Meeting ID	Confirm the correct 12-digit KUDO Meeting ID was entered
Multilingual audio is unavailable	KUDO meeting not started	Confirm the KUDO meeting is running before attendees join
Participants report missing languages	Languages not configured	Verify interpretation languages were set up before the meeting began
Integration changes aren't applied	Settings not saved	Reopen the Apps section and confirm settings were saved successfully

Need Help?

Implement Auto-Floor API for KUDO Widget

The KUDO Widget Auto-Floor API allows a third-party platform to automatically respond when an attendee selects a language channel inside the KUDO Widget. When interpretation is active, KUDO notifies the parent platform so it can mute or lower the original floor audio. When the attendee returns to Original Audio or interpretation is not active, KUDO sends a message to restore it. This prevents both audio streams from playing at the same time.

How It Works

When an attendee selects a language channel inside the embedded KUDO Widget, KUDO sends a floorMute message to the parent platform via JavaScript's window.postMessage() method. The platform listens for that message and mutes or lowers its original audio accordingly. When the attendee selects Original Audio or interpretation is inactive, KUDO sends the message again with a value that tells the platform to restore audio.

Before You Start

Confirm the following before implementing:

You have a KUDO client account with access to the Language Access Widget
The KUDO Widget is embedded in a supported third-party web platform
Your development team can update the parent page hosting the KUDO iframe
The iframe is embedded in a single-level hierarchy
The KUDO language access meeting is scheduled with auto-floor disabled

Implementation

Add the following listener to the parent page hosting the KUDO iframe:

window.addEventListener("message", (event) => {
  try {
    const data = JSON.parse(event.data);
    const muteFloor = data["floorMute"];
    if (muteFloor) {
      // Mute or lower the platform's original meeting audio.
    } else {
      // Unmute or restore the platform's original meeting audio.
    }
  } catch (error) {
    console.log(error);
  }
}, false);

Expected Behavior

Scenario	Expected Platform Behavior
Attendee selects a language channel and interpretation is active	Platform mutes original audio
Attendee selects a language channel but interpretation is not active	Platform restores original audio
Attendee selects Original Audio	Platform restores original audio

A Few Things to Keep in Mind

KUDO sends the floorMute message one level up to the parent window only. The third-party platform is responsible for muting, lowering, or restoring its own floor audio — KUDO does not directly control the platform's audio player. This workflow is intended for embedded Widget experiences where the platform needs to manage original audio playback automatically.