Community Wishlist Survey 2022/Larger suggestions/Spoken Articles
This proposal is a larger suggestion that is out of scope for the Community Tech team. Participants are welcome to vote on it, but please note that regardless of popularity, there is no guarantee this proposal will be implemented. Supporting the idea helps communicate its urgency to the broader movement. |
Spoken Articles
- Problem: Projects to make Wikimedia articles spoken have not gone ahead and/or the number of audios compared to the number of articles is negligible. This is caused by two reasons: Few editors know how to make these audios and over time these audios become outdated by the edits made.
- Proposed solution: One of the possible ways to expand and improve this idea is to make software that reads (with pre-established rules) the text of articles in all Wikimedia projects in all languages automatically, allowing people to choose to listen or read, observe misspellings more easily to correct them, learn the pronunciation of words and the visually impaired can benefit from this.
- Who would benefit:
- More comments: You might find interesting pronunciation lexicons for XHTML and SSML attributes in XHTML. There could be wiki syntax, possibly templates, for listing pronunciations which could be aggregated into pronunciation lexicon resources referenced with document metadata. There could also be one or more wiki templates for rendering XHTML spans with SSML attributes. As for which document content to synthesize, this could also be done using cascading stylesheets using the CSS Speech Module, specifically the
speak
property. (AdamSobieski idea) - Phabricator tickets:
- Proposer: N4CH77 (talk) 18:56, 10 January 2022 (UTC)
Discussion
Agree I think this would be a great idea. This would surely help out those with visual impairments. Although they have TTS, these can often mess up the formatting and read unnecessary information (such as citations) in a way that would confuse a listener. Perhaps before software is made, users can upload audio of them just reading articles? Jmaxx37, 02:10, 11 January 2022 (UTC)
- Spoken Wikipedia exists for just this purpose currently. Agree that automation would be great if possible. Retswerb (talk) 05:11, 11 January 2022 (UTC)
- Automated text reader option would be nice, like press a button and the page is converted to audio on the fly. You would need a way to skip sections and return to the ToC. Would be heavy on bandwidth compared to text, but light compared to video. Great for use when driving. · · · Peter (Southwood) (talk): 07:32, 11 January 2022 (UTC)
- That was exactly my idea of what the features would look like =) —N4CH77 (talk) 21:07, 11 January 2022 (UTC)
Are you aware of Wikimedia Sverige's Wikispeech project? Jon Harald Søby (talk) 10:01, 11 January 2022 (UTC)
- Yes, I'm aware. But this project only has 4 languages available and even with a page explaining it, I didn't understand how to download it. (sorry)
Maybe if I get more stuff it can be used to read the text automatically. --N4CH77 (talk) 12:11, 11 January 2022 (UTC)
- Browsers have an entire Speech synthesis api these days.. Why are we not using that ? Seems simpler/more durable. Also, I can just select a page in my browser and have the browser read it to me. Been an option for about 8 years now I think. On my phone i can select text and choose "speak". Rebuilding things that the OS or browser can already do is generally a bad idea, we are NOT better at it than Apple or Google. —TheDJ (talk • contribs) 12:44, 11 January 2022 (UTC)
- At least, for me, these browsers don't work the right way (Reading unnecessary parts, wrong pronunciation, reading in a disordered way and in quotes and in images they don't say what it is, it only reads the text below thus harming readers and the visually impaired). I don't know what a new software idea that reads with pre-established rules and correctly has to "bad" and at no time did I say that you are better than Apple or Google (and why this is taken into question ¯\_( ツ)_/¯) --N4CH77 (talk) 15:55, 11 January 2022 (UTC)
- This could probably be written reasonably well for languages like Spanish, where any spelling has precisely one way it could be pronounced. Writing it for languages like English, where there are a lot of exceptions, would be much more difficult, and writing it for languages like Hebrew, where vowels are frequently omitted, is probably impossible. Animal lover 666 (talk) 19:47, 11 January 2022 (UTC)
- It doesn't have to be done all at once (especially since I know it will take time to program these languages) and the pronunciation doesn't have to be THE MOST PERFECT in the world, it just needs to be understandable —N4CH77 (talk) 20:38, 11 January 2022 (UTC)
- I still think that this would be impossible for languages like Hebrew and Arabic (although simple for Yidish, which has a 1:1 correspondence for words which aren't from Hebrew or Aramaic) and very difficult for languages like English and French. Animal lover 666 (talk) 09:23, 12 January 2022 (UTC)
- Text to speech engines do the work. Most of the time they work fine. Just copy any paragraph into Google Translate and click the Play button to listen to how they pronounce it. It is indeed troublesome for languages like Japanese where a single words have multiple possible and distinct pronunciation depending on context, but most modern text to speech engine have reasonable accuracy rate at guessing which pronunciation to use, according to my understanding. And they would work much better than anything developing from new by the community tech team. C933103 (talk) 00:24, 16 January 2022 (UTC)
- I still think that this would be impossible for languages like Hebrew and Arabic (although simple for Yidish, which has a 1:1 correspondence for words which aren't from Hebrew or Aramaic) and very difficult for languages like English and French. Animal lover 666 (talk) 09:23, 12 January 2022 (UTC)
- It doesn't have to be done all at once (especially since I know it will take time to program these languages) and the pronunciation doesn't have to be THE MOST PERFECT in the world, it just needs to be understandable —N4CH77 (talk) 20:38, 11 January 2022 (UTC)
- The reading incorrect parts thing and the wrong order thing can probably be improved by improving accessibility of Wikipedia's website, allowing the website to properly tell the browser which parts should they read. And I think it would also be much easier to done and have much higher chance to accomplish than creating an entirely new software just to read Wikipedia. C933103 (talk) 00:30, 16 January 2022 (UTC)
- I agree, it's much simpler to do and would improve screen reading without much effort. —N4CH77 (talk) 19:21, 16 January 2022 (UTC)
- This could probably be written reasonably well for languages like Spanish, where any spelling has precisely one way it could be pronounced. Writing it for languages like English, where there are a lot of exceptions, would be much more difficult, and writing it for languages like Hebrew, where vowels are frequently omitted, is probably impossible. Animal lover 666 (talk) 19:47, 11 January 2022 (UTC)
- At least, for me, these browsers don't work the right way (Reading unnecessary parts, wrong pronunciation, reading in a disordered way and in quotes and in images they don't say what it is, it only reads the text below thus harming readers and the visually impaired). I don't know what a new software idea that reads with pre-established rules and correctly has to "bad" and at no time did I say that you are better than Apple or Google (and why this is taken into question ¯\_( ツ)_/¯) --N4CH77 (talk) 15:55, 11 January 2022 (UTC)
- This should probably be in the Multimedia and Commons category. --Izno (talk) 22:48, 18 January 2022 (UTC)
- Hello and thanks for taking the time to write this proposal. The needed support of voice media to include and disseminate more knowledge makes complete sense. However, we reviewed this proposal as a team and have determined that this is out of scope for our team due to the nature of its technical complexity but an idea that's valid nonetheless. I am therefore moving it to the Larger Suggestions Category. There, it will still allow folks to show support and help the Community Tech team communicate how the community perceives this need to the leadership at WMF. Thanks again. Regards, NRodriguez (WMF) (talk) 15:28, 28 January 2022 (UTC)
Voting
- Support So text to speech? Rzzor (talk) 19:58, 28 January 2022 (UTC)
- Support Hanif Al Husaini (talk) 01:58, 29 January 2022 (UTC)
- Support A big task, it seems, but important for accessibility. {{u|Sdkb}} talk 04:33, 29 January 2022 (UTC)
- Support THainaut (talk) 11:00, 29 January 2022 (UTC)
- Support EDITHIDEC (talk) 14:23, 29 January 2022 (UTC)
- Support Aca (talk) 16:25, 29 January 2022 (UTC)
- Support —— Eric Liu(Talk) 18:42, 29 January 2022 (UTC)
- Support Javiermes (talk) 21:54, 29 January 2022 (UTC)
- Support Libcub (talk) 01:51, 31 January 2022 (UTC)
- Support Bluerasberry (talk) 17:32, 31 January 2022 (UTC)
- Support -- Ulanwp (talk) 10:58, 1 February 2022 (UTC)
- Support--Mravlja Matjaz (talk) 21:26, 1 February 2022 (UTC)
- Support I think it would be really interesting to have an easy way to speak the pages, regardless of operating systems or browser support, so work in that area looks useful.
If we look at https://en.wikipedia.org/wiki/Canada, there is a spoken version, but https://en.wikipedia.org/wiki/Wikipedia has no spoken version nor alternatives (like a generated spoken version). And even with the Canada article you have to already know that it can be spoken and click on a tiny icon, so there is room for improvement. Having that feature work for both people with and without visual impairment is important as the later could help promoting that feature and also enable more people to use Wikipedia in general (you could for instance listen to Wikipedia while doing other things, or some people might not find it great to read an article on the tiny screen of a smartphone, or might have issues with screens, etc). GNUtoo (talk) 21:41, 1 February 2022 (UTC)
- Oppose crucially the proposal doesn’t say who would benefit. Is the proposal assuming a need that doesn’t exist? For example do the visually impaired already have screen readers that do this for them? Siri certainly makes a good attempt at reading anything you point it at. Unless the need is clarified with would probably be better placed in making content more accessible to third party screen reading technology. Lineslarge (talk) 17:27, 2 February 2022 (UTC)
- Support WikiAviator (talk) 16:11, 3 February 2022 (UTC)
- Oppose Screen reader software already exists and is routinely used by blind people. It would be pointless to try to replicate that just for use on Wikipedia. However, if there is no semantic markup on Wikipedia that allows people using screen readers to easily navigate, that should be added. Silver hr (talk) 20:57, 3 February 2022 (UTC)
- Support Sir Proxima Centauri (talk) 07:55, 5 February 2022 (UTC)
- Support Probably mostly useless for blind people, which AFAIK already have their preferred software for such things, but quite useful for everyone that would like to know about a subject without using the eyes - while traveling, at the beach, while relaxing, whatever. - Darwin Ahoy! 14:02, 5 February 2022 (UTC)
- Support Thingofme (talk) 15:05, 5 February 2022 (UTC)
- Support --Ciao • Bestoernesto • ✉ 20:26, 6 February 2022 (UTC)
- Support Gaurav (talk) 03:17, 11 February 2022 (UTC)