W3C

- DRAFT -

Web Content Accessibility Guidelines Working Group Teleconference

05 Jul 2012

Agenda

See also: IRC log

Attendees

Present
Kathy, Peter_Korn, Robin_Tuttle, Cooper, Alex_Li, Gregg_Vanderheiden, Bruce_Bailey, +1.703.227.aaaa, Katie_Haritos-Shea, Loretta_Guarino_Reid, James_Nurthen, Andi_Snow-Weaver, adam_solomon
Regrets
Moe_Kraft
Chair
Loretta_Guarino_Reid
Scribe
Kathy, Andi

Contents


<trackbot> Date: 05 July 2012

<MichaelC> scribe: Kathy

http://tinyurl.com/7jtpema

<Loretta> http://www.w3.org/WAI/GL/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html

<Loretta> items that share a common characteristic are organized into tabular rows and columns;

SC 3.1.2 in Understanding WCAG 2.0

Resolution: do not accept, language in their own glyphs cannot be blank to a screen reader.

SC 1.3.1 in Understanding WCAG 2.0

<greggvanderheiden> Sighted users perceive structure through various visual cues — headings are often in a larger, bold font separated from paragraphs by blank lines; list items are preceded by a bullet and perhaps indented; paragraphs are separated by a blank line; items that share a common characteristic are organized into tabular rows and columns with their headers; form fields may be positioned as groups that share text labels; a different background

<greggvanderheiden> color may be used to indicate that several items are related to each other; words that have special status are indicated by changing the font family and /or bolding, italicizing, or underlining them and so on. Having this structure and these relationships programmatically determined or available in text ensures that information important for comprehension will be perceivable to all.

<greggvanderheiden> There may also be cases where it may be a judgment call as to whether the relationships should be programmatically determined or be presented in text. However, when technologies support programmatic relationships, it is strongly encouraged that information and relationships be programmatically determined rather than described in text.

RESOLUTION: replace the seventh paragraph with "There may also be cases where it may be a judgment call as to whether the relationships should be programmatically determined or be presented in text. However, when technologies support programmatic relationships, it is strongly encouraged that information and relationships be programmatically determined rather than described in text.

<Loretta> Sighted users perceive structure through various visual cues — headings are often in a larger, bold font separated from paragraphs by blank lines; list items are preceded by a bullet and perhaps indented; paragraphs are separated by a blank line; items that share a common characteristic are organized into tabular rows and columns <ins>

<greggvanderheiden> Sighted users perceive structure through various visual cues — headings are often in a larger, bold font separated from paragraphs by blank lines; list items are preceded by a bullet and perhaps indented; paragraphs are separated by a blank line; items that share a common characteristic are organized into tabular rows and columns WITH THEIR HEADERS; form fields may be positioned as groups that share text labels; a different background

<greggvanderheiden> color may be used to indicate that several items are related to each other; words that have special status are indicated by changing the font family and /or bolding, italicizing, or underlining them and so on. HAVING THIS STRUCTURE AND THESE RELATIONSHIPS PROGRAMMATICALLY DETERMINED OR AVAILABLE IN TEXT ENSURES THAT INFORMATION IMPORTANT FOR COMPREHENSION WILL BE PERCEIVABLE TO ALL.

<greggvanderheiden> Sighted users perceive structure through various visual cues — headings are often in a larger, bold font separated from paragraphs by blank lines; list items are preceded by a bullet and perhaps indented; paragraphs are separated by a blank line; items that share a common characteristic are organized into tabular rows and columns WITH THEIR HEADERS; form fields may be positioned as groups that share text labels; a different background

<greggvanderheiden> color may be used to indicate that several items are related to each other; words that have special status are indicated by changing the font family and /or bolding, italicizing, or underlining them and so on. HAVING THIS STRUCTURE AND THESE RELATIONSHIPS PROGRAMMATICALLY DETERMINED OR AVAILABLE IN TEXT ENSURES THAT INFORMATION IMPORTANT FOR COMPREHENSION WILL BE PERCEIVABLE TO ALL.

<greggvanderheiden> There may also be cases where it may be a judgment call as to whether the relationships should be programmatically determined or be presented in text. However, when technologies support programmatic relationships, it is strongly encouraged that information and relationships be programmatically determined rather than described in text.

