W3C

WCAG Weekly Telecon

9 Feb 2006

Agenda

See also: IRC log

Attendees

Present
David_MacDonald, Alex_Li, Michael_Cooper, Yvette_Hoitink, John_Slatin, Katie_Haritos-Shea, Gregg_Vanderheiden, Ben_Caldwell, Makoto_Ueki, Sofia_Celic, Andi_Snow_Weaver, Sorcha_Moore, Luca_Mascaro, Roberto_Ellero, Christophe_Strobbe, Cynthia_Shelly, Becky_Gibson, Loretta_Guarino_Reid, Bengt_Farre, Kerstin_Goldsmith, Judy_Brewer
Regrets
Roberto_Scano, Sebastiano_Nutarelli, Roberto_Castaldo
Chair
Gregg_Vanderheiden and John_Slatin
Scribe
Becky, Andi

Contents


Techniques for SC 1.3.1 from 26 January

<ben> scribe: Becky

Resolution: adopt all items where acceptance was unanimous except for edits. Items are:

SC2.4.2 Table of contents, General technique for SC 2.4.3: Skip to main content, SC 2.4.8 technique on breadcrumb trails, HTML technique for link element and navigation, Providing a submit button to initiate a change of context, Providing submit buttons in HTML, SC 1.3.1 Common Failure: Failure due to using space characters to format tables in simple text content, SC 1.3.1 Common Failure: Failure due to using space characters to create multiple columns in simple text content, Issue 1825

Using table, tr, and td elements for tabular information and Using th elements to identify column and row headers in data tables (but not in layout tables)

after brief discussion teamb has enough information to rework these examples.

Using caption elements to identify data tables (but not layout tables) (1.3.1 HTML technique)

<Zakim> Christophe, you wanted to say "caption also exists outside HTML"

<Christophe> ach chr

<Zakim> Yvette, you wanted to say "use applicability section of technique"

<sorcha> apologies - am having trouble with my telephone connection so have changed to skype

after discussion: keep caption and summary techniques separate but to cross reference them. Team b will rework.

Using id and headers attributes to associate data cells with header cells in data tables (but not in layout tables)

Team b will rework based on comments

HTML Tech - Using label elements to associate text labels with form fields

Resolution: Adopt HTML technique, Using label elements to associate text labels with form fields, with the suggested edits.

Tech - Using title attributes to label form controls that can't be individually labeled

Resolution: Adopt HTML technique, Using title attributes to label form controls that can't be individually labeled, with suggested edits.

HTML tech - Using ol, ul and dl for lists

<Zakim> Yvette, you wanted to say "sufficient but not necessary"

Resolution: Adopt HTML technique, Using ol, ul and dl for lists, with suggested edits.

HTML Technique, Using headings

<rellero> Sorry I have to leave, bye

<Zakim> Christophe, you wanted to say "remove reference to XHTML 2 because that spec will require a separate techniques document?"

Resolution: Send HTML Technique, Using Headings, back to team b: In addition to edits on survey: suggest new title "Using h for headings", suggested Update description that is best practice is to not skip numbers rather than requirement. Will remove any mention of hierarchy from the tests for this technique.

Using standard text formatting conventions for paragraphs

<jslatin> 9brb

Topic (cont): Using standard text formatting conventions for lists and Using standard text formatting conventions for headings

Resolution: accept 3 plain text techniques with suggested edits and the following ammendment: For plain text list technique. List items are paragraphs which begin with a asterisk or number.

Draft Techniques and Issues for Guideline 2.4 from 02 February

Proposal to delete 2.4.1

Subcommittee has been appointed to dicuss further.

General technique for Using a Site Map

Resolution: accept general technique, Using a Site Map, with edit process.

Proposal to change SC 2.4.3 wording

<Zakim> bengt, you wanted to say in another survey

A mechanism is available to bypass blocks of content that are repeated on multiple perceivable units."

resolution: change 2.4.3 wording to, "A mechanism is available to bypass blocks of content that are repeated on multiple perceivable units."

discuss requiring skip links to be visible as sufficient to meet 2.4.3

Will discuss when reach the Feb 9 2.4 survey

Proposal for SC 2.4.5 wording

<Andi> q

<Sofia> q

resolution: reject proposal to change the wording of 2.4.5.

Draft Techniques and proposals for Guideline 3.2 from 02 February

<Andi> scribe: Andi

resolution: 3.2.2 Changing the setting of any form control or field does not automatically cause a change of context unless the delivery unit contains instructions before the control that describe the behavior.

<Becky> q

resolution: Changing the setting of any form control or field does not automatically cause a change of context (beyond moving to the next field in tab order) unless the delivery unit contains instructions before the control that describe the behavior.

rationale: concern that putting the exception in the definition would allow moving the focus to the next field when a field receives focus (3.2.1)

<Zakim> Yvette, you wanted to ask "how long are we going to continue? I need to sleep soon"

resolution: 3.2.2 moves to Level 1
... keep failure technique with slight modification "Failure due to automatically submitting a form and presenting new content when the last field in the form is given a value without prior warning."

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.127 (CVS log)
$Date: 2006/02/15 21:12:43 $