I am a user of NVDA and would love to use Chrome with NVDA, however this issue definitely causes a loss of productivity. I very much appreciate all of your work and effort to make Chrome accessible to those of us that rely on screen reading technology. I do experience this issue, and it does not only happen with the above sites.

Additional notes: I am able to reliably repro this bug on both Dev and Canary but not on regular Chrome build. I can always cause this bug to come up by doing the following:
1. Navigate to blindbargains.com
2. Navigate to google.com
3. Observed behavior on my end is that there is a loss of focus and NVDA can no longer access web content. NVDA hasn't frozen, and Chrome has not crashed.

I am attaching an NVDA log as I am not sure if the issue is Chrome-related or related to NVDA. However I hope this helps in troubleshooting the issue.

Deleted: NVDA Log.txt 15.4 KB

NVDA Log.txt 15.4 KB View Download

Sorry, I was unable to reproduce any crashes. I am looking into the focus bug.
I started NVDA (fully updated), started Chrome Canary Version 51.0.2699.0 (64-bit), cleared my history and navigated to all the sites listed above. Then, I navigated to the same sites again in a few random permutations. No crashes occurred.
Could you please provide the IDs associated with the crashes?
To do this, navigate to chrome://crashes and copy / paste here the IDs of the crashes that took place on the day you had experienced this issue.

Hello,

I can not provide an ID as Chrome did not actually crash. I apologize if 
the content of the message is confusing, however the focus loss is what 
I experience. Chrome does not crash, however NVDA gets to a point where 
it is unable to read web content unless Chrome is restarted.

Thank you so much for all that you do and for looking into this issue.

On 4/4/2016 2:19 PM, nektar@chromium.org via Monorail wrote:

Sorry for misunderstanding the issue. Indeed, NVDA freezes. Not Chrome.
The problem is that under certin conditions, NVDA's tree interceptor doesn't get created. I checked with other accessibility debugging tools and Chrome's accessibility tree is present and accessibility mode is enabled, but NVDA still doesn't create a virtual buffer for it.
I'll look through NVDA's source code to see where we might be tripping it up, since the log didn't help.
Thanks for your patientce while I am trying to resolve this.

Crashes have definitely been eliminated.