- From: Steven McCaffrey <smccaffr@MAIL.NYSED.GOV>
- Date: Fri, 11 May 2001 11:19:05 -0400
- To: <liz@netlogix.net>, <w3c-wai-ig@w3.org>
My short definition is data tables are about logical relationships, layout tables are about visual relationnships. If each row can be thought of as an entity and each column as an attribute of that entity, it's a data table, otherwise it isn't. If yuou find yourself using the information to "look up" something, it's a data table. An address book with name, phone number, and address is a data table since it is used to "look up" someone's phone number and/or address by finding the name then scanning across to the required column. Business accounts are also data tables. Steve >>> Liz Roberts <liz@netlogix.net> 05/11/01 09:52AM >>> I have a few questions regarding table use & construction: First, as table use relates to sec 508, my understanding is that tables are not completely barred from use as a layout tool. Is this accurate? (Referring only to 508.) Second, what exactly defines a "data table"? For instance, how does a data table differentiate itself from a "layout table" that has a header graphic in the first row, navigation in the second, and content in the third. Could the first cell holding the header graphic be correctly labeled as a table header (<th>)? (What would be great is a test or syllogism of some sort which would help me clearly define data tables.) Third, are there screen readers that can utilize the "scope," "id," and "headers" attributes? How valuable are these additions? (And if anyone knows of a detailed tutorial on their use, I would greatly appreciate it; I'm getting better at reading the HTML spec, but there are limited examples.) Thank you, Liz
Received on Friday, 11 May 2001 11:37:52 UTC