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 am totally blind, and I use the NVDA Screen Reader as my default Screen Reader.
As things stand right now, we the blind must be content with old and outdated speech synthesizers.
Why is this so?
Developers of new and better quality speech don't seem to understand that we need our Screen Readers to voice everything that is on any computer screen.
In order for NVDA to use ElevenLabs voices to read a book, or even a newspaper article would require us to pay money to convert text to speech on line, and even then we wouldn't have the voice read everything that is on our computer screens to us.
I know you guys are acquinted with the NVDA Screen Reader, and you have an idea as to just how it works.
Why not consider developing an add-on for NVDA?
The voice driver could be free, and a small fee could be charged for the voices we would like.
Say $25.00 each?
The text was updated successfully, but these errors were encountered:
all,
I am totally blind, and I use the NVDA Screen Reader as my default Screen Reader.
As things stand right now, we the blind must be content with old and outdated speech synthesizers.
Why is this so?
Developers of new and better quality speech don't seem to understand that we need our Screen Readers to voice everything that is on any computer screen.
In order for NVDA to use ElevenLabs voices to read a book, or even a newspaper article would require us to pay money to convert text to speech on line, and even then we wouldn't have the voice read everything that is on our computer screens to us.
I know you guys are acquinted with the NVDA Screen Reader, and you have an idea as to just how it works.
Why not consider developing an add-on for NVDA?
The voice driver could be free, and a small fee could be charged for the voices we would like.
Say $25.00 each?
The text was updated successfully, but these errors were encountered: