Yes, it is only occurring in Windows 10 ver 1809. Narrator does not read this information... Rui Fontes Às 23:50 de 20/11/2018, Don H escreveu:

I did and it worked well Window is narrator way better Regards Ian

Wonder how many on the list installed Win 10 version 1809 when it first came out and before it was pulled back. It seems that the strange verbage I get when openning up the settings app relates to

thanks Quentin, deleting the existing auto corrects worked a treat :)

Travis is probably correct, but in all cases this is a matter of the developer not verifying focus control is working in your browser. Of course since you are using not one of the big four browsers,

Ah ha! Hang on, let me check that, because I am using OneCore but I do have symbol level set to none. Let's give it a shot here. Yep! That worked just fine, thanks! Now another question, it says it

Generally, the links that say click here for ore information that do't seem to do anything are the javascript links that simply pop up a window over top of the existing page with the information in

Many sites now helpfully say, click here for main content, or a variation on the theme. But some do as they say, while others seem to cause no discernable change. I have always wondered about this,

Hi, Based on the log I got from this person, it appears UIA events are not seen by NVDA in some cases (even with log level set to debug, relevant info isn't showing up). Cheers, Joseph

What do you mean? Is this a windows 10 thing, as I hear no junk on windows 7. Brian bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting

No I'm using the slower ring if you will. I can't remember but yeah I am usi gsnaps but they are updated I thin weekly. Take care

Yes I have the alpha as a portable, and like to use the beta as a working version, which is why to some extent I do not like it updating to the stable every time. Brian bglists@... Sent

Basically the beta of the last version ran through the rc to the stable, so if that is what you did then yes, you need to restart using the beta again by downloading it. I know it seems cock eyed, but

Yes saw that it made a nasty error noise when it loaded but it seems OK on a reboot. Brian bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@...,

Bit clunky though. I imagine thatches program is not exposing the correct data for nvda to read. Brian bglists@... Sent via blueyonder. Please address personal E-mail

Hi, If you are using alpha snapshots, you don’t have to grab a beta, as the code is identical at this point (although in the next few days, it may diverge somewhat). Cheers, Joseph

I should know the answer to this, but do I as I'm already using a beta need to grab this one? Or am I good to go go go? Take care

Actually , my mac read everything with out exaggeration or what not. It all sounded normal to me. Now if I would have taken the time to "spell" everything , I would probably notice the mistakes, but

Hi, Eh? That's weird. Have you tried with OneCore synthesizer too? If the new CLDR setting is checked from voice settings yet NVDA isn't reading emojis, chances are that you may have symbol level set

Hi, Okay, can you do the following for me please: 1. Close Settings app. 2. Restart NVDA with debug logging enabled (from exit dialog). 3. Open Settings app. NVDA should announce gibberish at this