Recently, after I updated my Edge browser, I discovered some speech-to-text extensions were unable to recognize my voice. Through my research, I found that the reason could be due to an API called SpeechRecognition. In Chrome, the speech-to-text API used to be called 'webkitSpeechRecognition', but Edge doesn't support this API.

However, in a recent update to Edge, the SpeechRecognition API became invalid for some reasons I don't know.I tried and find that I cannot use any other likely speech-to-text services on other websites while using Edge but they work in Chrome.

In the morning, I wrote a web page to test this interface and successfully reproduced this error. Can you please let me know if it's my problem or do I need to wait for the official fix from Edge?

When I click "stop", there is no output on the webpage. When I try to recognize for the second time, it will output: "
Uncaught DOMException: Failed to execute 'start' on 'SpeechRecognition': recognition has already started.
    at HTMLButtonElement.<anonymous> (file:///E:/Project/talk-to-chatgpt/chrome-extension/test.html:26:25)
I have enabled the Experimental JavaScript in the experimental web platform feature.
												
This link https://mdn.github.io/dom-examples/web-speech-api/speech-color-changer/  is a speech recognition demo from MDN Web Speech API documentation (https://developer.mozilla.org/en-US/docs/Web/API/Web_Speech_API/Using_the_Web_Speech_API). It shows that Speech Recognition is not working on edge with an error message "language-not-supported".
I remember edge used to support speech recognition. I hope Edge fix the issue soon.
More info. The above statement of Speech recognition not working is for the Edge Browser I downloaded on March 30th 2023 on a Mac Air (M1) laptop. When I tried old version of Edge on my PC the Speech recognition still works.
						
Hi @Hilbrand Valham  ,
Normally, webkitSpeechRecognition should work in Edge as well because in this doc it says Edge is "Implemented with the vendor prefix: webkit". 
Judging from the error message, it is caused by multiple "start" event triggered by button click as mentioned in your question. It can just possibly be the network issue which caused the first attempt failure. You can also provide a minimal code example that can help us reproduce this issue if possible.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 
Best Regards,
Shijie Li