From:  "Rich Caloggero" <>
Date:  26 Jun 2015 04:07:10 Hong Kong Time

Re: Firefox and live regions with Jaws


Update: this is *not* a regression. 

There is a setting in Jaws quick settings dialog (jawsKey+v). If you enter this dialog when in Firefox and find the setting “page refresh”, be sure it is set to “automatically”. I had it set to “off”.

This is not intuitive behavior for this setting. It predates the introduction of live regions and was intended to turn off full-page meta refreshes which used to be the way that web pages would maintain “real time” information before the advent of asynchronous javascript (ajax) methods.  I kept it set to off out of habbit, even though very few, if any, websites use this method of keeping the document current.  The effect was that it prevented DOM modifications from effecting the virtual buffer, but did speak the changes if they occured inside a container marked up as a live region.

Hope this helps someone out there. I’ve been pulling my hair out over this one for months now. Oddly enough, Jaws14 and earlier did not exhibit this behavior.

-- Rich Caloggero, MIT ATIC

From: Marco Zehe 
Sent: Tuesday, June 23, 2015 6:04 PM
To: Rich Caloggero 
Subject: Re: Firefox and live regions with Jaws

Hi Rich, 

I am not aware of any changes in the way we notifiy assistive technologies when live region changes occur. The fact that other page changes don't seem to be reflected in JAWS virtual buffer suggests that they regressed somehow.


On Mon, Jun 22, 2015 at 6:47 PM, Rich Caloggero  wrote:

  I've noticed a regression in the past two major versions of jaws whereby text accumulating in a live region will speak based on the attributes on the live region, but it is not shown in the virtual buffer until you manually refresh the page.  Of course, this also happens on any change to the page, whether it happens to be marked up as a live region or not, but the live region case is perhaps the most interesting because Jaws obviously knows the DOM has changed, but is not responding to it properly.

  Am I correct in assuming that this is a Jaws issue, or does it have something to do with a possible change in the way firefox notifies assistive technologies of DOM changes?  It does not happen with Jaws in IE for instance, but nor does it happen with NVDA and firefox.

  I've contacted FreedomScientific many times, but they do not recognize the issue.

  See the following for a simple test case:

  -- Rich