- From: Sailesh Panchang <sailesh.panchang@deque.com>
- Date: Wed, 1 Jul 2015 10:24:01 -0400
- To: Jonathan Avila <jon.avila@ssbbartgroup.com>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Jon, >>There are just some situations where no cell acts as a row header I did acknowledge in my email (see link#1) that sometimes, one will need to concatenate two/three cells using headers-id method in order to provide a unique row identifier even for a simple table when the header-data relation is not very strong or unambiguous. That may be tedious / impractical. But in order to allow users to experience the functionality offered by the table markup, exposing one column as a row header with the scope attribute will surely help if it cannot be marked up as TH. Consider the 3 column table in the tutorial with Date, Event, Venue as column headers. I agree the date by itself does not serve as a row identifier but in this case perhaps the event name does. I know the scope will work on cells to the right of it but providing it on what the author considers the best candidate for a row identifier will surely help SR users at least. The table "presentation" conveys "relationships" and offers "functionality" ...these should be perceivable / available to AT users as well. (Refer H51 and normative definitions of the 3 terms). Thanks, Sailesh Panchang
Received on Wednesday, 1 July 2015 14:24:28 UTC