One more question. Since described_by/description_for relations are
exposed on cells and header cells both, i.e. multiple described_by
relations should be exposed on cell to link it with row and column
header cells, then how much does this overlap with idea of
IAccessibleTable for headers? I mean when does AT need to have header
table taking into account they can get some information from
relations? Idea when AT might need header table was there might exist
tables where relation targets order (which corresponds to DOM
hierarchy) doesn't satisfy to AT needs.
James Teh suggested to consider the following example
<table>
<tr>
<th>Product</th><th>Bugs fixed</th>
</tr>
<tr>
<th colspan="2">2008</th>
</tr>
<tr>
<td>NVDA</td><td>50</td>
</tr>
<tr>
<th colspan="2">2009</th>
</tr>
<tr>
<td>NVDA</td><td>30</td>
</tr>
</table>
Possibly relations might be not very helpful here. But what kind of
column header table do we expect here?
Alex.
On Thu, May 21, 2009 at 3:19 PM, Alexander Surkov
<[email protected]> wrote:
> Hi.
>
> I summarized all our discussions with Pete about IAccessibleTalbe
> rowHeader/columnHeader implementation -
> https://wiki.mozilla.org/Accessibility/TableHeaders. Feedback on this
> proposal is needed.
>
> Thank you.
> Alex.
>
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
