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. Load "data:text/html,<table border='1'><tr><th>foo</th></tr><tr><td>bar</td></tr></table>" in browser

3. Launch Accerciser and use the interface viewer to examine the accessible object corresponding with the table element

What is the expected behavior?
The table interface would be shown as implemented in Accerciser's interface viewer.

What went wrong?
The table interface is not shown as implemented in Accerciser's interface viewer.

Did this work before? No 

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/AtkTable.html

Impact: Orca uses the table interface to report table properties (e.g. number of rows and columns), to present row and column headers as the user navigates amongst cells, and perhaps most importantly to provide that means to navigate cell by cell in all directions. None of this functionally works because the accessible table interface is not implemented.

Comments: The border and header in the test case have been added in order to cause the table to be treated as a data table rather than a layout table and thus eliminate the possibility that the interface is absent due to a heuristic. Firefox treats this test case as a data table (absence of layout-guess:true in object attributes). Ditto for Epiphany (it's exposed as a table, rather than as sections of text).