Browse the docs

Voice

Voice simulations on iPhone and iPad

On iPhone and iPad, an embedded voice simulation can open a separate voice window so the learner can grant microphone access.

On this page

Voice simulations are built to run on iPhone and iPad. When a voice simulation is embedded inside another page, such as a course in an LMS, and the browser does not report that the embedded frame is allowed to use the microphone, the voice session opens in a separate window instead of running inside the frame. Safari on iPhone and iPad typically takes this path, and shows the window as a new tab. This is expected behavior, not a defect.

When the simulation is opened directly in its own tab rather than embedded in another page, the voice session runs in that page and no separate window opens.

How the separate voice window works

  1. The learner taps the start button in the simulation ("Tap to start").
  2. A separate voice window opens with a Start voice session button and the note "You'll be asked to allow microphone access."
  3. The learner taps Start voice session and allows microphone access. This second tap is always required in the voice window.
  4. The session connects. The learner can go back to the course tab and continue the conversation there, while the voice window stays open in the background.
  5. When the simulation ends, the voice window closes on its own. The simulation does not switch tabs for the learner, so they may need to go back to the course tab themselves.

Closing the voice window early ends the voice session.

What to tell learners

  • Tap the start button, then tap Start voice session in the window that opens, and allow microphone access.
  • Leave the voice window open until the simulation is complete. It closes automatically.
  • If the message "Please allow popups for this site to use voice mode, then try again." appears, the browser blocked the voice window. Allow pop-ups for the site and tap start again.
  • If "Microphone access was blocked" appears, allow microphone access in the browser and try again.