See also: IRC log
<MichaelC> HTML A11Y TF wiki developing media accessibility requirements
<David> http://www.eramp.com/david/Media.html
<MichaelC> Survey for 24 June 2010
<David> The objective of this technique is to use HTML and XHTML heading markup to convey the structure of the content and to use headings 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...
<David> ...communication disability or illiteracy, who uses a screen reader to assist them in their reading.
<David> Using headings merely to change the appearance of text does not convey the organization of the content, and may confuse users who use headings to perceive structure or rely on them for navigation. Conversely, while applying bold format, or even "class=heading", can result in the visual display of a heading, assistive technologies will not recognize such text as headings.
<David> It is recommended that headings be presented in a hierarchical structure indicating top level section and subsections (i.e., h2 is a subsection of h1). Hierarchical presentation of heading markup is not always possible or practical for all design layouts and therefore not strictly required. However as a general rule, the most important information should be given the highest logical level,...
<David> ...and subsections should be give subsequent logical levels.
<scribe> ACTION: David to propose resolution for H69 [recorded in http://www.w3.org/2010/06/24-wai-wcag-irc]
<trackbot> Sorry, amibiguous username (more than one match) - David
<trackbot> Try using a different identifier, such as family name or username (eg. dmacdona, dtodd2)
<scribe> ACTION: DMacdona to propose resolution for H69 [recorded in http://www.w3.org/2010/06/24-wai-wcag-irc]
<trackbot> Created ACTION-98 - Propose resolution for H69 [on David MacDonald - due 2010-07-01].
RESOLUTION: Accept 2681 as amended
RESOLUTION: Accept as proposed
RESOLUTION: Accepted as amended
<Loretta> Giving users advanced warning when opening a new window
<scribe> ACTION: Dmacdona use example 4 to write up 'giving users advanced warning when opening a new window' [recorded in http://www.w3.org/2010/06/24-wai-wcag-irc]
<trackbot> Created ACTION-99 - Use example 4 to write up 'giving users advanced warning when opening a new window' [on David MacDonald - due 2010-07-01].
<Loretta> http://www.w3.org/WAI/GL/2010/WD-WCAG20-TECHS-20100617/G200
RESOLUTION: Reject new advisory technique
s/RESOLUTION: Reject new advisory technique in favor of modification of G200/RESOLUTION: Reject new advisory technique/
<scribe> ACTION: Andrew to send How to Meet wish list to Ben. [recorded in http://www.w3.org/2010/06/24-wai-wcag-irc]
<trackbot> Sorry, amibiguous username (more than one match) - Andrew
<trackbot> Try using a different identifier, such as family name or username (eg. akirkpat2, alahart)
<scribe> ACTION: akirkpat2 to send How to Meet wish list to Ben. [recorded in http://www.w3.org/2010/06/24-wai-wcag-irc]
<trackbot> Created ACTION-100 - Send How to Meet wish list to Ben. [on Andrew Kirkpatrick - due 2010-07-01].
<MichaelC> Flash techniques
<MichaelC> ARIA techniques
<scribe> ACTION: akirkpat2 to send michael rundown of files and what to link to for each technique [recorded in http://www.w3.org/2010/06/24-wai-wcag-irc]
<trackbot> Created ACTION-101 - Send michael rundown of files and what to link to for each technique [on Andrew Kirkpatrick - due 2010-07-01].
<MichaelC> Tracker items
<MichaelC> Updated participants list