17:46:32 RRSAgent has joined #ua 17:46:32 logging to http://www.w3.org/2009/12/10-ua-irc 17:46:34 RRSAgent, make logs public 17:46:34 Zakim has joined #ua 17:46:36 Zakim, this will be WAI_UAWG 17:46:36 ok, trackbot; I see WAI_UAWG()1:00PM scheduled to start in 14 minutes 17:46:37 Meeting: User Agent Accessibility Guidelines Working Group Teleconference 17:46:37 Date: 10 December 2009 17:47:01 rrsagent, set logs public 17:56:43 jeanne has joined #ua 17:57:31 WAI_UAWG()1:00PM has now started 17:57:37 +AllanJ 17:59:57 +Jeanne 18:00:02 sharper has joined #ua 18:01:03 zakim, code? 18:01:03 the conference code is 82941 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), sharper 18:02:12 +Greg 18:02:45 Greg has joined #ua 18:03:16 +??P9 18:03:20 zakim, ??P9 is sharper 18:03:20 +sharper; got it 18:03:28 regrets: Kelly_Ford, Kim_Patch, Jan_Richards, Henny_Swan 18:04:19 Agenda+ Logistics (Regrets, agenda requests, comments)? Agenda+ review survey http://www.w3.org/2002/09/wbs/36791/20091208/ 18:04:45 Agenda+ review survey http://www.w3.org/2002/09/wbs/36791/20091208/ 18:04:56 Agenda+ new assignments (4.7.2-5, 4.8) 18:08:03 scribe: allanj 18:08:30 GL: discusses comments to 4.9.6 18:08:41 ...replace UA with user agent 18:10:40 ... clarify 'and/or' based on what's there, not what the author provides. need to clarify in the definitions and supplemental materials 18:15:09 ... settle on one term for "time-based media" (4.9.3), "animation" (4.9.7), and "video" (4.9.6) 18:15:41 issue: settle on one term for "time-based media" (4.9.3), "animation" (4.9.7), and "video" (4.9.6) 18:15:41 Created ISSUE-61 - Settle on one term for "time-based media" (4.9.3), "animation" (4.9.7), and "video" (4.9.6) ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/61/edit . 18:18:45 ... ISO has slow multimedia as an AA level not A 18:22:34 ... is media broad enough, should we choose a different word, to generalize to encompass audio, video, animation, haptic, etc. 18:23:55 what about canvas element. 18:25:04 GL: if all control of timing is done by a script then it is up to the author to provide functionality. 18:28:12 issue: editorial checks -- review document for 'recognize', 'and/or', initialisms (UA, acromyns, etc.) 18:28:12 Created ISSUE-62 - Editorial checks -- review document for 'recognize', 'and/or', initialisms (UA, acromyns, etc.) ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/62/edit . 18:34:19 discussion of flash threshhold 18:38:12 WCAG flash language: Three Flashes or Below Threshold: Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. (Level A) 18:40:38 SH: wants to combine 4.4.1 and 4.4.2 18:45:35 GL: what about 'blink' element. if UA has a hard coded blink rate of 4+ times, then UA is in violation. 18:48:32 mhakkinen has joined #ua 18:49:05 ... UA that recognizes flashing control should provide a mechanism to limit the number of flashes. 18:49:11 +??P11 18:49:17 WCAG understanding: http://www.w3.org/TR/UNDERSTANDING-WCAG20/seizure-three-times.html 18:50:08 zakim, P11 is really mhakkinen 18:50:08 sorry, AllanJ, I do not recognize a party named 'P11' 18:50:23 zakim, ??P11 is really mhakkinen 18:50:23 +mhakkinen; got it 18:50:49 Actually my point was that if a Web page uses the tag and the UA renders that by flashing the content four times per second, the UA would not violate the currently worded guidelines, but we should revise the guidelines so it would be in violation of something. 18:52:01 rrsagent, make minutes 18:52:01 I have made the request to generate http://www.w3.org/2009/12/10-ua-minutes.html AllanJ 18:53:53 We can either modify 4.4.1 and 4.4.2 to restrict both the UA UI *and* recognized flashing in rendered content, or we could add separate success criteria for the latter. 18:59:45 To go further, should the UA be required to override recognized Web content attributes that would cause blinking that violates the thresholds? Or, should the UA only be required not to violate them when IT (the UA itself) provides the blink rate? 19:07:23 Intent- to avoid causing seizures. 19:07:35 I suggest that we recommend the user agent provide a user option to constrain recognized blinking in web content to fall within the general flashing and red flashing ranges so as to avoid triggering seizures in individuals with photosensitive seizure disorders. 19:08:28 intent - this is about preventing physical harm 19:08:37 ... to the user 19:11:49 two items: user option to set blink rate; and, default flashing rate for interface and content 19:12:27 "the user interface and default presentation of recognized flashing Web content never violate..."? 19:13:43 action: Jim to rewrite 4.4.1 to include the user interface and default presentation of recognized flashing Web content never violate and create user has the option to... 19:13:43 Created ACTION-258 - Rewrite 4.4.1 to include the user interface and default presentation of recognized flashing Web content never violate and create user has the option to... [on Jim Allan - due 2009-12-17]. 19:18:44 issue: mechanism to expand marque (or other element) to read the content within - scroll bars, etc 19:18:44 Created ISSUE-63 - Mechanism to expand marque (or other element) to read the content within - scroll bars, etc ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/63/edit . 19:23:31 Suggestion: the UA should allow the user to perform on CSS images and background images any action they could perform on normal, foreground images. Same with extra text e.g. bullets and numbering. 19:24:23 issue: the UA should allow the user to perform on CSS images and background images any action they could perform on normal, foreground images. Same with extra text e.g. bullets and numbering. UA should have access to CSS DOM or its generated content. 19:24:24 Created ISSUE-64 - The UA should allow the user to perform on CSS images and background images any action they could perform on normal, foreground images. Same with extra text e.g. bullets and numbering. UA should have access to CSS DOM or its generated content. ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/64/edit . 19:26:09 -Jeanne 19:26:10 -sharper 19:26:10 -AllanJ 19:26:12 -Greg 19:26:21 -mhakkinen 19:26:22 WAI_UAWG()1:00PM has ended 19:26:23 Attendees were AllanJ, Jeanne, Greg, sharper, mhakkinen 19:26:46 rrsagent, make minutes 19:26:46 I have made the request to generate http://www.w3.org/2009/12/10-ua-minutes.html AllanJ 19:27:59 zakim, please part 19:27:59 Zakim has left #ua 19:28:10 rrsagent, make minutes 19:28:10 I have made the request to generate http://www.w3.org/2009/12/10-ua-minutes.html AllanJ 19:28:41 rrsagent, please part 19:28:41 I see 1 open action item saved in http://www.w3.org/2009/12/10-ua-actions.rdf : 19:28:41 ACTION: Jim to rewrite 4.4.1 to include the user interface and default presentation of recognized flashing Web content never violate and create user has the option to... [1] 19:28:41 recorded in http://www.w3.org/2009/12/10-ua-irc#T19-13-43 19:28:42 FYI retro link and marquis page with both blink tag and blink css 19:28:45 http://users.jyu.fi/~mhakkine/blink.html