Status Update
No update yet.
Comments
ja...@google.com
Thank you for reporting this issue. We’ve investigated, but unfortunately have not been able to reproduce it with the steps provided.
- Tables are being read, for example "1. A <div> container wrapping a <table>" is being read out loud.
If you are able to reproduce the issue again or have additional information to help us, please let us know.
For us to further investigate this issue, please go over the data below carefully and provide the following additional information:
Please fill out each question and comment, thank you.
-
If possible, capture the issue in a screen recording with audio (desktop and/or phone capture).
-
Upload the full bug report file. Steps followed here:
https://developer.android.com/studio/debug/bug-report
Note: Please upload to google drive and share the folder to
The more information we have, the more accurately our product and engineering team can solve the issue. Thank you for your cooperation.
me...@adrianroselli.com
Then try to get into the table cells.
I included the first two tables to show they do not break with the role. The two headings preceded with "BROKEN" show the issue, and the two headings preceded by "FIXED" demonstrate the workaround.
ja...@google.com
Thank you for the update.
- Yes, even heading 3 is being read out loud.
For us to further investigate this issue, please go over the data below carefully and provide the following additional information:
Please fill out each question and comment, thank you.
If possible, capture the issue in a screen recording with audio (desktop and/or phone capture).
Upload the full bug report file. Steps followed here:
Note: Please upload to google drive and share the folder to
The more information we have, the more accurately our product and engineering team can solve the issue. Thank you for your cooperation.
me...@adrianroselli.com
The heading isn't the issue, that _table_ following the heading is the issue.
Are you hearing the table following heading 3?
Can you navigate into its cells?
Be aware there are more tables on the page, so pay attention to the focus ring.
In the video I provided, from 1:30 to 1:36 you can see it skip the table completely. Unlike previous tables, it does not go into the cells. All it does it announces the wrapper, but not the table.
ja...@google.com
Thank you for the update.
- I believe I found what it is you are referring to. After the header, it does read the sub header. But it does not read the Author section for example, the way the next header section does. It skips over it.
me...@adrianroselli.com
The sub-header is actually the accessible name of the wrapper <div>, which it gets via aria-labelledby pointing to the id of the <caption>. It is not reading the <caption> directly because it cannot get to it.
For each table following a BROKEN heading, none of the table data can be accessed with TalkBack.
Thank you for trying again.
ja...@google.com
Thank you for reporting this issue. We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.
ja...@google.com
The product and engineering team has replied:
This should be fixed in Chrome version 91.0.4450.0 or higher.
Please retest to see if the issue is resolved.
Thanks!
me...@adrianroselli.com
au...@gmail.com
It is not possible to access the inner elements via talkback.
Description
- When reading the entire page, the tables are skipped;
- When exploring by touch, the tables are skipped;
- When using Alt + T, the tables are skipped.
This construct will trigger the bug, and removing the tabindex will fix it:
```
<div role="region" aria-labelledby="Caption03" tabindex="0">
<table>
<caption id="Caption03">Region, Tabindex</caption>
[…]
</table>
</div>
```
This occurs in Android 9, 10, and 11 across devices. The video example uses Android 11 on a Pixel 2 with Chrome 86.
I have made a demo to demonstrate the issue:
I have recorded a video:
In the video I have TalkBack read the entire page, and then I navigate by keyboard. The Android 11 built-in screen recorder does not capture audio from TalkBack, but the captions are at the bottom of the screen.
So far the only fix I have identified is to put an interactive control (link, button, etc) as a descendant of the container. For example, A link in a table cell, a link before or after the table, or similar with buttons, will make the tables discoverable to TalkBack again.