You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm thinking of integrating speech synthesis functionality in https://ilovedotnet.org and would like to understand if this API has functionality to speak contents of current component. Or I have figure out a way to parse all the text inside the current component and pass it to this API to speak? Your thoughts on this please..
The text was updated successfully, but these errors were encountered:
The browser's speech API wrapped by this package doesn't have the functionality to read aloud the contents of the current page. It is more simple and primitive. The speech API can only speak up an utterance object that passed into its argument, consisting of a simple string and some hint information such as pitch or volume.
So, if you want to add a functionality speaking up the ilovedotnet.org contents with this package, you have to figure out a way to parse all the text inside the current component and pass it to this API to speak.
By the way, modern web browsers have built-in "Read aloud" or "Reader View mode" functions. For example, the Microsoft Edge browser allows us to enter "Read Aloud" mode with the Ctrl+Shift+U keyboard shortcut. Microsoft Edge and Mozilla Firefox enter the "Reader View" mode when a user hits the F9 key if the current page is ready for Reader View mode. In the reader view mode of Firefox, when a user enters the N key, it speaks up the page.
So, it might be better to consider to optimize ilovedotnet.org for "Reader View" and W3C accessibility.
Hi @jsakamoto ,
I'm thinking of integrating speech synthesis functionality in https://ilovedotnet.org and would like to understand if this API has functionality to speak contents of current component. Or I have figure out a way to parse all the text inside the current component and pass it to this API to speak? Your thoughts on this please..
The text was updated successfully, but these errors were encountered: