Chrome Crashes with Narrator When Navigating beyond Tab and Arrows

[Ana G]

Hi All,


I'm running Chrome on three different Windows 10 machines: a Dell
four-in-one running 2004, a Surface Pro 7 running 1909, and an HP laptop
(at work) running the last version where you use caps-lock+tab to read
the item with focus.


On all three machines, I have trouble using Chrome with Narrator. Things
mostly (though not entirely) work fine when I'm just tabbing and
arrowing around. When I use more advanced navigation, however, Chrome
crashes. For example, in the two newer versions I'm citing, if I open a
page, go into scan mode (caps-lock+space), and hit the letter H a few
times to find out what headings are available, the page crashes after a
couple of keystrokes, or if I'm using say-all (caps-lock+dn-arrow) in
scan mode and hit B a couple of times to jump to a button, the page
crashes.


I know there are fewer commands in the earliest version of Narrator I'm
citing, and I'm so used to just arrowing that I don't remember the
specific examples there, but that version is also unstable.


In all versions, I'm not sure exactly what causes the crashes because I
can sometimes work with the page for a full two minutes or so before
Chrome kicks me out and closes, but in the newer versions the problem
seems to be using screen reader navigation commands (e.g., B for button,
H for heading, X for checkbox) while in scan mode. When I switch to NVDA
or Jaws, I don't have any problems with Chrome, so the issue is clearly
between Chrome and Narrator.


Weirdly, this problem may or may not happen if I go to a page from, say,
an email link, but it happens almost every time if I go to a page from a
search or from a URL I type in.


I use Narrator at work because I only do a couple of things on the
computer, but this problem is so incredibly disruptive that I've
installed NVDA to get that small amount of work done. I really would
prefer to use Narrator.


Ciao

[chal...@gmail.com]

Hmm, if Chrome is crashing then it seems like the issue is somewhere in Chrome. Sure Narrator may be doing something wrong, but nothing Narrator is doing should cause an application to crash. I'm curious, do you have any better luck with Narrator and the latest Edge based on Chromium?

--
Christopher (AKA CJ)
Chaltain at Gmail

> --
> You received this message because you are subscribed to the Google Groups
> "axs-chrome-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to axs-chrome-disc...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/axs-chrome-discuss/11c1fb7c-63e1-363a-
> 6b39-9913c7d8a52d%40sbcglobal.net.