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

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

2. Load the attached test case in the browser (progress-value.html)

3. Launch the attached accessible-event listener (value-events.py)

4. Press the "change value" button several times

What is the expected behavior?
The event listener would print out a value change event each time the value changes.

What went wrong?
The event listener doesn't print out any value change events.

Did this work before? No 

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

Compare to: Firefox (with accessibility enabled)

Documentation: https://developer.gnome.org/atk/stable/AtkValue.html#AtkValue-value-changed

Impact: Because there is no accessible event when the value changes, Orca cannot present the change to the user.

Comments:

The test case made the progress element focusable, and the listener also listens for focus changes, so one can verify that the value interface is implemented correctly and updating the current value: Just Tab between the progress element and the button element and the listener will print out the value in response to the focus change. It's just the value-change events which are absent.

Anything which implements the value interface (e.g. input with type='number') should emit value-changed events when the value changes. Gecko and WebKitGtk+ seem to be failing in this regard (at least for a number input). But that is due to a bug or implementation failure in those user agents. The events are expected.
 

Deleted: progress-vaue.html 323 bytes

progress-vaue.html 323 bytes View Download

Deleted: value-events.py 746 bytes

value-events.py 746 bytes View Download