UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3505.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 (an accessibility inspector for GNU/Linux)

3. View a document

4. Expand "Accessible" in Accerciser's Interface Viewer and examine the state set for each of the accessible objects corresponding with elements in the document

What is the expected behavior?
* Expandable elements would have STATE_EXPANDABLE

* Elements would have STATE_HORIZONTAL or STATE_VERTICAL to indicate their orientation

* Elements which are rendered would have STATE_VISIBLE

* Elements which are on screen would have STATE_SHOWING

* Elements which are multiselectable would have STATE_MULTISELECTABLE

* Elements which are required would have STATE_REQUIRED

* Link elements which are visited would have STATE_VISITED

* Input elements with an invalid state would have STATE_INVALID_ENTRY

* Input elements which are checkable (like a checkbox) would have STATE_CHECKABLE

* Elements which are busy (loading/repopulating) would have STATE_BUSY

* Elements representing a modal dialog would have STATE_MODAL

* Text inputs would have STATE_MULTI_LINE or STATE_SINGLE_LINE to reflect their type

* Inputs which support autocompletion would have STATE_SUPPORTS_AUTOCOMPLETION

* Interactive elements which are not "grayed out" would have STATE_SENSITIVE

What went wrong?
The expected behavior is not implemented.

Did this work before? N/A 

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

Impact: Orca uses states as a key aspect of figuring out if and how to present elements to the user.