W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2010

Re: Action Item H69

From: Sailesh Panchang <spanchang02@yahoo.com>
Date: Fri, 25 Jun 2010 06:49:12 -0700 (PDT)
Message-ID: <671559.14706.qm@web111703.mail.gq1.yahoo.com>
To: lorettaguarino@google.com, cooper@w3.org, caldwell@trace.wisc.edu, w3c-wai-gl@w3.org, befree@magma.ca
David,
Please refer to the concerns and wordings  in my emails on this topic and WCAG-WG responses. The following emails may help you to  improve the draft changes.
Emails from Sailesh Panchang <spanchang02@yahoo.com>
1. Saturday, February 28, 2009 12:16 AM
Re: Include H69 as technique for 2.4.6
Sent to public-comments-wcag20@w3.org

2. Fri, Nov 14, 2008 at 1:23 PM, 
Re: HTML Headings technique: duplicated
Sent to public-comments-wcag20@w3.org

3. Friday, November 9, 2007 11:48 AM
Re: Techniques doc WCAG 2: H42 and H69
Sent to public-comments-wcag20@w3.org

4. Wednesday, April 29, 2009 11:38 AM
Re: About techniques for SC 2.4.1
Emails sent to w3c-wai-gl@w3.org

Thanks,
Sailesh Panchang
Tel 571-344-1765
www.deque.com



 
  --- On Thu, 6/24/10, David MacDonald <befree@magma.ca> wrote:

From: David MacDonald <befree@magma.ca>
Subject: Action Item H69
To: lorettaguarino@google.com, cooper@w3.org, caldwell@trace.wisc.edu, w3c-wai-gl@w3.org
Date: Thursday, June 24, 2010, 10:42 PM


I had an action item to combine the existing H69 with the description text I had previously proposed for H42. Here is the proposal which would be the new description of H69... some 
Description
The objective of this technique is to use section headings to convey the structure of the content, and to create chunks of information that can be found easily by people with disabilities, such as a blind person using a screen reader, or a person with a cognitive disability who uses assistive technology that delineates groups of information, or someone with a communication disability or illiteracy, who uses a screen reader to assist them in their reading. Since headings indicate the start of important sections of content, it is possible for users with assistive technology to jump directly to the appropriate heading and begin reading the content. This significantly speeds interaction for users who would otherwise access the content slowly. Heading markup can be used to:

indicate start of main content
mark up section headings within the main content area
demarcate different navigational sections like top or main navigation, left or secondary navigation and footer navigation
markup images (containing text) which have the appearance of headings visually.
In (X)HTML, headings are designed to convey logical hierarchy. Skipping levels in the sequence of headings may create the impression that the structure of the document has not been properly thought through or that specific headings have been chosen for their visual rendering rather than their meaning. Authors are encouraged to nest headings hierarchically where the most important information is given the highest logical level, and subsections are given subsequent logical levels.(i.e., h2 is a subsection of h1). 
If the generic visual presentation of a particular heading level is not what is desired by the author (e.g., font size), Cascading Style Sheets (CSS) can be used to change the way headings look or sound. It is even possible to style headings using CSS so that they are exposed to assistive technology but are hidden from view visually. However, showing the headings visually benefits a wider set of users, including those with some cognitive disabilities. Be sure not to use CSS to mark up the <p> tag to look like a heading, because although it would visually look like a heading, assitive technology would not recognize it as such. Also, do not use heading markup to style text that is not a heading, because this would 
Add to related techniques
F2: Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text


      
Received on Friday, 25 June 2010 13:49:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 25 June 2010 13:49:49 GMT