See also: IRC log
1. proposal for script techniques (from becky) 2. testing scripts
3. reviewing test cases, closed some tests but not all.
4. responding to al's message re: hotkeys
<scribe> ACTION: john, wendy, gregg discuss relationship between test cases and relationship to success criteria in prep for agenda next week [recorded in http://www.w3.org/2005/08/18-wai-wcag-minutes.html#action01]
resolution: keep WCAG 1.0 Checkpoint 13.3 mapped to WCAG 2.0 Guideline 2.4 Level 2 Success Criterion #1
one suggestion to map to a Level 1 criterion, need to understand if now required at Level 1
resolution: keep WCAG 1.0 Checkpoint 10.1 mapped to WCAG 2.0 Guideline 3.2 (2 level 2 success criteria and one level 3 SC) [e.g., no change]
resolution: deprecate (per proposal, no change) WCAG 1.0 Checkpoint 10.4
may not want to deprecate, but say "no longer required for conformance"
from 04 august minutes: resolution: use "deprecated" for things we don't want people to do anymore and "not required" for things that WCAG 2.0 does not require for conformance, but may still appear in advisory
HTML defn of deprecated: http://www.w3.org/TR/html4/conform.html#deprecated
resolution: WCAG 1.0 Checkpoint 10.3 no longer required for conformance
2.2 (per proposal) or 3.2 (per comments)
related action item: http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JulSep/0296.html
"So it appears that most redirects are not covered by GL 2.2, and that auto-redirect without a timeout is covered by GL 3.2 L1 SC1."
map to both w/note that says "redirects w/timeout 2.2 applies, w/out timeout 3.2 applies"
restriction not to do it maps to level 3, detecting maps to level 1
resolution: map WCAG 1.0 Checkpoint 7.5 to WCAG 2.0 GL 3.2 L3 SC2
proposal - no longer required for conformance, refer to discussion about baseline and how to determine what falls in/out of baseline
resolution: mark WCAG 1.0 Checkpoint 11.1 as "no longer required for conformance" and note about advice to authors about choosing appropriate technologies as related to baseline
resolution: WCAG 1.0 Checkpoint 12.3 is no longer required for conformance, map to 3.1 advisory information (in the guide doc) - good practice encourage people to do as appropriate
resolution: WCAG 1.0 Checkpoint 13.2 no longer required for conformance, could be a technique for satisfying a 2.4 criteria, 4.2 criteria, or 1.3 criteria
discussion about use of title to describe relationships between frames
cncern about author's feeling they need to use longdesc (on frames)
proposal 1.3 and 2.4
title is a separate wcag 1.0 checkpoint
resolution: WCAG 1.0 Checkpoint 12.2 no longer required for conformance (because longdesc on frame has not been supported and is likely to disappear from spec)
3 people map to guideline 1.3, no sc, or 2.4
2 people guideline 1.3, l3, sc 1
proposal -- this is no longer required, but maybe new sc needed in 2.0 for positioning for magn. and cogn.
how do I put in an action item?
<wendy> ACTION: gian, alex, andi work on proposal for implicit labels and positioning of labels (as relates to WCAG 1.0 Checkpoint 10.2) [recorded in http://www.w3.org/2005/08/18-wai-wcag-minutes.html#action02]
No Resolution: no resolution, pending action item recorded
Resolution: map checkpoint 7.3 to checkpoint 2.2, L2, SC 2 (Note: until user agents clause has been satisfied, so it's no long necessary to avoid movement altogether, as long as authors don't do anything to interfere with the user's ability to pause the content)
Resolution: map checkpoint 8.1 to guideline 4.2, all of Level 1
resolution: wcag 1.0 checkpoint 5.5 is "no longer required for conformance"
Resolution: checkpoint 5.6 "no longer required for conformance" but a potentially useful technique