Accountapprovers, antispam, bureaucrat, canmove, confirm, module, administrator (Semantic MediaWiki), curator (Semantic MediaWiki), administrator, team, widget editor
7,243
edits
Changes
m
→Why are we doing it?: Correct typo compatability to compatibility
Chrome, Edge, Safari and Opera support a form of this API currently for Speech-to-text, which means sites that rely on it work in those browsers, but not in Firefox. As speech input becomes more prevalent, it helps developers to have a consistent way to implement it on the web. It helps users because they will be able to take advantage of speech-enabled web experiences on any browser they choose. We can also offer a more private speech experience, as we do not keep identifiable information along with users’ audio recordings.
If nothing else, our lack of support for voice experiences is a web compatability compatibility issue that will only become more of a handicap as voice becomes more prevalent on the web. We’ve therefore included the work needed to start closing this gap among our 2019 OKRs for Firefox, beginning with providing WebSpeech API support in Firefox Nightly.
===== What does it do? =====
