Closed Bug 1840895 Opened 2 years ago Closed 2 years ago

JAWS + Firefox ignores updates to role="status"

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Version:
Firefox 114
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1440083

People

(Reporter: sskwon, Unassigned)

References

(Blocks 1 open bug)

Details

Steps to reproduce:

Changes to role="status" elements are not being announced by NVDA only on Firefox.

Repro:

  • go to https://codepen.io/shws/pen/dyQpzXj
  • move focus on to the button
  • hit ENTER to toggle the tooltip
  • with JAWS + Chrome, the tooltip content is read once shown. With JAWS + Firefox, the tooltip content is not announced.

Also worth noting, looking at this Freedom Scientific demo page for aria live regions, and found that with JAWS + Firefox, the live region is not being announced when the content changes. Looking at this same page with JAWS + Chrome the live region is being announced as it changes.

To further test, I created a codepen (https://codepen.io/shws/pen/ZEmpJRJ) with role="status". Again, I found that with JAWS + Firefox, the live region is never announced (I also tried setting aria-live="assertive" and that did not alter anything). With JAWS + Chrome, the contents of that region is announced every time it's changed.

To repro:

  • go to https://codepen.io/shws/pen/ZEmpJRJ
  • navigate to the "Click Me" button
  • click the button to update the text on the page
  • With JAWS + Chrome, the updated text is announced after each button click. With JAWS + Firefox, this updated text is not announced.

Also worth noting that I filed a bug against JAWS but was told to instead file a bug against Firefox since this is only an issue on this browser.

Actual results:

JAWS does not announce updates to aria live regions.

Expected results:

JAWS should announce updates to aria live regions.

The Bugbug bot thinks this bug should belong to the 'Core::Disability Access APIs' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Disability Access APIs
Product: Firefox → Core

I'm somewhat surprised by this, as I tested live regions with JAWS fairly recently. Marking as s2 for now because this is pretty serious if the breakage is this widespread. Severity might be downgraded depending on the outcome of testing.

Blocks: jaws
Severity: -- → S2

I can't reproduce this. With JAWS and Firefox on my system, all of the test cases you've provided announce the live content as expected.

What versions of JAWS and Firefox are you using?

Flags: needinfo?(sayrisays)

Oh, one more question: are you starting Firefox after you start JAWS or the other way around? JAWS unfortunately relies on some Firefox legacy code that can only be enabled if JAWS is detected when Firefox starts accessibility. If Firefox is started after JAWS, everything will work fine. However, if you start Firefox and then start JAWS later, this might not work.

Firefox V 114.0.2 (64-bit)
JAWS Version 2020.2006.12 ILM

Machine:
Edition Windows 10 Enterprise
Version 22H2
Installed on ‎3/‎8/‎2021
OS build 19045.3086
Experience Windows Feature Experience Pack 1000.19041.1000.0

I was opening firefox then NVDA -- if I open NVDA after firefox things are working. Is there a bug for this behavior?

Flags: needinfo?(sayrisays)

Gah sorry, can't edit my previous comment. I mean to say if I open Firefox after JAWS then things are WAI.

Thanks for the info. That's bug 1440083. I'm going to close this as a duplicate.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Duplicate of bug: 1440083
Resolution: --- → DUPLICATE

Thanks for the quick triage, appreciate it!

You need to log in before you can comment on or make changes to this bug.