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
[email protected]
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: [email protected]
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
