Yes, #2 is the use-case I had in mind - a spreadsheet where only some of
the cells are actually rendered at any one time.
I think we need both aria-rowindex/aria-colindex and also
aria-rowspan/aria-colspan, otherwise it's not possible to make an arbitrary
ARIA grid without using an HTML table.
One other thought: it'd be nice if you could put aria-rowindex on the
element with role="row" rather than needing to repeat it on every single
cell. (Not sure about aria-colindex, but at least the row would be helpful.)
On Mon, Jan 12, 2015 at 5:07 PM, Daniel Trebbien <dtrebbien@gmail.com>
wrote:
> Hi Alexander,
>
> Two reasons that I can think of for having aria-rowindex/aria-colindex in
> addition to rowspan/colspan are:
>
> 1. You can apply aria-rowindex/aria-colindex to non-TD/TH elements.
>
> 2. Even when using table elements, if you only have rowspan/colspan
> available, then you have to make sure that the table model is "filled out"
> to match the table that you are trying to represent. For example, suppose
> that you want to start at row 1000 of 5000. You would have to have an
> empty TD spanning the first 999 rows in a separate TBODY so that implied
> empty rows would be created. With aria-rowindex/aria-colindex, the
> separate TBODY would be unnecessary.
>
>
> On Mon, Jan 12, 2015 at 11:51 AM, Alexander Surkov <
> surkov.alexander@gmail.com> wrote:
>
>> Hi. Can anybody share some use cases for aria-rowindex/colindex? Does it
>> serve for other proposes than HTML rowspan/colspan attributes?
>> Thanks.
>> Alex.
>>
>
>