- From: Daniel Trebbien <dtrebbien@gmail.com>
- Date: Mon, 12 Jan 2015 20:07:55 -0500
- To: Alexander Surkov <surkov.alexander@gmail.com>
- Cc: "W3C WAI Protocols & Formats" <public-pfwg@w3.org>
Received on Tuesday, 13 January 2015 01:08:22 UTC
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. >
Received on Tuesday, 13 January 2015 01:08:22 UTC