But why? having aria-colindex on cell makes my example possible. It doesn't
look any better than on row.
<table>
<thead>
<th>X</th>
<th>Y</th>
<th>Z</th>
</thead>
<tr>
<td aria-colindex="2">We skipped X and Y successfully</td>
</tr>
On Wed, Jan 28, 2015 at 4:06 PM, Joanmarie Diggs <jdiggs@igalia.com> wrote:
> Hi all.
>
> On 01/28/2015 03:28 PM, Dominic Mazzoni wrote:
>
> > The use-case I had in mind was more like this, where the entire table
> > isn't rendered, and the rows or columns that are rendered are a subset
> > of the virtual set of all rows and columns.
> >
> > <table>
> > <caption>Showing columns 24 through 26</caption>
> > <thead>
> > <th aria-colindex=24>X</th>
> > <th aria-colindex=25>Y</th>
> > <th aria-colindex=26>Z</th>
> > </thead>
> > <tbody>
> > <tr>
> > <td aria-colindex="24">Xylophone</td>
> > <td aria-colindex="25">Yak</td>
> > <td aria-colindex="26">Zebra</td>
> > </tr>
> > </tbody>
> > </table>
>
> And that's the same sort of thing I was picturing. As such, I think that
> (as you've done in your use case), aria-colindex needs to be a property
> of the cell; not of the row.
>
> Where would you put aria-rowindex? On the row element or the cell
> element? I myself cannot think of a reason to have authors duplicate it,
> but there may be one.
>
> --joanie
>