I'm not sure what the use case for this was, but regardless, this is
potentially going to require a pretty big change to table interfaces. In
order to do table navigation, screen readers need to be able to navigate
from a given cell to the cell in the next column or the next row, as
well as being able to fetch all cells in a given row or column. If the
numbering is not sequential, we can't simply increase indexes to do
this. No API I know of supports something like this.
I guess the table interfaces could just deal with sequential, 0-based
coordinates as they always have. We'd then need a way of getting the
numbers from aria-*index and aria-*count to report to the user. However,
that is extremely obscure and starts to raise questions about why we're
doing this in the first place.
Jamie
On 25/06/2015 9:20 AM, Alexander Surkov wrote:
Hi. ARIA introduced aria-colcount/rowcount [1], [2] which allows -1
value that means the number of rows/columns is unknown. Are there ideas
how to expose that?
Thanks.
Alexander.
[1] https://rawgit.com/w3c/aria/master/aria/aria.html#aria-rowcount
[2] https://rawgit.com/w3c/aria/master/aria/aria.html#aria-colcount
_______________________________________________
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
