> Oddly the <td> does not show up in the Accerciser hierarchy,
> though the two paragraphs inside it do.
This is due to the fact that WebKit decides not to expose "layout tables" as tables. Your table has been heuristically declared a "layout table," thus your cells are not cells and your table is not a table. :-)
WebKit a11y work is largely the work of the folks at Apple. They've done lots of great things which we can ultimately use. However, sometimes what makes sense for VoiceOver users doesn't jive with what we expect in GNOME-based ATs. This is such a case.
My intent is to make a platform specific change to cause such tables and cells to be exposed as such, leaving it up to individual ATs to decide how to present the content. With any luck, that might be sufficient to cause Orca to present the right info even with a borked table hierarchy (which is also on my list for this weekend). Such a change, I believe, will be small, simple, and safe. So even if there have been API changes, you could patch your version of WebKitGtk to fix the issue.
All a long way of saying the following: If it's not too late, hold off on the list conversion and let me see what I can do between now and Monday evening.
Triaging now.....
W.r.t. this:
> Oddly the <td> does not show up in the Accerciser hierarchy,
> though the two paragraphs inside it do.
This is due to the fact that WebKit decides not to expose "layout tables" as tables. Your table has been heuristically declared a "layout table," thus your cells are not cells and your table is not a table. :-)
WebKit a11y work is largely the work of the folks at Apple. They've done lots of great things which we can ultimately use. However, sometimes what makes sense for VoiceOver users doesn't jive with what we expect in GNOME-based ATs. This is such a case.
My intent is to make a platform specific change to cause such tables and cells to be exposed as such, leaving it up to individual ATs to decide how to present the content. With any luck, that might be sufficient to cause Orca to present the right info even with a borked table hierarchy (which is also on my list for this weekend). Such a change, I believe, will be small, simple, and safe. So even if there have been API changes, you could patch your version of WebKitGtk to fix the issue.
All a long way of saying the following: If it's not too late, hold off on the list conversion and let me see what I can do between now and Monday evening.