Re: Problem with windows 11 notepad, and browsers


I don't want there to be any misunderstanding of what I am saying.  I am not saying that the person who started the discussion shouldn't have discussed problems with how Notepad or other programs work in Windows 11 compared with how they work in Windows 10.  I am pointing out kinds of approaches I think are important when working with programs and screen-readers.  As I said, screen-readers work in complex environments.  I am not objecting to people asking about or pointing out problems.  I am saying that where there are problems, unless or until they are resolved, you may be able to efficiently work around them in the meantime.  I've been using read current line in screen-reader searches for a long time.  I don't know if the annoyance will ever be corrected but I can avoid the excess speech problem using Reade current line.

I also see, from time to time, people asking about excessive and repetitive speech when an e-mail message is opened in this or that program.  Opening the message, then when the message has opened fully, issuing the read to end command stops the behavior.  If you do this regularly, it becomes second nature.  You may want until the moment you hear a bit of speech before issuing the command or you may want to try to develop a sense of when enough time has passed that issuing the command will start reading.  You may save a bit of time that way. 


On 3/15/2022 12:32 PM, Gene via wrote:

I take that back.  I did see it discussed once in teaching material.  I discussed it in my Internet tutorial, which is out-of-date but which discusses using read current line as I described.  It also points out numerous times where I use logic and inference when working with Internet pages.


On 3/15/2022 12:14 PM, Chris Smart wrote:

Joseph is talking about Notepad in Windows 11.




From: <> On Behalf Of Gene
Sent: March 15, 2022 1:08 PM
Subject: Re: [nvda] Problem with windows 11 notepad, and browsers


What behavior do you, Joseph and the person asking the question, expect in a search in Notepad?  On my Windows 10 computer, in Notepad, if what you are searching for is found, it isn't announced.  NVDA says found next occurrence of text.  In earlier versions of Windows, nothing is spoken.  I can use read current line to hear what has been found but I don't bother.  If the text is found, I hear nothing.  If not, an error message comes up which is spoken. 


When working with screen-readers, using logic and inference to determine what is happening is a skill that helps you use computers well.  this may be important in working with some programs or doing things efficiently in some programs.  Literally expecting a screen-reader to do everything exactly as expected in such a complex environment is a way to get caught up in minutia when you can often know what is going on without a literally exactly correct behavior. 


When using f3 in Notepad, to repeat a search, what is searched for is announced in Windows 10.  I hear it announced, followed by selected. 


I don't recall if I hear anything in earlier versions of Windows.  But whatever the case, if using f3 finds something I know it because no error message comes up. 



On 3/15/2022 11:33 AM, Joseph Lee wrote:


Regarding Notepad on Windows 11, NVDA repeating the last line entered is actually a known problem, and a brief discussion between developers indicates that this may have something to do with (once again) a possible bad UI Automation implementation from Microsoft as Narrator suffers from text announcement bug sometimes (this is one of those instances where I just throw my hands up and give up; I spent some time trying to do something to no avail).

As for find dialog in new Notepad, NVDA not announcing things when you press Enter key is the correct behavior - this can also be observed with Narrator.



Join to automatically receive all group messages.