Because of multiple edits I made for the previous email, it is not so clear as I would expect :) So putting it into different words.
It sounds that main problem of ARIA span is that, it can be used to span the missed cells. In this case it cannot be exposed via IAccessibleTable interface as a cell extent because cell index + cell extent should point to the missed cell, however it points to the last cell in DOM. Jamie's suggestion if I read it right was to put ARIA span as an object attribute if it serves for informational proposes only, otherwise expose it via IAccessibleTable as we do that for HTML. It sounds reasonable with me. If there are no objections then that's the way to go I think. On Thu, Jul 16, 2015 at 10:35 AM, Alexander Surkov < surkov.alexan...@gmail.com> wrote: > So we do have two use cases. > > #1 Example of spanned cells in a table having missed column > <div role="table" aria-colcount="4"> > <div role="row"> > <div role="cell" aria-colindex="1" aria-colspan="2">cell 1</div> > <div role="cell" aria-colindex="4">cell 4</div> > </div> > <div role="row"> > <div role="cell" aria-colindex="1" aria-colspan="2">cell 1</div> > <div role="cell" aria-colindex="2">cell 2</div> > <div role="cell" aria-colindex="4">cell 4</div> > </div> > </div> > > #2 Example of spanned cells > <div role="table"> > <div role="row"> > <div role="cell" aria-colspan="2">cell 1</div> > </div> > <div role="row"> > <div role="cell">cell 1</div> > <div role="cell">cell 2</div> > </div> > </div> > > Do I understand correct that the table interface should take into account > of aria-colspan in case #2, and it should ignore it in case #3? > > > On Sun, Jun 28, 2015 at 9:13 PM, James Teh <ja...@nvaccess.org> wrote: > >> I think it should. However, this shows up an edge case. What if the >> author provides non-contiguous rows or columns, as aria-row/colindex >> allows? For example, suppose only columns 1 and 4 were in the DOM (using >> aria-colindex), but column 1 had a span of 2 (using aria-colspan). Column 4 >> in the DOM would be mapped to column 2 in the table interface (since the >> table interface is always contiguous). In this case, the table interface >> should not expose column extent for column 1, since that would suggest that >> column 2 in the table interface was spanned (which is column 4 in the DOM). >> So now we need a secondary way of exposing aria-colspan, perhaps an object >> attribute. This is really quite hideous. FWIW, I don't know of any API that >> can handle this; UIA can't either. >> >> Jamie >> >> >> On 27/06/2015 8:15 AM, Alexander Surkov wrote: >> >>> Hey. ARIA introduced aria-rowspan and aria-colspan attributes [1] and >>> [2]. Should be they exposed as part of IAccessibleTable interface, i.e. >>> as col/row extents? >>> >>> [1] https://rawgit.com/w3c/aria/master/aria/aria.html#aria-rowspan >>> [2] https://rawgit.com/w3c/aria/master/aria/aria.html#aria-colspan >>> >>> >>> >>> _______________________________________________ >>> Accessibility-ia2 mailing list >>> Accessibility-ia2@lists.linuxfoundation.org >>> https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2 >>> >>> >> -- >> James Teh >> Executive Director, NV Access Limited >> Ph +61 7 3149 3306 >> www.nvaccess.org >> Facebook: http://www.facebook.com/NVAccess >> Twitter: @NVAccess >> SIP: ja...@nvaccess.org >> _______________________________________________ >> Accessibility-ia2 mailing list >> Accessibility-ia2@lists.linuxfoundation.org >> https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2 >> > >
_______________________________________________ Accessibility-ia2 mailing list Accessibility-ia2@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
