Currently, when a table appears to be a layout table, Chrome does not expose it as a table at all.
On Windows, we should switch to Firefox behavior, where it is still exposed as a table, with the additional object attribute layout-guess:true.
On Android and ChromeOS, we should also expose as a table.
On Mac, we should continue to not expose it as a table for now, in order to match Safari and what is expected by VoiceOver users. If we learn in the future that users would prefer these layout tables to be exposed as tables, it can be changed.
Currently, when a table appears to be a layout table, Chrome does not expose it as a table at all.
On Windows, we should switch to Firefox behavior, where it is still exposed as a table, with the additional object attribute layout-guess:true.
On Android and ChromeOS, we should also expose as a table.
See the attached file for an example table that is treated as a layout table.
On Mac, we should continue to not expose it as a table for now, in order to match Safari and what is expected by VoiceOver users. If we learn in the future that users would prefer these layout tables to be exposed as tables, it can be changed.
Comment 1 by aleventhal@chromium.org
, Jan 23 2018