WCAG 2.0 Weekly Meeting (marathon)

Guideline 4.1

<ben> survey results: http://www.w3.org/2002/09/wbs/35422/use-spec2/results

<wendy> An SGML content model cannot be ambiguous. Every element or character found in the document instance must be able to satisfy only one content token without looking ahead in the document instance. (from http://www.is-thought.co.uk/book/sgml-5.htm#Ambiguous)

Not all tags need to be present in a document. Provided that the OMITTAG feature has been enabled in the SGML declaration, tags can be omitted when their presence can be implied without ambiguity. (from http://www.is-thought.co.uk/book/sgml-5.htm#Use)

<wendy> The most commonly used form of minimization is tag omission. This optional SGML feature allows tags to be omitted when their presence can be unambiguously implied by the program from the structure of the document declared in the document type definition. (from http://www.is-thought.co.uk/book/sgml-9.htm#OMITTAG)

<bengt> deterministic see http://www.nist.gov/dads/HTML/deterministc.html

<wendy> http://en.wikipedia.org/wiki/Parse

<ben> proposed: parsed unambiguously

<ben> Parsing transforms markup or other code into a data structure, usually a tree, which is suitable for later processing and which captures the implied hierarchy of the input. Parsing unambiguously means that there is only one data structure that can result.

resolution: Resolution: Accept Solution 2 for the next draft.
... "Parsing transforms markup or other code into a data structure, usually a tree, which is suitable for later processing and which captures the implied hierarchy of the input. Parsing unambiguously means that there is only one data structure that can result."

resolution: accept definition of parsing as follows: "Parsing transforms markup or other code into a data structure, usually a tree, which is suitable for later processing and which captures the implied hierarchy of the input. Parsing unambiguously means that there is only one data structure that can result."
... adopt wording for 4.1 L1 SC1 "Delivery units can be parsed unambiguously."
... adopt wording for 4.1 L1 SC1 "Delivery units can be parsed unambiguously." for the next draft.

Luminosity 1.4 contrast foreground and background

<ben> survey results: http://www.w3.org/2002/09/wbs/35422/2005-11-10s1/results

Resolution: delete the sufficient technique of having no background specified 1.4 L2 SC1
... have a sufficient technique for 1.4 L2 SC1 and L3 SC1 not specifying background color and not specififying text color AND delete the sufficient technique of having no background specified 1.4 L2 SC1 and L3 SC1
... delete the word "minimum" from L2 SC1 and L3 SC1 of GL 1.4

<scribe> ACTION: Gregg will work with Yvette and Makoto, Christophe to find an easier way say "Luminosity" in 1.4 L2 SC1 [recorded in http://www.w3.org/2005/11/10-wai-wcag-irc]

<scribe> ACTION: Gregg will see if he can add text to the intent of 1.4 L2 SC1 to give background on the definition of luminosity [recorded in http://www.w3.org/2005/11/10-wai-wcag-irc]

resolution: accept GL 1.4 L2 SC1 and L3 SC1 and their guide docs

GL 2.3 L1 SC1

resolution: add sufficient technique for GL 2.3 L1 SC1 and L2 SC2 - Providing a means to disable or turn off the provacative information before encountering it

<scribe> ACTION: Gregg - add benefits to GL 2.3 L1 SC1 [recorded in http://www.w3.org/2005/11/10-wai-wcag-irc]

proposed: when content violates .... users are warned in a way that they can avoid it

resolution: change GL 2.3 L1 SC1 to "When content violates either the general flash threshold or the red flash threshold, users are warned in a way that they can avoid it.

<scribe> ACTION: Tim to propose GL 2.3 SC that addresses provision of alternative equivalent content. [recorded in http://www.w3.org/2005/11/10-wai-wcag-irc]

<Zakim> Yvette_Hoitink, you wanted to ask "is allowing to switch off sufficient for L2?"

Tim to look at GL 4.2 to see if the issue is covered there

resolution: Modify last resolution - do not add sufficient technique to GL 2.3 L2 SC1 - Providing a means to disable or turn off the provocative information before encountering it.

s/and L2 SC1/and L2 SC2/

<bengt> im against provocative since its value can imply censoring

resolution: modify "general flash threshold" and "red flash threshold" definitions change "is not permitted when" to "where"
... adopt John's suggestions for edits to intent section.

<gregg> change sufficent technique to read "Content has been tested and does not violate the general flash threshold or red flash threshold (See resources for Tools)" and move reference to Trace tool to resources.

resolution: Modify GL 2.3 L2 SC1 sufficient technique to remove reference to Trace tool. Replace with "Content has been tested and does not violate general flash threshold or red flash threshold (See reources for tools)" and move reference to Trace tools to resources.
... adopt GL 2.3 L1 SC 1 and L2 SC 1 and their guide docs as modified by resolutions.

GL 2.4 L2 SC 1

resolution: modify GL 2.4 L2 SC1 to "More than one way is available to locate content within a set of delivery units where content is not the result of, or a step, in a process or task."

s/or a step in,/or a step in,/

resolution: adopt GL 2.4 L2 SC1 and it's guide as amended by resolutions.

Katie wants to amend their survey results - can live with proposed wording

GL GL 2.4 L2 SC4

<gregg> Each programmatic reference to another delivery unit or to another location in the same delivery unit is associated with text describing the destination.

resolution: adopt proposed language for GL 2.4 L2 SC4 with an ed note that describes the question group has with regard to what "associated" means and how tight the association has to be. "Each programmatic referece to another delivery unit or to another location in the same delivery unit is associated with text describing the destination."
... adopt GL 2.4 L2 SC4 and it's guide doc as amended by resolutions.

GL 1.3 L1 SC2 - proposal to delete and to promote GL 1.3 L2 SC2 to Level 1

<ben> survey results: http://www.w3.org/2002/09/wbs/35422/2005-11-10s2/results

proposed GL 1.3 L1 SC2 text: When information is conveyed by color, the information is also conveyed through another means that does not depend on the user's ability to differentiate colors.

proposal for GL 1.3 L1 SC2 text: When information is conveyed by color, the information is also conveyed through another means that does not depend on color.

Resolution: accept new text for GL 1.3 L1 SC2: When information is conveyed by color, the information is also conveyed through another means that does not depend on color.

GL 2.2 L1 SC1

<gregg> In response to becky's question about whether HTTP Refresh techniques are needed, I'd suggest that we generalize these to say something like "using server-side techniques to automatically redirect pages after a timeout." (not sure, but I think ASP can be used create this same issue)

Resolution: adopt Ben's comment to generalize HTTP refresh techniques to say something like, "using server-side techniques to automatically redirect pages after a timeout."

Resolution: add the following editorial note to GL 2.2 L1 SC1: The Working Group is considering adding techniques and/or modifying the success criterion to ensure addtional accessibility features are employed for events where no alternative to a timeout is possible or where timing is essential.

Resolution: Accept GL 2.2 L1 SC1 and its Guide doc with the editorial note resolved upon above.

Consider Promotion of Guideline 2.2 Level 3 Success Criterion 3 to Level 2

Action: Gian continue action item to find techniques that do not require specific technologies not commonly in the baseline to implement. [recorded in http://www.w3.org/2005/11/11-wai-wcag-minutes.html#action01]

Resolution: accept GL 2.2 L3 SC3 and its Guide Doc

Guideline 1.2

Resolution: Replace current editorial note with new text: "Working group is seeking comment on the following proposal for GL 1.2 (paste proposal from survey)"

Resolution: Accept Guide doc for GL 1.2 L1 SC1.

Resolution: Accept Guide doc for GL 1.2 L1 SC2

SC text and Guide Doc for GL 2.1 L1 SC1

Resolution: Accept Success criterion and Guide doc for GL 2.1 L1 SC1 with suggested editorial changes.

definition of programmatically determined

Resolution: accept definition of programmatically determined as, "can be recognized by user agents, including assistive technologies, that support the technologies in the chosen baseline" and remove the editorial note.

2.4 L1 SC1

<ben> results: http://www.w3.org/2002/09/wbs/35422/2005-11-10s3/results

resolution: accept the sc and guide doc as edited "Navigational features within the content can be programmatically determined." and Adopt alternate definition from the F2F . 2.4 L1 SC1

resolution: unanimous consent the wording of GL L SC1 changed to read "perceivable structures within the content can be programmatically determined."
... accept guide doc as edited, GL 1.3 L1 SC1

1.3 L3

resolution: adopt Christophe's edit to 1.3 L3 SC2 "Information required to understand and operate content does not rely solely on shape, size, visual location or orientation of components."
... adopt 1.3 L3 SC2 guide doc as edited

1.3 L3 SC1

resolution: change "determined programatically" to "programatically determined"
... change "determined programatically" to "programatically determined" 1.3 L3 SC1
... accept Guide doc for 1.3 L3 SC1 as edited

Guideline 3.1

GL 3.1 L1 SC3

<ben> survey: http://www.w3.org/2002/09/wbs/35422/meaning20051014/results#xL3SC2

resolution: adopt guide doc as edited GL 3.1 L 3 SC 1
... adopt guide doc as edited GL 3.1 L 3 SC 1 (restricted words-unusual words)

3.1 L3 SC3

3.1 L3 SC3

Resolution: accept edits for GL 3.1 L3 SC3 (acronym expansions)
... accept guide doc edits for GL 3.1 L3 SC3
... adopt edited guide doc for 4.2 L1 SC2

<ben> resolution: * The content and properties of user interface elements that can be changed via the user interface can also be directly changed programmatically.

<ben> NOTE: Some examples of standardized properties that typically can be changed by the user interface include its value, whether it is currently selected, and whether it currently has the focus.

resolution: adopt the wording for SC 4.2 L1 SC 5 "The content and properties of user interface elements that can be changed via the user interface can also be directly changed programmatically. " with the ednote:
... adopt edited guide doc for Accept 4.2 L1 SC6?

Baseline

<ben> GV's post: http://lists.w3.org/Archives/Public/w3c-wai-gl/2005OctDec/0469.html

baseline doc, change conformance section to say Baselines are a set of technologies but the claim would state its baseline, say what else it used beyond the baseline, but what it relied on wa optiional,

resolution: adopt the proposed rewording to conformance section to relect that baseline is what is requied and relied is optional
... ednote: the working group s developing language to distinguish between web content and downloaded files which is not content...
... The Working Group is developing language to differentiate between Web content on the one hand and downloaded files and other non-Web content on the other.
... The Working Group is developing language to differentiate between Web content on the one hand and downloaded software and other non-Web content on the other.

Motion: to authorize the editors to make any additional cleanup needed to prepare the document with notification to the working group of any non-editorial changes

resolution: unanimous. to authorize the editors to make any additional cleanup needed to prepare the document with notification to the working group of any non-editorial changes