This table would be displayed as follows:
Spring Summer Autumn Winter
Betty 9 5 10 6
8 4
7 3
Wilma 10 6
10 6
9 5
9 5
Fred 10 6 10 6 10 6 10 6
The efficiency of using the scope attribute becomes more apparent in much larger tables. For
instance, if an agency used a table with 20 rows and 20 columns, there would be 400 data cells
in the table. To make this table comply with this provision without using the scope attribute
would require special coding in all 400 data cells, plus the 40 header and row cells. By contrast,
using the scope attribute would only require special
attributes in the 40 header and row cells.
Using the "ID" and "Headers" Attributes in Tables
Unlike using the "scope" attribute, using the "id" and "headers" attributes requires that every
data cell in a table include special attributes for association. Although its usefulness for
accessibility may have been diminished as browsers provide support for the "scope" attribute,
the "id" and "headers" attributes are still very useful and provide a practical means of providing
access in smaller tables.
The following table is much more complicated than the previous example and demonstrates the
use of the "id" and "headers" attributes and then the scope attribute. Both methods provide a
means of complying with the requirements for data tables in web pages. The table in this
example includes the work schedules for two employees. Each employee has a morning and
afternoon work schedule that varies depending on whether the employee is working in the
winter or summer months. The "summer" and "winter" columns each span two columns labeled
"morning" and "afternoon." Therefore, in each cell identifying the work schedule, the user needs
to be told the employee s name (Fred or Wilma), the season (Summer or Winter), and the shift
(morning or afternoon).
| |
| Winter |
| Summer |
| |
| Morning |
| Afternoon |
| Morning |
| Afternoon |
| Wilma |
| 9 11 |
| 12 6 |
| 7 11 |
National GACC Website and GACC Website Template
31
Implementation Guidelines