Flintstone Tutor Schedule
Tutor Spring Summer Autumn Winter
  Morning Afternoon Morning Afternoon Morning Afternoon Morning Afternoon
Betty
9-12
No hours
10-11 None 10-12 None 10-11 None
Wilma
10-12
1-6 p.m.
 7-11 12-3 7-11 12-3 7-11 12-3
Fred
10 - 12
1-3 p.m.
9-11 12-5 9-11 12-5 9-11 12-5

Table Coded with "ID" and "Headers" tags

Tutor Winter Summer
  Morning Afternoon Morning Afternoon
Wilma 9-11 12-6 7-11 12-3
Fred 10-11 12-6 9-11 12-5

Note that in both instances the IBM Home Page Reader (HPR) only reads the column or row headers.  The same result is achieved regardless of whether

  1. the "scope" attribute is used in the table header <th scope="col">Summer</th> cells, or
  2. the more cumbersome "id" and "headers" attributes are used in the individual data cells.

Thus, the more cumbersome use of the "headers" and "id" attributes may add no new functionality for the text reader, depending on the make and model of the text reader being used.  The Access Board guidelines recognized this when it described the "scope" attribute as "effective."

 

"Using the "scope" attribute is one of the most effective ways of making HTML compliant with these requirements.

'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." (emphasis added)
http://www.access-board.gov/sec508/guide/1194.22.htm#(g)

 

 

Other Text Reader Navigation Factors -  Avoid "Nested Data Tables" (Not required by the 508 rules)

Text readers often have difficulty navigating through data tables "nested" inside "design tables", table templates. or other data tables.  Nesting makes it more difficult and sometimes impossible for text readers to navigate through embedded data tables. 

Users of the IBM Home Page reader have to use two navigation modes, "Table Jump" mode, and "Table Navigation" mode, to effectively find and scroll through nested tables on a web page.

The data tables above are not nested inside design tables or templates.  If possible use simple page designs and avoid complex page designs where data tables are presented.   While not required by the 508 Accessibility rules, eliminating "table nesting" improves text reader navigation through data tables.