Games move pretty fast though. Are you able to OCR and read and act with real speed?

I think I totally agree with the original post. NVDA OCR, in the current form, is quite good already but I think this could be improved further, if technology allows it. From my tests, OCR seems to

The error sound plays when NVDA encounters an error (and that will be written to the log). In some (many?) cases, the program will pick this up, and try something else to do what it needs to do. In

It should work with image PDF files. A couple of things to bear in mind: - It will recognise printed or typed text, but not so much handwritten text (a limitation of basically every OCR). - It works,

Good day:  This is a test to see if I can send and receive group messages. Dave

Hi, No, it doesn’t do that, although we came so close to it a while back with Crash Hero. The checkbox in question is about data to be sent when NVDA checks for updates for the purpose of gathering

It works with content immediately visible on the screen.

Doesn't NVDA have an automatic bug reporting system? I thought that is why we have that checkbox that says if you want to send info to the NVDA developers to make it better. Thought it

Joseph, The lack of detailed bug reporting is hardly limited to NVDA, and you know that as well as anyone. But as I've said before, and Tyler confirms in other instances (but at

Ok nope it really doesn't. I guess that's the one thing I'll keep the other screen reader for.

OK will do. Does this work with image PDF documents?

Find a graphic with text and hit NVDA+r. OCR results pop up in a little virtual window. Hit escape to close.

I've never used the OCR with NVDA, so how do you use it?

There have been lots of messages on this group in the last several days

I haven't been receiving messages from this group in some time. I just want to make sure I can still receive message and send messages. -- Joshua Hendrickson Joshua Hendrickson

Hi, It is useful in alpha builds, but I do understand that it isn't so much for beta releases. The bigger problem isn't swapping debug tone - rather, instructing people as to how to spot these errors

Maybe the solution here is to open issues for every single error we hear that isn't a duplicate of something else, since these are obviously important enough to get the user's attention. You (and

- Works for me. But the production of error tones when there are no errors is, quite simply, a philosophical no-go for me. I don't care if some "benchmark tone" is used, but it should never be what

Hi, One counterexample, although not that intuitive, is desktop watermark shown on Windows Insider Preview builds; they are early beta quality builds so folks expect stability when considering small

NVDA-X would break my fingers on my left hand, lol. Seriously I think it is free….