Techniques doc WCAG 2: H42 and H69

Issue 1 for H42 and H69:
H42: Using h1-h6 to identify headings
H69: Providing heading elements at the beginning of
each section of content
Comment: It is unnecessary to have two techniques that
essentially  recommend the same thing.
Proposed: Merge H42 and H69 and incorporate
description of h69 within description for h42.
Also see issue #2 below.

Issue 2 for H42:
Under Description for H42, it states:
The objective of this technique is to use HTML heading
markup to convey the structure of the content. Heading
markup can be used: 
• to distinguish the main content from navigation
bars, graphical banners, footers, etc.
• to show the organization of material within the main
content 

Comment:
The first statement is apt. The remaining needs to be
changed as under.
Proposed:
Heading markup can be used: 
- to mark up section headings within the main content
area 
- to indicate start of main content  (*)
- to demarcate different navigational sections like
top or main navigation, left or secondary navigation
and footer navigation   (*)
- to markup images (containing text) which have the
appearance of headings visually. 

(*) In the absence of visible section headings, it is
possible to insert headings that are exposed to screen
reading software but are hidden from view using CSS.
Structure that is visually apparent can thus be
conveyed through screen reading software. 

Issue 3 for H42: 
In the description it states that it is not ok to skip
heading levels. So headings must be nested correctly.
This should be included as a test. It is missing now.
Proposed test 3:
Check that headings are nested sequentially and that
heading levels are not skipped. 

Sailesh Panchang
Deque Systems
www.deque.com
Phone 571-344-1765



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Received on Friday, 9 November 2007 16:49:30 UTC