See also: IRC log
mc: went through requirements document. lots of
clean up.
... most work needed for guide/general split
... will send draft in next week
... getting back to reviewing test cases. will start polls soon.
... next week - more about testing and test suites.
... and scripting
... talked w/peter-paul and expecting some materials from him
resolution: we'll meet in seattle 17-20 october
1.0 specifically lists ascii art which was lost from defn of non-text content
add "this includes ascii art" to "non-text content used to convey information - content that communicates ideas, data, facts [@@include info from definition of information] and is not text."
(proposal)
isn't ascii art a sequence of unicode characters?
replace "or sequence" with "or meaningful sequence"
resolution: replace defn of non-text content
with "Content that is not represented by a Unicode character or sequence of
Unicode characters. This includes ASCII Art which is a pattern of
characters."
... add to mapping for functional non-text content, also link to guideline
4.2
... images used as bullets is also covered in guideline 1.3 wrt css usage
frame title maps to 2.4. no longer recommending noframes? therefore, not map to anything else?
noframes no longer required (map to deprecated html techs?). see 2.4 regarding descriptive titles of delivery units
resolution: noframes longer required.
... add "for video, alternatives (beyond labels) are covered under 1.2"
no change. all agree appropriate.
resolution: note - identification of the language for individual words no longer required
some things, even though possible, if not done in a standard and supported way "don't count"
e.g. programmtically determined means "standard and supported"
resolution: baseline dependent - if style sheets are in your baseline, WCAG 1.0 cp 6.1 is not required. If stylesheet are not in your baseline, then WCAG 1.0 cp 6.1 is required at Level 1 (as it maps to Guideline 1.3 L1). (link to baseline discussion in conformance section)
bug - need to figure out if alternatives changing when content changes needs to be made explicit (in WCAG 2.0)
resolution: leave 4.2 in the list
resolution: add benefit to 2.2 about
"distractibility"
... this maps to level 2, but we added a level 1 criterion that says users
can avoid. (Thus maps to 2 places - 2.3 level 1 and level 2).
<Christophe> http://www.w3.org/TR/2005/WD-WCAG20-20050630/Overview.html
resolution: leave what is there, add "there is no direct mapping."
add note: server-side image maps are not operable from the keyboard. ?
also map to 1.1?
also map to 2.4?
also to 4.2?
maps to 1.1 with regard to text alternatives, to 2.1 with regard to keyboard access (server-side image maps are not keyboard accessible), 2.4 l2 sc4, and 4.2 L1 #1
resolution: maps to 1.1 with regard to text alternatives, to 2.1 with regard to keyboard access (server-side image maps are not keyboard accessible), 2.4 l2 sc4, and 4.2 L1 #1
map same as previous?
are server-side imag maps allowed?
the need expressed by this checkpoint is met if the following...
acknowledge that this bar is no longer there? e.g., even if equivalent way to doing, still can't use it.
say "this is no longer a level 1 requirement?"
regardless if you are using server-side or client-side image maps, you have to meet the guidelines (1.1, 2.1, 2.4, 4.2).
resolution: this checkpoint most directly maps to 1.1 with regard to text alternatives, to 2.1 with regard to keyboard access (server-side image maps are not keyboard accessible), 2.4 l2 sc4, and 4.2 L1#1
resolution: no change since already have a level 1 requirement and adding others may cause confusion b/c not requiring any additional work to be done.
resolution: no change since already have a level 1 requirement and adding others may cause confusion b/c not requiring any additional work to be done.
concern about level 1 vs level 2
no resolution.
mapping seems appropriate, but concern that at level 2 in wcag 2.0
<scribe> ACTION: yvette, ben, michael discuss mapping of WCAG 1.0 Checkpoint 12.1 [recorded in http://www.w3.org/2005/07/28-wai-wcag-minutes.html#action01]
resolution: add 4.2 l1 sc1
<scribe> ACTION: ben propose wording for 4.2 l1 sc1 [recorded in http://www.w3.org/2005/07/28-wai-wcag-minutes.html#action02]
resolution: adopt as is
resolution: adopt as is
resolution: also map to 1.2 l1 sc2 (audio descriptions)
This is scribe.perl Revision: 1.126 of Date: 2005/05/16 16:49:48 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/is/seems/ Succeeded: s/resolution: add 4.2 l1 sc1 and it is baseline dependent/resolution: add 4.2 l1 sc1/ Succeeded: s/WCAG 1.0 Checkpoint 4.1/mapping of WCAG 1.0 Checkpoint 4.1/ Found Scribe: wendy Inferring ScribeNick: wendy Default Present: Wendy, Bengt_Farre, Ben_and_Gregg, Andi, David, Michael_Cooper, Christophe_Strobbe, Gian, Becky_Gibson, rellero, Alex_Li, Loretta_Guarino_Reid, Matt_May Present: Wendy Bengt_Farre Ben_and_Gregg Andi David Michael_Cooper Christophe_Strobbe Gian Becky_Gibson rellero Alex_Li Loretta_Guarino_Reid Matt_May Regrets: Roberto_Scano Yvette_Hoitink Luca_Mascaro Makoto_UEKI Sebastiano_Nutarelli Tim_Boland Agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JulSep/0187.html Got date from IRC log name: 28 Jul 2005 Guessing minutes URL: http://www.w3.org/2005/07/28-wai-wcag-minutes.html People with action items: ben yvette WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]