WCAG Weekly Telecon

SC 1.3.1 Failures (March 30)

<Andi> scribe:

<Andi> scribe: Andi

resolution: accept How to Meet Success Criterion 2.3.2, Understanding 1.3, 1.4, 2.2, 2.3, 2.5, 3.1, 4.2 with edits by consent decree

Failure due to using scripting events instead of anchors to create links

<scribe> scribe: David_MacDonald

resolution: accept SC 1.3.1 , adopt with edits except for the last item... except the end of Michael recommendation starting at "another related situation..."

sc 1.3.1 Failure due to using structural markup in a way that does not represent relationships in the content

<scribe> ACTION: Andi to add a line in the wording of the text of the Failure technique to ensure that the failure does not cover layout tables [recorded in http://www.w3.org/2006/03/30-wai-wcag-irc]

resolution: adopt sc 1.3.1 Failure due to using structural markup in a way that does not represent relationships in the content with Andi's edit to the language in the description to make sure it does not apply to layout tables

2.4.4 Failure: Failure due to not programmatically associating a link with text which its purpose can be determined

<Zakim> Yvette, you wanted to say "failure due to not including a description of a link"

resolution: do not adopt the failure 2.4.4 Failure: Failure due to not programmatically associating a link with text which its purpose can be determined. And adding a line in the example of the parent element example that says that preceeding parent element must contain the link or it is not a parent.

how to meet doc....1.2.2

How to Meet Documents for 1.2.2 and 2.3.2 and Text of Guideline 4.1

<Zakim> Yvette, you wanted to ask for clarification

resolution: accept how to meet sc 1.2.2
... accept John's definition of fully corrected screenplay with the old note about "a screenplay used to create removing "as it occurred and"

<Sorcha> IP caller is Sorcha Moore, Segala

resolution: accept how to meet 1.2.2 with John's intent edit

<Andi> scribe: Andi

How to meet SC 2.3.2

resolution: accept "How to meet 2.3.2" with edits

Revised proposal for 4.1.2

resolution: accept reworded guideline 4.1 Support compatibility with current and future user agents

(including assistive technologies)

definition of "publicly documented" that is included in the note for the definition of "programmatically set"

<ben> current definition: http://www.w3.org/WAI/GL/WCAG20/appendixA.html#programmaticallydetermineddef

<judy> http://www.w3.org/Consortium/Patent-Policy-20030520.html

<judy> sorry, updated version: http://www.w3.org/Consortium/Patent-Policy-20040205/

<gregg> ACK

resolution: roll call vote to open up normative definitions of "programmatically set" and "programmatically determined"

<judy> +1 on being careful on terminology & intent

<gregg> set by software using methods that are user-agent-supported

proposal for definition of "programmatically set" - "set by software using methods that are user-agent-supported"

proposal for definition of "programmatically determined" - "determined by software from data provided in a user-agent-supported manner such that the user agents can extract and present this information to users in different modalities"

amend proposals on definition of "programmatically set" and "programmatically determined" - add and address issue of the availability of the APIs in the information on choosing a baseline.

resolution: accept proposal to remove "publicly documented" from definitions of "programmatically set" and "programmatically determined" and address issue of the availability of interfaces to the information on choosing a baseline.

Understanding guideline 1.1

resolution: accept "Understanding guideline 1.1" with edits
... accept all "Understanding guideline x.y" documents with edits

Failure due to omitting the alt-attribute for non-text content used for decorative purposes only in HTML

resolution: accept with edits
... accept