W3C

WCAG WG weekly telecon

1 Sep 2005

Agenda

See also: IRC log

Attendees

Present
Tim_Boland, Andi_Snow_Weaver, Don_Evans, Christophe_Strobbe, Michael_Cooper, Matt_May, Wendy, Gregg_and_Ben, Takayuki_Watanabe, John_Slatin, Loretta_Guarino_Reid, Kate_Haritos-Shea, Roberto_Costaldo, Neil_Soiffer, Gian_Sampson-Wild, Bengt_Farre, Kerstin_Goldsmith, Makoto, Gian
Regrets
Yvette_Hoitink, Rob_Haverty, Roberto_Scano, Luca_Mascaro, Sebastiano, Nutarelli
Chair
Gregg
Scribe
ben, wendy

Contents


 

 

Techniques Task Force (TTF) update

<scribe> continued techniques harvesting prioritization and review

10.2 Mapping Proposal <http://tinyurl.com/c7mnq>

<wendy> chris' reasoning (to keep label positioning): http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JulSep/0198.html

<wendy> gez's feedback/position: http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JulSep/0199.html

<wendy> questions: 1. map 10.2 to 1.3 level 3 #1? if yes, done with mapping. 2. redefine prog. determined? if yes, accept ben's defn?

<wendy> Proposed wording programmatically determined means that the specific value can be determined in a standard and supported, machine or software readable form.

<wendy> Current wording programmatically determined means that the specific value can be determined in a standard, machine or software readable form.

issue: what is meant by "supported"? Is one screenreader enough?

<wendy> resolution: do not adopt proposed defn of programmatically determine b/c don't have defn of "supported" that isn't a "slippery slope."

resolution: map WCAG 1.0 Checkpoint 10.2 to advisory.

<scribe> ACTION: gian to look at proposal for new SC to address positioning of labels [recorded in http://www.w3.org/2005/09/01-wai-wcag-minutes.html#action01]

Guideline 3.2 proposed SC <http://tinyurl.com/7fs8x>

resolution: do not include proposed SC, "Within a set of delivery units, components that are rendered the same have the same function."

Plan to publish mapping/"heartbeat requirement" <http://tinyurl.com/7mgb2>

gv - mapping will be published as part of "heartbeat requirement" - i.e., have to publish docs on rec track every 3 months. will be published as appendix to next wcag 2.0 WD in september.

heartbeat requirement in w3c process: http://www.w3.org/2004/02/Process-20040205/groups.html#three-month-rule

Document formats and templates. Proposal: <http://tinyurl.com/9wv6c>

comments? gv will be republishing after this call (and will include comments sent to the list thus far)

techniques doc - "when does this tech work or not?" is that an applicability condition?

<scribe> ACTION: michael propose sentence about "applicabilty conditions" for doc formats and templates. [recorded in http://www.w3.org/2005/09/01-wai-wcag-minutes.html#action02]

resolution: adopt proposal as working documents and directions/templates.

Teams and assignments

resolution: we will move from old model (one Techniques Task Force working on techniques and tests) to new model (2 or 3 task forces working on end-to-end)

<gregg> http://www.w3.org/WAI/GL/2005/09/teamtf.html

<scribe> ACTION: wendy create 3 separate mailing lists (1 for each task force/team) (public-wcag-teama, public-wcag-teamb, public-wcag-teamc ?) [recorded in http://www.w3.org/2005/09/01-wai-wcag-minutes.html#action03]

Summary of Action Items

[NEW] ACTION: gian to look at proposal for new SC to address positioning of labels [recorded in http://www.w3.org/2005/09/01-wai-wcag-minutes.html#action01]
[NEW] ACTION: michael propose sentence about "applicabilty conditions" for doc formats and templates. [recorded in http://www.w3.org/2005/09/01-wai-wcag-minutes.html#action02]
[NEW] ACTION: wendy create 3 separate mailing lists (1 for each task force/team) (public-wcag-teama, public-wcag-teamb, public-wcag-teamc ?) [recorded in http://www.w3.org/2005/09/01-wai-wcag-minutes.html#action03]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.127 (CVS log)
$Date: 2005/09/02 16:37:05 $