See also: IRC log
<Becky> scribe: Becky
Resolution: Accept Failure due to using the onblur event to change the context as ammended
<scribe> ACTION: Cynthia to explore techs and examples of occluding overlays. Due March 30, 2006 [recorded in http://www.w3.org/2006/03/02-wai-wcag-irc]
Resolution: Accept Failure due to opening new windows that are not requested by the user, Note the name change.
<RylaDog> spec
<RylaDog> matches spec
<Zakim> Michael_Cooper, you wanted to say I'm a little lost now? my comments were different
Resolution: Accept Validating Delivery Units as ammended
Agenda item 2:
This topic has been resurveyed - will be discussed later in call
Resolution: Accept Using semantic elements to mark up structure.
Agenda item 3: GL 2.4 Techniques and Issues (Feb 23)
<RylaDog> http://www.w3.org/2002/09/wbs/35422/gl24feb23/results
Resolution: Accept Providing link text that describes the destination of a link as ammended.
Resolution: Accept Using the title attribute of the frame element
This has been removed as a failure and an new advisory technique, Failure due to providing adjacent image and text links that point to the same resource, has been created.
s/Combining adjacent image and text links for the same resource./Failure due to providing adjacent image and text links that point to the same resource
Resolution: Remove the failure and Accept new optional technique, Combining adjacent image and text links for the same resource.
not needed - accepted last week.
Agenda item 4: GL 3.1 Techniques and ssues (Feb 23)
Resolution: Accept Using a Unicode right-to-left mark (RLM) or left-to-right mark (LRM) to mix text direction inline. Team B will added the discussed tests.
<scribe> ACTION: Team B to define "nested directional run" And to run these directional related techniques by the I18N Working group. Due March 6, 2006. [recorded in http://www.w3.org/2006/03/02-wai-wcag-irc]
Resolution: Accept Using the dir attribute on an inline element to resolve problems with nested directional units.
<RylaDog> thanx andi
<RylaDog> yes
<RylaDog> def tag
<RylaDog> dfn yes
<Zakim> Christophe, you wanted to say: "title on span for definitions can be added in later version of tech docs, when AT starts supporting it - techs are not in Rec track to allow this
Related to this tech. Group is discussing whether or not a title on a span is a sufficient technique for 3.1.3.
<Zakim> Becky, you wanted to say HPR already supports this
<jslatin> Be Right Back
Resolution: Title on span is an advisory technique for 3.1.3 but will not publish the tech. in the next draft - it will remain as "title only". Will rediscuss after last call.
<Zakim> Michael_Cooper, you wanted to say second part of my comment was relevant
Resolution: Accept the structure and content of How to Meet Success Criterion 3.1.1 given the previous resolution about title on span.
... Add "or phrases" after words in 3.1.1. It now becomes, A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.
<ben> From 2.2 Surveys (both 23 Feb. and 02 Mar.)
<ben> Approved to publish with edits
<ben> * Failure caused by defaulting to non-conforming version as a result of content negotiation (4.2.1)
<ben> * Failure due to a script that causes a blink effect without a mechanism to stop the blinking at 3 seconds or less (2.2.2)
<ben> * Failure due to an object, such as Java or Flash, that has blinking content without a mechanism to pause the content that blinks for more than three seconds (2.2.2)
<ben> * Failure due to using server-side techniques to automatically redirect pages after a timeout (2.2.1)
<ben> * If users submit data when the user is no longer authenticated, the data is saved and the data is reused after the user re-authenticates (2.2.6)
<ben> * Making non-essential alerts optional (2.2.5)
<ben> * Providing a help link on every delivery unit (2.5.4)
<ben> * Providing client-side validation and alert (2.5.1, 2.5.2)
<ben> * Providing expected data format and example (2.5.4)
<ben> * Providing the ability for the user to review and correct answers before submitting (2.5.3)
<ben> * Providing the ability to recover the deleted information (2.5.3)
<ben> * Satisfying all WCAG success criteria at levels 1 and 2 that the technology outside the baseline can support (4.2.3)
<ben> * Using scripts to control blinking and stop it in three seconds or less (2.2.2)
<ben> Approved, no edits required
<ben> * Providing keyboard-controllable event handlers (2.1.1)
<ben> From 2.4 Survey (Feb 23)
<ben> Creating elements when creating new content, Failure due to the title of a delivery unit being the filename of the delivery unit or some other text that is not a title
<ben> unanimous items from 02 March glossary survey:
<ben> delete definition of "link", definition of programmatic reference, definition of structure, Editorial and formatting revisions to glossary
Resolution: Accept all items previous listed by Ben. These are items which are accepted via the surveys with only editoral comments.
Agenda item 5: Techniques for Guideline 2.2
<rscano> bye. good work!
<scribe> ACTION: Gregg, Yvette, and Andi to explore the issue of on-the-fly user agents and responsibility of authors. Due March 13, 2006. [recorded in http://www.w3.org/2006/03/02-wai-wcag-irc]
Accept Allowing the content to be paused and restarted from where it was stopped.
Resolution: Accept Allowing users to complete an activity without any time limit as ammended.
Agenda Item 6: Techniques from Team C for 02 March 2006
<ben> scribe: ben
<Zakim> Yvette, you wanted to say "failure due to having a session time-out that causes loss of user data"
<RylaDog> can you hrae me
resolution: Accept this technique with edits
resolution: replace this failure with two tech-specific examples (<blink> element and CSS text-decoration: blink)
<Michael> http://trace.wisc.edu/wcag_wiki/index.php?title=How_to_Meet_Success_Criterion_4.2.1
resolution: accept this technique with comments
... Split how to meet for this into two situations. (one for using a technology where a link to alternatives is accessible, another for using a technology where it is not possible to create an accessible link)
<scribe> ACTION: team c to clean up situations described above [recorded in http://www.w3.org/2006/03/02-wai-wcag-irc]
conforming version of a non-conforming page (4.2.1)
<scribe> ACTION: John and Michael to work on cleaning up concerns with, "Failure to provide a method for the user to find the alternative conforming version of a non-conforming page" [recorded in http://www.w3.org/2006/03/02-wai-wcag-irc]
resolution: accept this failure with edits, "Failure to provide a method for the user to find the alternative conforming version of a non-conforming page"
resolution: accept with edits
<scribe> ACTION: Makoto and John to discuss comments regarding color [recorded in http://www.w3.org/2006/03/02-wai-wcag-irc]
no resolution - need to discuss a proposal to remove this given concerns regarding search engine optimization
EO is working on proposals related to glossary proposals (to be sumbitted next week)
resolution: accept revisions to analog, time-dependent input as proposed by EO (Gregg's comments) with John's edits ("input whose result...")
<bengt> closest word to entity is thing
resolution: accept proposed revisions to "authored unit," as "set of material created as a single body by an author"
resolution: accept proposed definition of "baseline" without notes other than, "NOTE: For more information on Baselines and their use see http://www.w3.org/place-where-we-put-baseline-discussion-doc."
<gregg> ackkat
resolution: accept proposed definition of "caption" with editorial revisions from John and change "dialog" to "speech" -- "text presented and synchronized with multimedia to provide not only the speech, but also sound effects and sometimes speaker identification"
<Michael> I have to go catch that last bus. Although I was a lone "other" I thought my issues with the flash/luminosity ones were very important, so I hope they get enough discussion...
EO had questions about what would be excluded by proposed definition
<judy> "everything that the user agent uses to render presentation units"
<scribe> ACTION: Judy to take the above definition to EO for additional feedback [recorded in http://www.w3.org/2006/03/02-wai-wcag-irc]
resolution: accept "everything that the user agent uses to render presentation units" as definition with proposed note until we have something better
resolution: accept proposed definition of "general flash threshold" and expand "FPA" in parentheses in note.
<Zakim> judy, you wanted to comment on idiom
resolution: update definition of "idiom" to read, "a phrase whose meaning is not clear from the meaning of the individual words" and revise note with example to use "In US English, "kick the bucket" means "die."
resolution: accept proposed revisions to luminosity contrast ratio
<scribe> ACTION: Gregg to review EOWG comments and look at how to make it more human-readable [recorded in http://www.w3.org/2006/03/02-wai-wcag-irc]
<scribe> ACTION: team b to look at alternatives for definition of "perceivable structures" [recorded in http://www.w3.org/2006/03/02-wai-wcag-irc]
no resolution
resolution: accept proposed definition (same resolution as general flash threshold)
... accept definition of "technology" with editorial comments
resolution: accept proposal to make examples specific "example of Web page," "example of primary resource"
resolution, accept proposal to Replace "delivery unit" with "authored unit" in 3.2.2
resolution: back to team a
resolution: accept proposed revisions without the word content, "1.1.6 For prerecorded multimedia, a combined document containing captions intermixed with the audio description transcripts is available."