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 Accerciser

3. Use Accerciser's tree of accessibles to examine the accessibility tree for Chrome/Chromium

What is the expected behavior?
Nothing would have a role of "redundant object."

What went wrong?
Quite a few objects (mostly in the browser's chrome) have a role of "redundant object."

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, any Gtk+ app. I've never run across this role in any other app or toolkit.

Documentation: https://developer.gnome.org/atk/stable/AtkObject.html#AtkRole

Impacts: If an object is truly redundant and should be ignored by clients like Orca, it might be more performant for both the user agent and Orca to not create accessible objects for those items in the first place.