|
|
|
|
|
Tables
Guideline
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
Intent
The intent of this regulation is to present tabular information in a way that preserves relationships within the information even when users cannot see the table or the presentation format is changed. Information is considered tabular when logical relationships among text, numbers, images, or other data exist in two dimensions (vertical and horizontal). These relationships are represented in columns and rows, and the columns and rows must be recognizable in order for the logical relationships to be perceived.
Using the element with the child elements , , and makes these relationships perceivable. Techniques such as inserting tabs to create columns or using the element are purely visual, and visually implied logical relationships are lost if the user cannot see the table or the visual presentation is changed.
Simple tables generally have only one level of headers for columns and/or one level of headers on the rows.
Usually, for simple tables, row 1 column 1 is either blank or describes the contents of the entire column 1. Row 1 columns are not blank (i.e. they contain "column headings"), describe the contents of the entire column, and allow the reader to distinguish the difference in meaning between that column and other columns.
Column 1 rows are usually not blank, they often contain "row headings" which describe the contents of the entire row, and allow the reader to distinguish the difference in meaning between that row and the other rows. Otherwise, the Column 1 would contain simple data.
Finding Applicable Components
- Check for the presence of tabular information.
- It may be necessary to use a tool, such as the "Show Data Tables" bookmarklet.
Inspecting and Using Components
- For each occurrence of tabular information:
- Check the table markup to ensure at least the , , , and elements are used.
- If the table used is a layout table, ensure that the attribute is set to and that the reading order is logical.
Section 508/WCAG 2.0 Failure Conditions
- A data table does not have its row and/or column header cells correctly marked programmatically.
- Fails 1194.22(g): Identify row and column headers.
- Fails 1.3.1 Info and Relationships.
Reporting Test Results
- Any failure in Section 508 Failure Conditions results in: Fails Baseline Requirement #13.
- Data tables have their row and/or column header cells correctly marked programmatically then: Passes Baseline Requirement #13.
See Also |