Re: Read-all problem with a website
I don't know what is causing the problems. Try a different synthesizer. I don't know what voices are available to you but you should be able to test with e-speak. If you want to hear the article read by the same voice you are using, try selecting the page once its loaded, control a, then copying it to the clipboard.toggle quoted messageShow quoted text
Open Notepad and paste it in. Search for the beginning of the article, or for the title, something you know is there and that will be easy to find. You can probably just search for two, three, or maybe four words of the title or the first sentence. In this case, I just searched for the words a question.
You shouldn't have any problems reading in Notepad.
From: Giles Turnbull
Sent: Wednesday, July 08, 2020 5:01 AM
Subject: [nvda] Read-all problem with a website
I subscribe to a regular email called Pulse, Writings from the world of Medicine. Their emails have recently changed so that you get to read the first paragraph and then have to visit a website to read the rest of the article.
I find that this website doesn't work very smoothly with NVDA using the Read All method, and I'm wondering if other people have the same result.
so you can hear what I hear, I recorded the first few paragraphs and the mp3 file is saved on my website space. What you'll hear is that the end few words of a paragraph get repeated at the start of the next paragraph, and sometimes good chunks of a sentence don't get spoken at all (the text not being spoken isn't quite so evident in the mp3 extract, but it was very noticeable further down the article). This is the link to my mp3 extract:
And this is the link to the actual website article:
Just to clarify, the repeated words are not repeated in the actual text, and the skipped words are present in the actual text.
In the recording I'm using the SAPI5 voice Zira at speed 85, and I can confirm it is also producing the same effects at slower speeds, as it is if I change the voice to SAPI5 voice Hazel. I'm using NVDA Version: 2020.1, windows 10 Version 1903 (OS Build 18362.900), and am getting these effects in both Mozilla Firefox version 78.0.1 (64-bit) and Google Chrome (which is up to date) Version 83.0.4103.116 (Official Build) (64-bit)
Does anybody know if this is an NVDA issue, or if it's something I can report to the Pulse organisation for them to hopefully sort out?