- From: Evan Liu <notifications@github.com>
- Date: Mon, 28 Apr 2025 16:59:29 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/1038/2837046998@github.com>
evanbliu left a comment (w3ctag/design-reviews#1038) Google Meet is one site that would only adopt this API if it provides a mechanism to guarantee that on-device speech recognition is used, though not for typical data residency reasons. Specifically for Google Meet, the performance of the latest on-device speech recognition language packs, in addition to biasing support, meets their stringent requirements, whereas the Open Speech API that powers the cloud implementation of the Web Speech API in Chrome does not. If on-device speech recognition is not available, Google Meet would continue to use its own cloud speech recognition implementation instead of the Web Speech API. More commonly, developers have been requesting on-device speech recognition support simply because they do not want to send audio data to Google or other speech recognition services for various reasons. Here are some examples of these requests: https://webwewant.fyi/wants/55/ https://github.com/WebAudio/web-speech-api/issues/108 https://stackoverflow.com/questions/49473369/offline-speech-recognition-in-browser https://www.reddit.com/r/html5/comments/8jtv3u/offline_voice_recognition_without_the_webspeech/ padenot@mozilla.com may have other examples of EU partners with regulatory requirements regarding this. As for receiver-side captioning in a WebRTC scenario, one primary benefit is that in a large meeting, if only one person requires captions, then only that person has to install and run on-device speech recognition. Otherwise, with sender-side captioning, every single person in the meeting would have to run on-device speech recognition. This document isn't viewable externally, but go/receiver-captions has some trade-offs for receiver-side captioning specifically for Google Meet. I'll work on updating the explainer in the next day or so with all of the changes and discussion in this thread! -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1038#issuecomment-2837046998 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1038/2837046998@github.com>
Received on Monday, 28 April 2025 23:59:33 UTC