toggle quoted messageShow quoted text
Yes, that's what I would also consider the natural response. For me, unfortunately, it doesn't always see those focus changes in the first place.
I'll do some more testing with different timing constellations, for example, I'll wait until hard drive activity is very low before trying again. Maybe there's a pattern.
Any ideas, anyone, if it's Windows not raising the events, or NVDA failing to process them? Is there a way to find out easily?
John J. Boyer <john.boyer@...
> schrieb am Mo., 11. Sep. 2017 um 16:14 Uhr:
I use a braille display. When I start Firefox NVDA shows the first link on my home page, because that is where Firefox
has placed the cursor. i have always considered this the natural response. If I want to type something in the address
bar I press Alt+d.
On Mon, Sep 11, 2017 at 08:41:44AM +0100, Brian's Mail list account via Groups.Io wrote:
> For me its nearly always a browser.
> Sent via blueyonder.
> Please address personal email to:-
> briang1@..., putting 'Brian Gaff'
> in the display name field.
> ----- Original Message ----- From: "Quentin Christensen"
> To: <email@example.com>
> Sent: Monday, September 11, 2017 7:35 AM
> Subject: Re: [nvda] Focus changes that NVDA doesn't seem to notice
> >Which version of Windows are you using? And from the way you've written,
> >assume Chrome is just an example - it also happens if you open NotePad or
> >Word or Calculator or anything else?
> >On Mon, Sep 11, 2017 at 4:33 PM, Felix G. <constantlyvariable@...>
> >>I was wondering if anyone else has experienced the following phenomenon.
> >>Soon after starting Windows, I launch a program, let's say Chrome, and
> >>no feedback whatsoever about it. In particular, the Chrome window title
> >>not announced, and neither is the address bar. To test what NVDA is
> >>I press NVDA+t, and it says "Explorer." However, maintaining the
> >>that Chrome indeed has focus, I type a web address and press enter, and
> >>indeed the site opens in Chrome and is read properly by NVDA.
> >>So, a new window became active, and keyboard focus was on a specific
> >>control within this window, but NVDA did not detect this. The NVDA log
> >>shows no irregularities.
> >>Any idea what might be going on and how the effect could be prevented? Is
> >>it a known fact that Windows sometimes does not raise such important
> >>events? Or might there be a timing issue in which NVDA is temporarily
> >>overloaded and thus fails to track them? Would that not generate log
> >>Kind regards,
> >Quentin Christensen
> >Training and Support Manager
> >Official NVDA Training modules and expert certification now available:
> >Facebook: http://www.facebook.com/NVAccess
> >Twitter: @NVAccess
John J. Boyer
Status: Company dissolved but website and email addresses live.
Location: Madison, Wisconsin, USA
Mission: developing assistive technology software and providing STEM services
that are available at no cost