Persistent issues with Read Aloud in Edge
I have Windows 11. Today I began having an issue wherein the Read Aloud feature built into Edge doesn't work. I was initially trying to use a similar function on Internet Archive, and noticed that while all the Microsoft voices seemed to be available in the onsite dropdown, the only voices that made any sound were David, Mark, and Zira---none of the "Online (Natural)" voices. I tried to use Read Aloud as a workaround, and found all the buttons greyed out completely. Mind you, everything worked fine yesterday, and I made no changes to my computer in the intervening time. I've opened up two support tickets, but neither live chat agent was able to resolve the issue. Here are the things I've tried with their help: trying the feature on different websites updating & restarting Edge resetting Edge settings to defaults updating & restarting computer switching wifi networks connecting to a hotspot using InPrivate mode using a new Edge profile (rule out interference from extensions) checking that English tts is downloaded in Time & language > Language & region turning Online speech recognition off and back on again resetting experimental features checking sound systems (they work, but just in case) doing a system reset (?) to 24 hours ago, which took about an hour and undid all the updates I just mentioned maybe something else I don't remember? The next thing I am going to try is give my computer a long nap. It's been a while, so maybe it just needs some shut eye. Otherwise, help????
Microsoft Edge TTS refuses to read .pdf files
Hi there, [Reposting this here on the suggestion of an 'Independent Advisor' on the Microsoft Community forums.] I think the native MS Edge TTS is one of the best on the market, but it currently fails to initiate when I try and get it to read .pdf documents (even when opened in the browser and when the text is super-clear so OCR should be working). I have done everything from clearing my cache to reinstalling MS Edge and not importing anything or signing in, so that it's a completely fresh version, but the problem persists. I have also tried on Beta, Developer and Canary as well, with no luck. After a quick search online, I can see I'm not the only one with this problem - are there any fixes on the horizon? This is a real challenge from an accessibility standpoint. Kind Regards, Kristian