• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

javascript text to speech(Screen Reader) api

 
Ranch Hand
Posts: 98
Angular Framework Chrome Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi

can any one tell jQuery or javascript api to read html element text as speech..

i found some example via google it requires2mb file it makes webpages slow..

is there any new thing added in HTML 5 for speech

please help find solutio..?
 
author & internet detective
Posts: 41860
908
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
2MB doesn't sound like a lot for a text to speech reader. It's a complex requirement. You should only be loading it once. And you can do it in the background. That said, I wouldn't want a webpage loading 2MB unless I was actually planning to use the feature. And if I was planning to use the feature, I probably already have something that does this. Jaws is a standalone text to speech reader. Fangs is a Firefox plugin for the same. I believe Chrome has something similar.

Can you elaborate more on your use case? If it is for people who aren't blind/vision impaired, maybe have a link to the page that does the reading warning people it will be slow. You can even tell them based on their bandwidth how long it will take.
 
Dinesh Kumar Ramakrishnan
Ranch Hand
Posts: 98
Angular Framework Chrome Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Jeanne Boyarsky wrote:2MB doesn't sound like a lot for a text to speech reader. It's a complex requirement. You should only be loading it once. And you can do it in the background. That said, I wouldn't want a webpage loading 2MB unless I was actually planning to use the feature. And if I was planning to use the feature, I probably already have something that does this. Jaws is a standalone text to speech reader. Fangs is a Firefox plugin for the same. I believe Chrome has something similar.

Can you elaborate more on your use case? If it is for people who aren't blind/vision impaired, maybe have a link to the page that does the reading warning people it will be slow. You can even tell them based on their bandwidth how long it will take.



Yes we are developing application for physically challenged/blind peoples as academic project. we need only reading plain text as speech not a navigation link.i tried fangs screen reader but not sure it can trigger with javascipt..
 
Sheriff
Posts: 67746
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I believe that Jeanne's point is that you shouldn't be triggering it at all. Let the user trigger it with his or her own tools. Just follow the W3C guidelines for accessibility, to make sure that screen readers can do their job, and let the user's screen reader handle the rest. Why are you trying to intervene in that process which will likely just make things harder for readers?
 
Jeanne Boyarsky
author & internet detective
Posts: 41860
908
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Bear Bibeault wrote: Why are you trying to intervene in that process which will likely just make things harder for readers?


Exactly. ANd you are making it much harder. Your target audience already has a screenreader going all the time. Adding more sound to that will result in them not being able to hear either clearly.
 
Dinesh Kumar Ramakrishnan
Ranch Hand
Posts: 98
Angular Framework Chrome Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for your reply Bear Bibeault & Jeanne Boyarsky
actually we are making web application it can be used in any system so it's not possible to have screen readers in all system..
 
author
Posts: 297
5
Android Firefox Browser Fedora
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Why is it not possible to have screen readers in all systems? Screen readers are not browser add-ons, they are operating system add-ons, what operating systems are you targeting? In addition to the ones Jeanne mentioned, NVDA is a free screen reader for Windows, and Orca is a free screen reader for Linux systems. I understand that MacOS, iOS and Android have built in screen readers too, though I haven't tried them myself.
 
Jeanne Boyarsky
author & internet detective
Posts: 41860
908
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Dinesh Kumar Yadav wrote:Thanks for your reply Bear Bibeault & Jeanne Boyarsky
actually we are making web application it can be used in any system so it's not possible to have screen readers in all system..


That's not how accessibility works. Someone who is blind or vision impaired already has a screenreader that he/she uses daily. Your website shouldn't be duplicating that function. That's like saying your website should provide the ability to shut down your computer. It's not the website's job. It's the job of the computer (or software in this case.)

What is your job is making sure that the site will read well with a screenreader. WAI (WCAG) and Section 508 provide guidance in how to do this. For example, always use <label> tags for form elements.
 
Dinesh Kumar Ramakrishnan
Ranch Hand
Posts: 98
Angular Framework Chrome Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thank you Jeanne Boyarsky for your reply..

i go with screen reader for my problem..
 
Stop it! You're embarassing me! And you are embarrassing this tiny ad!
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic