Google Drive: VoiceOver does not read file or folder names when navigating among them. Table markup confuses VoiceOver's table heuristics and attributes.
Categories
(Core :: Disability Access APIs, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox84 | --- | affected |
People
(Reporter: MarcoZ, Unassigned)
References
Details
(Whiteboard: [Mac2020_2])
Steps:
- Open Drive.
- In the navigation outline, select the "Shared with me" item.
- Using the arrow keys, navigate among the folders and files.
Several observations:
- When navigating inside only the folders or the files, VoiceOver remains silent.
- When focus moves from either the folders to the files, or vice versa, the first selected item will be spoken, but no subsequent focus changes until the table is left and the other one entered.
- When exploring the tables with VoiceOver, they are not read in their entirety. Only the first focused item is navigable, the others are not there.
I explored those on Windows, and noticed that there is a text frame accessible between the table and the table row accessibles, coming from one of the c-wiztags used in Drive's markup. However, they do not seem to serve any purpose other than to contain the actual row. c-wiz is some closed-source JS framework by Google. I don't know what shadow DOM elements these c-wiz tags contain, but they appear to map to our internal TEXTFRAME role somehow. Anyway, these tables are rendered in a way that VoiceOver cannot make use of them, so that's probably why the subsequent rows are not read when focused. They are simply not there in VoiceOver's point of view.
This makes large parts of Drive unusable, marking as S2.
|
Reporter | |
Comment 1•4 years ago
|
||
I have confirmed that fixing bug 1676344 will fix this bug. Eliminating those intermediary hyperText accessibles restores the full table hierarchy for VoiceOver, and thus also the ability to speak the focus in all rows of both the folders and files tables, between which keyboard focus transitions. The test I added in the second Phabricator revision attached to that bug fails without the patch, indicating that there is only one row in the rows array, and one column in each row. A total of 5 properties fail without the first part of that bug. Closing this one as soon as the other patch set lands.
|
|
Reporter | |
Comment 2•4 years ago
|
||
As expected, this has been fixed by bug 1676344. Closing.
|
|
Reporter | |
Comment 3•4 years ago
|
||
Verified fixed in Nightly 84.0a1 (20201111095506).
Description
•