See also: IRC log
<Michael> scribe: Michael
<Andi> Hi Michael
hi Andi
1108 - agree needs clarification, TTF please do!
1110: suggest general technique about when refresh important and permitted - don't want to forbid e.g., status update functionality
<Andi> scribe: Andi
1243: Recommend considering technique submitted by Sofia http://trace.wisc.edu/wcag_wiki/index.php?title=Using_script_to_deactivate_blinking_content
1249: Agree with comments in issue. No changes necessary.
1251: dup of 1243
1243: Also consider technique documented in the issue
1274: OBE - no longer have SC having to do with following specifications.
1819: reject - it's a good idea to define a standard way for users to disable blinking but this is out of scope for WCAG.
1884: from security perspective, always require server-side validation. From accessibility perspective, though, requiring ssv is out of scope. It is a good idea to have server side validation techniques though so we recommend adding one. Client side or server side validation should be sufficient depending on the baseline.
1885: Recommend adding as an optional technique
1886: reject - the best way to identify errors could depend on context. We've done what we think we should in the SC and don't recommend any additional standardization.
1887: disagree with 1st paragraph - if provide
error notification in an accessible way as errors occur, this
could really benefit people with disabilities
... disagree with 2nd paragraphy - links to fields in errors is
a good idea but should not be forced upon all forms
... also recommend rejecting suggestion in 3rd paragraph -
doesn't fit the SC.
1889: reject - 2.5.1 does not require providing suggestions to correct the error. That's the fundamental difference between 2.5.2 and 2.5.1.
1890: investigate further - if popup window is a change of context, then remove the techniques. But if it is not a change of context, this should be allowed as it is similar to popups for logging in.
would be good if team members could look through wiki for 2.1, 2.2, 2.5, and 4.2 inserting notes if appropriate or starting a discussion on the mailing list.
<Michael> meeting: WCAG Team C teleconference
This is scribe.perl Revision: 1.127 of Date: 2005/08/16 15:12:03 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: Michael Inferring ScribeNick: Michael Found Scribe: Andi Inferring ScribeNick: Andi Scribes: Michael, Andi ScribeNicks: Michael, Andi Default Present: Michael_Cooper, Sofia_Celic, Andi_Snow_Weaver, [IPcaller], Tim_Boland, Makoto_Ueki Present: Michael_Cooper Sofia_Celic Andi_Snow_Weaver [IPcaller] Tim_Boland Makoto_Ueki Agenda: http://lists.w3.org/Archives/Public/public-wcag-teamc/2006Jan/0035.html Got date from IRC log name: 16 Jan 2006 Guessing minutes URL: http://www.w3.org/2006/01/16-wcag-teamc-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]