UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3500.0 Safari/537.36

Steps to reproduce the problem:
1. Launch Chrome/Chromium
  * export ACCESSIBILITY_ENABLED=1, and
  * launch with --force-renderer-accessibility

2. Launch the attached accessible-event listener in a terminal

3. Load and reload pages in the browser

What is the expected behavior?
The event listener would print out an event when load started and ended (because the page is "busy" when loading).

What went wrong?
The event listener does not print out any events.

Did this work before? N/A 

Chrome version: 70.0.3500.0  Channel: n/a
OS Version: 
Flash Version: 

Compare to: Firefox (with accessibility enabled), Epiphany

Documentation: https://developer.gnome.org/atk/stable/AtkObject.html#AtkObject-state-change

Impacts:

1. These notifications, used in conjunction with document-load notifications, help Orca determine when it is "safe" to present document summaries (e.g. number of landmarks and headings on the page), begin a "say all" of the content, etc.

2. These events also help Orca quickly filter out other accessibility events (e.g. children-changed, text-changed) which are irrelevant to the user because they are being emitted as a consequence of initially loading the content.
 

Deleted: busy-events.py 242 bytes

busy-events.py 242 bytes View Download