Without a specific page for potential assistants to attempt to replicate the issue, and figure out a fix, it's almost impossible to propose one.

--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

It’s hard waking up and realizing it’s not always black and white.

     ~ Kelley Boorn

 

I've encountered  those on some pages. something like "blah blah blah dot com says ..." then that's it. maybe it's a chrome issue, I really don't know. It's frustrating though.

Hi Group,

The referenced page reads well in Firefox.

Using the popup dialog on this page:

https://www.w3schools.com/js/js_popup.asp

It looks like this is a Chrome issue. Thanks all.

Devin Prater

sent from Gmail.

On Thu, Oct 29, 2020 at 12:42 PM Luke Robinett <blindgroupsluke@...> wrote:

I run into this nearly all of the time with Web dialogs in chrome. It would probably be easier to give the developers an example of a time when it actually worked correctly, LOL.

On Oct 29, 2020, at 9:50 AM, Devin Prater <r.d.t.prater@...> wrote:



Hi all. I can't give the specific page, and can't find the HTML or JavaScript source for this dialog, but I've found a dialog on the web that is not read automatically by NVDA. This problem is in Google Chrome, but is not with Firefox. The text of the dialog is not read by NVDA, but the OK button is, and the OK and cancel buttons can be navigated to. The text can be reached with Object Navigation.

However, the text of the dialog is read automatically by Narrator in Google Chrome. It is not read automatically by JAWS, though. Any ideas on what's causing this, or any ways to fix? Or am I missing some Google Chrome addon or something?

Devin Prater

sent from Gmail.

-- 
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"

On Thu, Oct 29, 2020 at 02:29 PM, Devin Prater wrote:

It looks like this is a Chrome issue.

-
Devin, the following is not meant to split-hairs, but to seek further clarification from you, as you can test this out quickly:  Is it a Chrome issue, or a Chromium issue?  This can be determined by testing the issue you're having with the page you referenced in new Edge, Brave, or any other Chromium-based browser.

Even though the Chromium-based browsers have way more in common than they do as differences, there can be weird things that really are specific to a single one or common to all of them, depending on the root cause.
--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

It’s hard waking up and realizing it’s not always black and white.

     ~ Kelley Boorn

 

I tested it in Brave and the dialog wasn't read. I had to use object navigation, I believe with Browse Mode off, though thisw was a few hours ago and I'm not sure now.

Gene

This is a situation where all appearances are that it's on "the Chromium side" that the bug exists in that something that should be exposed to the screen reader in a standard way isn't being exposed.  This is particularly indicated by the fact that Firefox, which uses an entirely different rendering engine, doesn't have the problem, and you know the webpage code has to be the same.

Now, what I don't know is the best way to approach this.  I have no idea how to file a bug report/trouble ticket or similar in such a way that all Chromium-base browsers would receive the fix.  I believe most of them do use the updated Chromium core code as it gets released, but I'm not 100% certain of that.

There are times when it may make sense to file a bug report with your screen reader's developers (NVDA, in this case) since there tends to be a far more consistent and open communication channel between the organizations that build and maintain screen readers and the various web browser development communities than any end user has any ability to tap.  But I don't know if this is the case here.  I am going to flag Quentin Christensen on this message to have him weigh in.

This is a gray area as far as whose cage should be rattled initially by the user(s) having issues.
--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

It’s hard waking up and realizing it’s not always black and white.

     ~ Kelley Boorn

 

--

Hi Group,

Now this is weird. Since the new Edge is Chrome based, I thought I would try Edge on this web page.
It works just as well as Firefox. Go figure!

This is a situation where all appearances are that it's on "the Chromium side" that the bug exists in that something that should be exposed to the screen reader in a standard way isn't being exposed.  This is particularly indicated by the fact that Firefox, which uses an entirely different rendering engine, doesn't have the problem, and you know the webpage code has to be the same.

Now, what I don't know is the best way to approach this.  I have no idea how to file a bug report/trouble ticket or similar in such a way that all Chromium-base browsers would receive the fix.  I believe most of them do use the updated Chromium core code as it gets released, but I'm not 100% certain of that.

There are times when it may make sense to file a bug report with your screen reader's developers (NVDA, in this case) since there tends to be a far more consistent and open communication channel between the organizations that build and maintain screen readers and the various web browser development communities than any end user has any ability to tap.  But I don't know if this is the case here.  I am going to flag Quentin Christiansen on this message to have him weigh in.

This is a gray area as far as whose cage should be rattled initially by the user(s) having issues.
--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

It’s hard waking up and realizing it’s not always black and white.

     ~ Kelley Boorn

 

-- 
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"