If you are web developer then you have probably heard at some point NOT to use tables for layout. This has to do with best practices for website accessibility. But what really are the rules? The WC3 defines the table model as follows:
The HTML table model allows authors to arrange data — text, preformatted text, images, links, forms, form fields, other tables, etc. — into rows and columns of cells.
On the same page it also mentions that you should not use tables for layout:
Tables should not be used purely as a means to layout document content as this may present problems when rendering to non-visual media.
See W3C Definition.
With that being said, it is perfectly fine to use tables for textual data that can be organized into columns and rows. It is also fine if hyperlinks or image-links are included with the data (i.e., email links). Tables can also be used for input as well. Feel free to use textboxes, dropdowns and other form elements if they all tie to a single record of information.
So what about headers? Are they required? They are required if you are adhering to Section 508 standards for web accessibility:
(g) Row and column headers shall be identified for data tables
(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.
The presence of table headers help eliminate confusion for both visual and non-visual user agents. The "markup" mentioned above can be performed as follows:
Table Header or <th> cells have a
scopeattribute. It tells the screen reader whether the header is for a column (col) or for a row (row).
Table Data or td cells have a
headersattribute. It contains the id(s) of any <th> cells that apply to it, delimited by spaces.
Scope and headers fulfill the same function so you can choose one or the other. While screen readers may correctly guess whether a header is for a column or row based on table layout, clarifying with one of the above methods makes this unambiguous. However, Section 508 demands the markup if multiple headers are involved.
Abbreviations can also assist in markup:
<th abbr="Type">Type of Coffee</th>
<td><abbr title="Doctor">Dr.</abbr> Larry</td>
They can be used for clarification, space-saving (for minimalistic user agents), and repetitive rendering (i.e., speech synthesizers may restate the <th> abbreviated value before reading each associated <td> value).
Hopefully this helps clarify some questions and aids in future development.