See also: IRC log
<scribe> continued techniques harvesting prioritization and review
<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]
resolution: do not include proposed SC, "Within a set of delivery units, components that are rendered the same have the same function."
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
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.
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]