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

Steps to reproduce the problem:
1. View the attached test case.

2. Launch Accerciser and use its event monitor to monitor state-changed events in Chromium.

3. Tab amongst the three focusable containers (thead, tbody, tfoot) in the table.

What is the expected behavior?
Each time focus changed, a focus event would be emitted by the container.

What went wrong?
The first time one of the containers gains focus, a focus event is emitted by the table. Subsequent focus changes within the table result in no events being emitted.

Did this work before? N/A 

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

The problem appears to be the lack of accessible objects for the focusable elements (tbody, thead, tfoot). As a result, the parent container is emitting the events. Because it appears to us (the ATK support) that the same object is repeatedly claiming focus, we only emit the first of the events.

Even if we didn't filter out the subsequent events from the table as duplicates, emitting a focus event just for the parent container isn't especially helpful to the end user who needs to know what part of the table is getting focus with each tab press.
 

Deleted: focusable-table-containers.html 410 bytes

focusable-table-containers.html 410 bytes View Download