WCAG WG telecon

2 Jun 2005


See also: IRC log


Wendy_Chisholm, Michael_Cooper, Joe_Clark, Bengt_Farre, John_Slatin, Yvette_Hoitink, Andi_Snow-Weaver, Alex_Li, Dave_MacDonald, Gregg_Vanderheiden, Ben_Caldwell, Christophe_Strobbe, Jason_White, Matt_May, Mike_Barta, Becky_Gibson
Makoto_UEKI, Sebastiano_Nutarelli, Roberto_Castaldo, Tim_Boland, Loretta_Guarino_Reid
John and Gregg


Summary of Resolutions

Related to Guideline 3.1

Summary of Action Items

Agenda review and announcements (5 minutes)

John goes through agenda and plan for the day.

Techniques Task Force (5 minutes)

mc: reviews for 4.2, 1.3, and 2.5. more work needed. expect emails on list. next week: scripts, scribe school, f2f prep

js: f2f agendas soon

GL 3.2 (25 minutes) http://tinyurl.com/bwbp9

john lists examples of extreme changes of context that he is concerned about.

discussion about "user-initiated extreme changes of context"

<scribe> ACTION: alex and mike rework proposals for 3.2 [recorded in http://www.w3.org/2005/06/02-wai-wcag-minutes.html#action01]

GL 4.1 (25 minutes) http://tinyurl.com/bp2yh

proposal 1 - 9 don't want

proposal 2 - 8 don't want

proposal 3 - 5 don't want

<scribe> ACTION: ben rework proposal for 4.1 based on feedback (either choose one approach and work into a proposal, or multiple). include "current wording" in survey. [recorded in http://www.w3.org/2005/06/02-wai-wcag-minutes.html#action02]

GL 3.1 (25 minutes) http://tinyurl.com/77h9g

john clarifies: readable means you can figure out words and sentences. understandable means you can comprehend what you're reading.

resolution: adopt proposed wording for Guideline 3.1 Make text content readable and understandable.

discussing: Proposed wording Level 1 SC2: A mechanism for finding the expanded form of acronyms and abbreviations is available

12 preferred proposed, 7 preferred current

examples: ibm (name), dvd (no longer stands for what it started out). are these still acronyms?

concern that discussion about acronym/abbreviation are important b/c they are structures in HTML. suggestion to not have anything specific about acronym and abbreviation because it is covered by "use according to spec." counter-example of "footnote" which is not an html structure that *is* available in pdf.

resolution: needs more work

discussing Proposed wording Level 3 SC3: Section headings and link text are understandable when read by themselves or as a group (for example in a list of links or a table of contents).

consider getting feedback about moving to level 2

joe doesn't support adopting proposed wording. response on survey was:

This remains a terrible and counterfactual idea, where we require X (coding according to spec and writing in a linearizable order) and anti-X (allowing any device to pull out content and remix it).

<jslatin> proposed l3 sc3 is authorial action to support UA function

resolution: (with objection) for Proposed wording Level 3 SC3: Section headings and link text are understandable when read by themselves or as a group (for example in a list of links or a table of contents). with the following actions:

<scribe> ACTION: john updated proposal for L3SC3 w/removal of "screen reader" and ask about moving to level 2. provide rationale for SC. [recorded in http://www.w3.org/2005/06/02-wai-wcag-minutes.html#action03]

GL 1.3 (25 minutes) http://tinyurl.com/dl25f

yvette proposes: ensure that the structure and function of the web content do not depend on the presentation

discussing - Proposed wording Level 1 SC2: Markup or coding is used to encode document semantics

10 preferred proposed wording, 3 preferred current wording

<scribe> ACTION: joe rework proposal for L1SC2, including a proposed defn of "document semantics" [recorded in http://www.w3.org/2005/06/02-wai-wcag-minutes.html#action04]

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.126 (CVS log)
$Date: 2005/06/02 23:09:40 $