- From: Alexander Surkov <surkov.alexander@gmail.com>
- Date: Wed, 28 Jan 2015 15:35:28 -0500
- To: Dominic Mazzoni <dmazzoni@google.com>
- Cc: Joanmarie Diggs <jdiggs@igalia.com>, "W3C WAI Protocols & Formats" <public-pfwg@w3.org>
- Message-ID: <CA+epNsenW2fr224pe9iBWezRW4dyEm5e-YqZ3mbqM_b-AxPQaA@mail.gmail.com>
It makes me think that table role is more appropriate place for aria-colindex. Having aria-colindex on cell allows the author to "move" the cells relative each other what overrides native semantics. On Wed, Jan 28, 2015 at 3:28 PM, Dominic Mazzoni <dmazzoni@google.com> wrote: > This seems wrong to me - ARIA is overriding the native semantics. > > 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> > > On Wed, Jan 28, 2015 at 12:19 PM, Alexander Surkov < > surkov.alexander@gmail.com> wrote: > >> Not sure, maybe something like this. >> >> <table> >> <thead> >> <th>field1</th> >> <th>field2</th> >> <th>field3</th> >> </thead> >> <tbody> >> <tr aria-colindex="2"> >> <td>only 3d column is loaded</td> >> </tr> >> </tbody> >> </table> >> >> I'm not sure what is use case for aria-colindex. If it's supposed to make >> holes in table (aka not yet loaded cells) and they can be anywhere in table >> then aria-colindex is suitable on cell role. If it's supposed to "skip" >> cells from beginning like spreadsheet then it's good to have it on row role >> or even on table role. Do we have examples other than spreadsheet? >> >> >> On Wed, Jan 28, 2015 at 3:08 PM, Joanmarie Diggs <jdiggs@igalia.com> >> wrote: >> >>> Hey Alex. >>> >>> Could you please provide a quick example of an ARIA non-interactive >>> table showing aria-colindex as a property of the row? >>> >>> Thanks! >>> --joanie >>> >>> On 01/27/2015 02:58 PM, Alexander Surkov wrote: >>> > tables are not different from grids in that means I think so if table >>> is >>> > not supposed to have holes then aria-colindex can be hosted by row. >>> > >>> > On Thu, Jan 22, 2015 at 9:28 AM, Joanmarie Diggs <jdiggs@igalia.com >>> > <mailto:jdiggs@igalia.com>> wrote: >>> > >>> > On 01/13/2015 01:54 PM, Alexander Surkov wrote: >>> > > Anyway if gridcells in the same row are not supposed to have >>> different row >>> > > indexes then aria-rowindex doesn't make sense on gridcell. If >>> gridcells in >>> > > a row won't have holes between each other then aria-colindex can >>> be defined >>> > > on the row. In that case aria-rowindex and aria-colindex would >>> mean a X-Y >>> > > shift of the grid. >>> > >>> > Are these properties going to be limited to just grids? Or will >>> they >>> > also apply to the proposed new ARIA table roles (for >>> non-interactive >>> > tables)? If the latter, wouldn't aria-colindex be a property of >>> the cell >>> > and not the row? >>> > >>> > --joanie >>> > >>> > >>> >>> >> >
Received on Wednesday, 28 January 2015 20:35:56 UTC