RESOLUTION: 2nd paragraph gets replaced with “Sighted users perceive structure through various visual cues — headings are often in a larger, bold font separated from paragraphs by blank lines; list items are preceded by a bullet and perhaps indented; paragraphs are separated by a blank line; items that share a common characteristic are organized into tabular rows and columns with their headers; form fields may be positioned as groups that share text labels; a different background color may be used to indicate that several items are related to each other; words that have special status are indicated by changing the font family and /or bolding, italicizing, or underlining them and so on. HAVING THIS STRUCTURE AND THESE RELATIONSHIPS PROGRAMMATICALLY DETERMINED OR AVAILABLE IN TEXT ENSURES THAT INFORMATION IMPORTANT FOR COMPREHENSION WILL BE PERCEIVABLE TO ALL.

1.1.1 Non-text Content

<Andi> THAT INFORMATION IMPORTANT FOR COMPREHENSION WILL BE PERCEIVABLE TO ALL.|

RESOLUTION: accept as proposed

RESOLUTION: accepted the following unanimous consent as approved 1.2.1, 1.2.3, 1.2.5, 1.3.3, 1.4.1, 1.4.5, 2.3.1, 2.4.4, 2.4.7

1.2.2 Captions (Prerecorded)

<korn> "Note: a standalone player that is absent the presence of pre-recorded media is outside of the scope of this provision."

<robin> apologies, i must drop off

RESOLUTION: approved with the following note removed. “Note: Requirements for ability of players or viewers to support captions for media being played or viewed is not within WCAG's scope and would have to be required in some other fashion than WCAG SC.”

1.2.4 Captions (Live)

RESOLUTION: approved with the following note removed. “Note: Requirements for ability of players or viewers to support captions for media being played or viewed is not within WCAG's scope and would have to be required in some other fashion than WCAG SC.”

1.4.4 Resize text

<Loretta> If an application replies upon a platform capability to meet this success criterion, then the application supports that platform capability.

<greggvanderheiden> NOTE: If a platform capability is relied upon, the application implies that it supports the platform capability.

<Loretta> If an application relies upon such a platform capability to meet this success criterion, then the application enables the user to access that platform capability.

<greggvanderheiden> If a platform capability is relied upon, it means that the application supports the platform capability.

RESOLUTION: Accept without the sentence "If a platform capability is relied upon, the application supports the platform capability." Taskforce is invited to clarify the sentence or reword as they see fit.

2.1.1 Keyboard

<korn> So the second paragraph would now read:

<korn> Note: This does not imply that software must directly support OR PROVIDE a keyboard or "keyboard interface". UNDERLYING Platform software may provide device independent input services to applications that enable operation via a keyboard. Software that supports operation via such platform device independent services would be operable by a keyboard and would comply.

RESOLUTION: Accepted with the following change: “Note: This does not imply that software must directly support or provide a keyboard or "keyboard interface". Underlying platform software may provide device independent input services to applications that enable operation via a keyboard. Software that supports operation via such platform device independent services would be operable by a keyboard and would comply.”

2.1.2 No Keyboard Trap

RESOLUTION: accept as proposed

<korn> +1

2.2.1 Timing Adjustable

<Zakim> MichaelC, you wanted to jump to my comments in the last question - which I shouldda before

<Loretta> :-)

<Andi> scribe: Andi

RESOLUTION: Accept 2.2.1 with last sentence removed ("Non-web Electronic Documents ... there are no time limits."). Task force is invited to re-word last sentence and re-submit.

2.2.2 Pause, Stop, Hide

RESOLUTION: Accept 2.2.2 as amended by Michael's edit.

2.4.6 Headings and Labels

RESOLUTION: Send 2.4.6 back to the task force based on comments related to the use of heading.

3.2.1 On focus

RESOLUTION: Accept 3.2.1 with last sentence removed. ["For non-web electronic documents without interactivity beyond hyperlinks - (no scripting or programming) - this SC would be automatically met."] The task force may wish to come back with a proposal to modify WCAG 2.0 intent.

3.2.2 On Input

RESOLUTION: Accept 3.2.2 with last sentence removed. ["For non-web electronic documents without interactivity beyond hyperlinks - (no scripting or programming) - this SC would be automatically met."] The task force may wish to come back with a proposal to modify WCAG 2.0 intent.

<korn> Keep: This applies directly as written, and as described in INTENT from Understanding WCAG 2.0  (above).

<korn> THrow away all after that.

3.3.1 Error Identification

RESOLUTION: Accept 3.3.1 with last two paragraphs removed. Task Force should consider proposing new text for Understanding WCAG instead of the note.

3.3.4 Error Prevention (Legal, Financial, Data)

