Haven't seen this issue posted anywhere, but maybe I missed it. For the last few Chrome and Edge versions--maybe about a month--loading a page seems often to land screen reader focus in never never land with no object in focus. To get either Narrator or NVDA to get the page into its virtual buffer, I can sometimes reload the page, at other times hit tab, and at other times press NVDA's buffer refresh key. It'll even do it on a simple page like AppleVis. Others getting this?
I wondered if my ad blocker was responsible, but I've disabled all my extensions.
Firefox is working better than I've seen before, so I'm happy 99% of the time until it hits a nag cookie page or Quara "log into Google" nag or the like, which it goes silent on.
Thanks.
Forum
Windows
Comments
Have not experienced this
Admittedly, I tend to use Firefox above all else on Windows, but I will occasionally load up Edge if I absolutely need to for one reason or another. Having said that, I have not experienced the page loading into never Neverland, as you suggest above.
Just because I must ask, have you tried clearing out all of your history in whichever browser you use, just to see if you get any better results?
Me either.
Me either.
Hevy chrome user here
I haven't seen this issue so far, everything updated to latest version.
I have this issue
Hello.
I have this issue. I thought that it is due to problems that can happen with my internet that pages don't always really load so I have to press F5 to update the page for it to work so I confirm this behavior.
clearing site data might at least help
I haven't tested it thoroughly, but the last few times I tried, I only had to hit tab to get into the page. I had literally never in my life gone into settings to clear site data. It's a new computer, but there was still a bunch of crud in there. so thank you brian. I am also prepared to say that windows on arm seems to have a few accessibility object model issues here and there.
oh, and one more thing
I also went into NVDA advanced settings and disabled speaking the virtual buffer before the page has finished loading. Page load remains instantaneous, so maybe it's just grabbing it too quickly