19:37:00 <RRSAgent> RRSAgent has joined #wai-wcag
19:37:01 <RRSAgent> logging to http://www.w3.org/2005/07/14-wai-wcag-irc
19:37:08 <wendy> RRSAgent, make log world
19:40:02 <wendy> Regrets: Roberto Castaldo, Alex Li, Roberto Scano (until 15 August)
19:40:28 <wendy> Agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JulSep/0044.html
19:40:37 <wendy> agenda+ Techniques Task Force update.
19:40:46 <wendy> agenda+ Harvest techniques and/or tests for guidelines 3.2, 4.1 and 4.2.
19:41:03 <wendy> agenda+ Discuss recent request for WCAG 1.0 interpretation regarding tables for layout. (refer to http://tinyurl.com/8drxs)
19:41:30 <wendy> agenda+ Mapping of 1.0 to 2.0 http://www.w3.org/WAI/GL/2005/06/30-mapping.html
19:50:06 <sebastiano> sebastiano has joined #wai-wcag
19:54:01 <rellero> rellero has joined #wai-wcag
19:59:19 <bengt> bengt has joined #wai-wcag
20:00:03 <Yvette> Yvette has joined #wai-wcag
20:00:19 <rellero> hi
20:02:03 <Michael> zakim, this is wai_wcag
20:02:03 <Zakim> ok, Michael; that matches WAI_WCAG()4:00PM
20:02:11 <Michael> zakim, who's on the phone?
20:02:11 <Zakim> On the phone I see Michael_Cooper, Ben, Christophe_Strobbe
20:02:24 <Zakim> + +1.212.404.aaaa
20:02:37 <Zakim> +Wendy
20:02:51 <Zakim> +Yvette_Hoitink
20:03:10 <wendy> zakim, +1.212.404.aaaa is Sebastiano
20:03:10 <Zakim> +Sebastiano; got it
20:03:14 <Zakim> +??P6
20:03:17 <Zakim> +??P7
20:03:26 <bengt> zakim, ??P6 is Bengt_Farre
20:03:26 <Zakim> +Bengt_Farre; got it
20:03:35 <wendy> zakim, ??P7 is Gregg_Vanderheiden
20:03:35 <Zakim> +Gregg_Vanderheiden; got it
20:03:35 <gregg> gregg has joined #wai-wcag
20:03:52 <Zakim> + +1.512.784.aabb
20:04:10 <LucaMascaro> LucaMascaro has joined #wai-wcag
20:04:10 <wendy> zakim, +1.512.784.aabb is John_Slatin
20:04:10 <Zakim> +John_Slatin; got it
20:04:20 <Zakim> +Becky_Gibson
20:04:25 <Becky> Becky has joined #wai-wcag
20:05:09 <Zakim> -John_Slatin
20:05:26 <Zakim> +??P10
20:05:34 <wendy> John called in to thank us for the song and say "hello" :)
20:05:37 <Tim> Tim has joined #wai-wcag
20:05:59 <wendy> zakim, ??P10 is Luca_Mascaro
20:05:59 <Zakim> +Luca_Mascaro; got it
20:06:07 <LucaMascaro> zakim, mute me
20:06:07 <Zakim> Luca_Mascaro should now be muted
20:06:32 <wendy> zakim, who's on the phone?
20:06:32 <Zakim> On the phone I see Michael_Cooper, Ben, Christophe_Strobbe, Sebastiano, Wendy, Yvette_Hoitink, Gregg_Vanderheiden, Bengt_Farre, Becky_Gibson, Luca_Mascaro (muted)
20:06:59 <wendy> zakim, take up item 1
20:06:59 <Zakim> agendum 1. "Techniques Task Force update." taken up [from wendy]
20:07:00 <Zakim> +Tim_Boland
20:07:02 <wendy> scribe: wendy
20:07:16 <Zakim> +??P11
20:07:28 <rellero> zakim, +??P11is rellero
20:07:28 <Zakim> I don't understand '+??P11is rellero', rellero
20:07:48 <bengt> zakim, ??P11 is rellero
20:07:48 <Zakim> +rellero; got it
20:08:01 <rellero> tks
20:08:07 <wendy> mc: will be finishing review of existing tests (about 100 of them) as well as pending (about 25). will be sending proposals to the list and gathering feedback using surveys, similar to guidelines.
20:08:08 <Yvette> zakim, mute me
20:08:08 <Zakim> Yvette_Hoitink should now be muted
20:08:31 <wendy> mc: script tests - not sure what they will look like. feel that need techniques before can write tests.
20:09:10 <wendy> mc: from the harvesting, focusing on developing script techniques.  looking at how to coordinate with experts.
20:10:14 <rellero> I have a problem with line, I'll follow in irc
20:10:36 <Zakim> -rellero
20:11:51 <wendy> mc: some editorial and structural changes to html techniques to make. easiest way is to make the changes to an internal draft (rather than writing proposals for each change).
20:12:36 <wendy> mc: not likely substantial changes, except addition of testable statements for each technique.
20:13:46 <wendy> resolution: michael will make some editorial and structural changes to html techniques and publish an internal draft for review.
20:14:02 <wendy> zakim, next item
20:14:02 <Zakim> agendum 2. "Harvest techniques and/or tests for guidelines 3.2, 4.1 and 4.2." taken up [from wendy]
20:15:17 <Michael> Mapping document: http://www.w3.org/WAI/GL/2005/06/30-sc-techniques-mapping.html
20:15:51 <wendy> Topic: guideline 3.2 techniques harvest
20:16:19 <Yvette> zakim, unmute me
20:16:19 <Zakim> Yvette_Hoitink should no longer be muted
20:16:29 <wendy> L1SC1 - Any change of context is implemented in a manner that can be programmatically determined.
20:16:36 <wendy> CSS inherit
20:17:12 <wendy> w/inherit property children will accept computed value of parent
20:17:28 <wendy> change of context?
20:17:49 <wendy> at least for rendering purposes, might facilitate similar look and feel across elements.
20:19:09 <wendy> 2. need an alternative to "target" since not allowed in strict html. rel is external then programmatically open new window.
20:19:39 <wendy> script techniques
20:21:08 <wendy> issues with SC? what does it mean to programmatically determine opening a window in script?
20:22:25 <wendy> using "a" is one way to satisfy this. have technique for using? [or just refer to html spec]
20:22:48 <wendy> L2 SC1 Components that are repeated on multiple delivery units within a set of delivery units occur in the same order each time they are repeated.
20:23:06 <wendy> currently - CSS about indenting text. not properly mapped.
20:23:18 <wendy> server-side includes
20:23:20 <wendy> templates
20:23:32 <wendy> cms to help
20:23:43 <wendy> general tech about introducing subitems to clarify allowed
20:24:09 <wendy> L2 SC2 When any component receives focus, it does not cause a change of context.
20:24:54 <wendy> in html, techniques that discuss onfocus event handler and what not to do when activated
20:25:07 <wendy> on forms submit, have to use submit so that doesn't rely on focus to cause submission
20:25:53 <wendy> does this address issue w/tabbing to menu itme and menu item opens automatically (on tab into)?
20:26:41 <wendy> change of context - A change of user agent, viewport, user interface controls, or focus; or complete change of content.
20:27:15 <wendy> L2 SC3 Changing the setting of any input field does not automatically cause a change of context .
20:27:55 <wendy> becky's submitted scripting technique using onchange on select (in an accessible way)
20:28:57 <rellero_> rellero_ has joined #wai-wcag
20:29:02 <wendy> somewhat controversial (but will log and explore)
20:29:35 <rellero_> rellero_ has joined #wai-wcag
20:29:52 <rellero_> rellero_ has joined #wai-wcag
20:30:33 <wendy> question about: technique to address issue that automatically advances you to next field after enter x # of characters? when hit back to fix an entry, now in different field. 
20:30:44 <wendy> L2SC4 Components that have the same functionality in multiple delivery units within a set of delivery units are labeled consistently.  	 
20:31:22 <wendy> this is more about generating the page rather than fixing later.  perhaps general technique "just do it..."
20:31:47 <wendy> L3SC1 Graphical components that appear on multiple pages, including graphical links, are associated with the same text equivalents wherever they appear.
20:32:47 <wendy> test - if a graphic is associated with different uris on different pages, flag them and determine if differences make sense. if not, make consistent.
20:32:56 <wendy> L3SC2 Changes of context are initiated only by user action.
20:33:04 <wendy> no automatic refreshes, at all.
20:34:23 <Zakim> -Ben
20:34:48 <wendy> navigating around page, shouldn't cause change of context (e.g., pop-ups). however, this meant to mean "only by user request."
20:35:01 <wendy> minor issue with wording of SC.  "user action" a bit too vague
20:35:15 <Zakim> +Ben.a
20:37:35 <wendy> new bug for this issue - http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1535
20:37:45 <wendy> "on leaving a data field"
20:37:55 <wendy> html-specific?
20:39:07 <wendy> resolution: adopt L3SC2 Changes of context are initiated only by user request.
20:39:51 <wendy> use links to cause page to refresh
20:39:56 <wendy> (or section of a page)
20:40:13 <wendy> instead of automatically causing refresh
20:42:58 <wendy> changes of user agent:
20:43:55 <wendy> discussion about issue.
20:44:32 <wendy> other parts of the defn of "change of context" - have we addressed "change in user interface control?"
20:44:39 <wendy> mentioned earlier (becky's proposal)
20:49:38 <wendy> Topic: Guideline 4.2
20:50:16 <wendy> L1SC1  If content does not meet all level 1 success criteria, then an alternate form is provided that does meet all level 1 success criteria.
20:53:52 <wendy> discussion about concerns with this SC
20:54:35 <wendy> issues raised - 1. does this apply to content outside the baseline? also applied to content inside the baseline?
20:56:59 <wendy> perhaps say something along the lines of, "If content outside the baseline does not meet..."
20:57:08 <wendy> however, tech may not be capable
20:57:15 <wendy> If content can not meet...
20:57:35 <wendy> "can not" would have to apply to technology not the author (or cost/effort)
20:57:45 <Christophe> q+
20:58:10 <wendy> ack ch
20:58:34 <wendy> if scripting in baseline, still things can do that don't meet the gl so still need to provide an alternative form.
21:00:05 <wendy> if you can make it accessible you must...
21:03:05 <wendy> http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1536
21:03:28 <wendy> RRSAgent, generate minutes
21:03:28 <RRSAgent> I have made the request to generate http://www.w3.org/2005/07/14-wai-wcag-minutes.html wendy
21:03:40 <wendy> noframes, noscript
21:04:24 <wendy> fallback mechanism for applets (if applet not in baseline) need alternative mechanism for funcationlity
21:05:40 <wendy> content negotiation
21:05:55 <wendy> set of general techniques links to alternatives
21:06:05 <wendy> (concern about these and cyberghetto)
21:06:33 <wendy> user settings, store preferences
21:06:49 <Tim> Tim has left #wai-wcag
21:06:56 <wendy> Meeting: WCAG WG weekly telecon
21:06:58 <Zakim> -Tim_Boland
21:06:58 <wendy> Chair: Gregg
21:07:04 <wendy> style switcher
21:08:02 <wendy> L1 SC2 #   Content using baseline technologies or non-baseline technologies, must meet the following criteria: [V]
21:08:03 <wendy>    1. Content that violates international health and safety standards for general flash or red flash is marked in a way that the user can avoid its appearance
21:08:05 <wendy>       Editorial Note: @@ update to match 2.3 text when it is complete
21:08:06 <wendy>    2. If the user can enter the content using the keyboard, then the user can exit the content using the keyboard.
21:08:45 <wendy> several techs already mapped to
21:08:57 <wendy> concern about mappings
21:09:13 <wendy> map to SC1 instead?
21:10:11 <wendy> gen tech about keyboard handling
21:10:11 <wendy> gen tech about not trapping keyboard
21:10:52 <wendy> javascript keyboard event handlers. how to return t/f if handle or if OS handles. 
21:11:01 <wendy> "hit x to return to previous page"
21:11:31 <wendy> covered by "must be able to use w/keyboard"
21:11:39 <wendy> this abut getting trapped in a plug-in
21:11:57 <wendy> can never use contentEditable?
21:12:41 <wendy> should document work-arounds/games/kludges related to
21:12:54 <wendy> L1SC3    	
21:13:08 <wendy> L1SC3 The role, state, and value can be programmatically determined for every user interface component of the web content that accepts input from the user or changes dynamically in response to user input or external events.
21:13:27 <wendy> there are techniques but can't validate right now and don't have spec *yet*
21:14:39 <wendy> however, if use elements semantically correctly would satisfy to best of ability. also, in some techs (flash) dont' you have to do for info to get passed through?
21:15:46 <wendy> concern that people creating UI elements with a and div and is that not using the elements semantically correctly
21:17:38 <wendy> issue - is it possible to meet the strict interpretation of this in html? if not, what is the intent?  can we meet the intent with other wording?
21:19:04 <wendy> http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1537
21:21:45 <wendy> L1SC4 The label of each user interface control that accepts input from the user can be programmatically determined and is explicitly associated with the control.
21:22:10 <wendy> zakim, who's talking?
21:22:21 <Zakim> wendy, listening for 10 seconds I heard sound from the following: Michael_Cooper (51%), Sebastiano (13%), Bengt_Farre (44%), Becky_Gibson (39%)
21:22:28 <wendy> zakim, mute Bengt
21:22:28 <Zakim> Bengt_Farre should now be muted
21:22:35 <wendy> form label techniques
21:22:40 <wendy> zakim, mute sebastiano
21:22:40 <Zakim> Sebastiano should now be muted
21:22:56 <wendy> value attribute to label (type=submit, reset, button)
21:23:01 <wendy> button element
21:24:06 <wendy> label element for most controls, alt for image input, value for most buttons, text for button element
21:24:33 <wendy> L1SC5  The states and values of content that can be changed via the user interface can also be changed programmatically.
21:24:37 <wendy> how different from 3?
21:24:51 <wendy> determined vs changed
21:25:30 <wendy> DHTML roadmap techniques 
21:26:55 <wendy> java and flash techniques
21:27:03 <sebastiano> Sorry about my little noise..
21:27:54 <wendy> primary concern now about programmatic objects. mapping to UAAG 1.0 that all things are covered.
21:28:20 <wendy> eventually xhtml. perhaps confusing now for html devs, but need to document in guide asap
21:28:43 <wendy> L1 SC6 Changes to content, structure, selection, focus, attributes, values, state, and relationships within the content can be programmatically determined.
21:28:46 <Zakim> -Gregg_Vanderheiden
21:29:20 <wendy> ah. perhaps.
21:29:23 <wendy> zakim, bengt is Gregg
21:29:23 <Zakim> +Gregg; got it
21:29:35 <wendy> document.write
21:30:25 <wendy> w/java if using classes that include accessibility then get for free, but if not then need to ensure that do these things
21:30:35 <wendy> point to external documentation that explains/shows
21:31:26 <wendy> redundant with using accessibility conventions? no - if use accessibilty features, get for free. if not, need to do the things in L1 SC6
21:31:35 <wendy> L2SC1 Accessibility conventions of the markup or programming language (API's or specific markup) are used.
21:32:45 <wendy> "Creating Invisible labels for form elements" is mapped here. should remap to L1SC4
21:33:32 <wendy> people interpret this to mean that they have to use all accessbiility features (e.g., accesskey, tabindex) that not necessarily the case.
21:34:03 <wendy> document the user agent issue where accessibility features are not supported or supported inconsistently
21:34:08 <Zakim> +Gregg_Vanderheiden
21:34:15 <Zakim> -Gregg
21:34:34 <wendy> L3 SC1 Content implemented using technologies outside of baseline follows all WCAG requirements supported by the technology.
21:35:34 <wendy> all uses of javascript on a site (if js not in baseline) are accessible and also work with out.
21:36:26 <wendy> tech is - follow techs for that tech
21:36:59 <LucaMascaro> zakim, unmute me
21:36:59 <Zakim> Luca_Mascaro should no longer be muted
21:37:12 <Zakim> -Ben.a
21:37:13 <Zakim> -Wendy
21:37:13 <Zakim> -Michael_Cooper
21:37:15 <Zakim> -Yvette_Hoitink
21:37:16 <wendy> adjourned
21:37:16 <Zakim> -Becky_Gibson
21:37:17 <Zakim> -Gregg_Vanderheiden
21:37:19 <Zakim> -Christophe_Strobbe
21:37:21 <Zakim> -Luca_Mascaro
21:37:30 <Zakim> -Sebastiano
21:37:31 <Zakim> WAI_WCAG()4:00PM has ended
21:37:32 <Zakim> Attendees were Michael_Cooper, Ben, Christophe_Strobbe, Wendy, Yvette_Hoitink, Sebastiano, Bengt_Farre, Gregg_Vanderheiden, John_Slatin, Becky_Gibson, Luca_Mascaro, Tim_Boland,
21:37:34 <Zakim> ... rellero, Gregg
21:37:43 <wendy> RRSAgent, generate minutes
21:37:43 <RRSAgent> I have made the request to generate http://www.w3.org/2005/07/14-wai-wcag-minutes.html wendy
21:56:50 <Christophe> Christophe has left #wai-wcag
22:04:16 <wendy> zakim, bye
22:04:16 <Zakim> Zakim has left #wai-wcag
22:04:20 <wendy> RRSAgent, bye
22:04:20 <RRSAgent> I see no action items