RESOLUTION: Accept 3.3.4 with last sentence removed. ["For non-web electronic documents without interactivity beyond hyperlinks - (no scripting or programming) - this SC would be automatically met."] The task force may wish to come back with a proposal to modify WCAG 2.0 intent.

4.1.1 Parsing

RESOLUTION: Not accept 4.1.1.

<scribe> ACTION: Peter to work with Bruce, Michael, Loretta, and James to draft new proposal for 4.1.1 [recorded in http://www.w3.org/2012/07/05-wai-wcag-minutes.html#action01]

<trackbot> Created ACTION-175 - Work with Bruce, Michael, Loretta, and James to draft new proposal for 4.1.1 [on Peter Korn - due 2012-07-12].

4.1.2 Name, Role, Value

RESOLUTION: Accept 4.1.2 with last sentence removed. ["For non-web electronic documents without interactivity beyond hyperlinks - (no scripting or programming) - this SC would be automatically met.]

General feedback for the WCAG2ICT Task Force

RESOLUTION: Send comments from the survey to the task force

Summary of Action Items

[NEW] ACTION: Peter to work with Bruce, Michael, Loretta, and James to draft new proposal for 4.1.1 [recorded in http://www.w3.org/2012/07/05-wai-wcag-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.136 (CVS log)
$Date: 2012/07/11 19:39:31 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/second/seventh/
Succeeded: s/Resolution:/RESOLUTION:/
Succeeded: s/seventh paragraph with There may/seventh paragraph with "There may/
WARNING: Bad s/// command: s/share text labe/share text labels; a different background color may be used to indicate that several items are related to each other; words that have special status are indicated by changing the font family and /or bolding, italicizing, or underlining them and so on. HAVING THIS STRUCTURE AND THESE RELATIONSHIPS PROGRAMMATICALLY DETERMINED OR AVAILABLE IN TEXT ENSURES THAT INFORMATION
Succeeded: s|groups that share text labe|groups that share text labels; a different background color may be used to indicate that several items are related to each other; words that have special status are indicated by changing the font family and /or bolding, italicizing, or underlining them and so on. HAVING THIS STRUCTURE AND THESE RELATIONSHIPS PROGRAMMATICALLY DETERMINED OR AVAILABLE IN TEXT ENSURES|
Succeeded: s/AVAILABLE IN TEXT ENSURES/AVAILABLE IN TEXT ENSURES THAT INFORMATION IMPORTANT FOR COMPREHENSION WILL BE PERCEIVABLE TO ALL./
WARNING: Bad s||| command: s|s/share text labe/share text labels; a different background color may be used to indicate that several items are related to each other; words that have special status are indicated by changing the font family and /or bolding, italicizing, or underlining them and so on. HAVING THIS STRUCTURE AND THESE RELATIONSHIPS PROGRAMMATICALLY DETERMINED OR AVAILABLE IN TEXT ENSURES THAT INFORMATION
Succeeded: s/thanks Andi//
Succeeded: s/]"For/["For/
Succeeded: s/]"For/["For/
Succeeded: s|may wish to come back with a proposal to modify WCAG 2.0 intent.||
Succeeded: s/: SC 3.1.2/SC 3.1.2/
Succeeded: s/Hi Zakim, Oracle is Peter_Korn//
Succeeded: s/<topic>: SC 3.1.2 in Understanding WCAG 2.0//
Found Scribe: Kathy
Inferring ScribeNick: Kathy
Found Scribe: Andi
Inferring ScribeNick: Andi
Scribes: Kathy, Andi
ScribeNicks: Kathy, Andi
Default Present: Kathy, Peter_Korn, Robin_Tuttle, Cooper, Alex_Li, Gregg_Vanderheiden, Bruce_Bailey, +1.703.227.aaaa, Katie_Haritos-Shea, Loretta_Guarino_Reid, James_Nurthen, Andi_Snow-Weaver, adam_solomon
Present: Kathy Peter_Korn Robin_Tuttle Cooper Alex_Li Gregg_Vanderheiden Bruce_Bailey +1.703.227.aaaa Katie_Haritos-Shea Loretta_Guarino_Reid James_Nurthen Andi_Snow-Weaver adam_solomon
Regrets: Moe_Kraft
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2012JulSep/0002.html
Found Date: 05 Jul 2012
Guessing minutes URL: http://www.w3.org/2012/07/05-wai-wcag-minutes.html
People with action items: peter

[End of scribe.perl diagnostic output]