17:56:00 RRSAgent has joined #ua 17:56:00 logging to http://www.w3.org/2009/02/05-ua-irc 17:56:10 zakim, this will be wai_u 17:56:10 ok, AllanJ; I see WAI_UAWG()1:00PM scheduled to start in 4 minutes 17:56:20 rrsagent, set logs public 17:56:23 JR has joined #ua 17:57:36 title: UAWG telecon 17:57:48 chair: Jim_Allan 17:58:23 Agenda+ Logistics (Regrets, agenda requests, comments)? 17:58:32 Agenda+ New Member (introductions all around) 17:58:39 Agenda+ WD Publication status 17:58:51 Agenda+ ATIA report on UAAG20 poster session 17:59:20 Agenda+ Glossary Review First 20 Items - 17:59:22 http://lists.w3.org/Archives/Public/w3c-wai-ua/2009JanMar/att-0009/UAAG_glossary_review.doc 17:59:44 Agenda+ Draft Charter review http://www.w3.org/WAI/UA/2008/draft_uawg_charter_20mar08.html 17:59:50 WAI_UAWG()1:00PM has now started 17:59:52 jeanne has joined #ua 17:59:57 +??P18 18:00:19 zakim, code? 18:00:19 the conference code is 82941 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), jeanne 18:01:07 +Jeanne 18:01:19 +[Microsoft] 18:01:56 +??P29 18:02:36 + +1.512.206.aaaa 18:02:36 zakim, ??P29 is really JR 18:02:38 +JR; got it 18:02:40 Agenda+ Action Item Review http://www.w3.org/WAI/UA/tracker/actions/open 18:02:41 sharper has joined #ua 18:02:52 Agenda+ Open Issues Review http://www.w3.org/WAI/UA/tracker/issues/open 18:03:25 +??P12 18:03:43 zakim,aaaa is really AllanJ 18:04:03 zakim, +1.512.206.aaaa is really AllanJ 18:04:24 +AllanJ; got it 18:04:39 sorry, JR, I do not recognize a party named '+1.512.206.aaaa' 18:05:02 zakim, ??P12 is really sharper 18:05:02 +sharper; got it 18:05:21 KFord has joined #ua 18:05:42 regrets: Alan 18:08:01 scribe: Harper_Simon 18:08:01 ScribeNick: sharper 18:08:12 +Mark_Hakkinen 18:09:32 present: Allan_James, Harper_Simon, Hakkinen_Mark, Spellman_Jeanne, Ford_Kelly, Swan_Henny 18:10:35 JA: Introduces new member HS (Opera Web Evangelist) 18:10:44 HS: Introductions and background 18:10:49 mth has joined #ua 18:11:53 present+ Richards_Jan 18:12:38 All: Round table Introductions 18:13:27 zakim, take up item 1 18:13:27 agendum 1. "Logistics (Regrets, agenda requests, comments)?" taken up [from AllanJ] 18:14:47 regrets+ Brewer_Judy 18:15:24 zakim, close item 1 18:15:24 agendum 1, Logistics (Regrets, agenda requests, comments)?, closed 18:15:24 zakim, next item 18:15:25 I see 7 items remaining on the agenda; the next one is 18:15:27 2. New Member (introductions all around) [from AllanJ] 18:15:29 agendum 2. "New Member (introductions all around)" taken up [from AllanJ] 18:15:40 zakim, close item 2 18:15:40 agendum 2, New Member (introductions all around), closed 18:15:40 zakim, next item 18:15:41 I see 6 items remaining on the agenda; the next one is 18:15:42 3. WD Publication status [from AllanJ] 18:15:43 agendum 3. "WD Publication status" taken up [from AllanJ] 18:16:41 JS: Draft - currently on hold for chartering and WG meetings per year for UAWG. Once complete we can then publish this draft. 18:16:51 JS: Hoping for something soon. 18:19:09 zakim, close item 3 18:19:09 agendum 3, WD Publication status, closed 18:19:09 zakim, next item 18:19:11 I see 5 items remaining on the agenda; the next one is 18:19:12 4. ATIA report on UAAG20 poster session [from AllanJ] 18:19:13 agendum 4. "ATIA report on UAAG20 poster session" taken up [from AllanJ] 18:19:53 JA: JS did a poster session at ATIA and has comments. 18:21:07 JS: @ posters - one on WAI and Guidelines and screen-shot of Easy YouTube Browser 18:21:37 JS: Generated most discussion as concerned that we where including Web Applications as User Agents. 18:22:08 JS: feeling was covered by WCAG and was confusion that we required developers to conform to 2 sets of guidelines 18:22:38 JS: Concern re - EU that thsi would quickly become a standard 18:23:07 q+ 18:23:11 JS: W-Applications are just widgets and have to conform to WCAG and ARIA and now UAWG 18:23:17 ack 18:23:40 q+ 18:23:45 KF: What do people think about this - what are our reactions? 18:24:38 JR: Not going to be to much of a big deal in reality - we already point to WCAG for a big chunk of this - things after this are really just to do with broswer specific stuff - in a browser setting. 18:25:02 q+ 18:25:18 ack JR 18:25:28 MH: Sorted in Public comment 18:25:36 ack KFord 18:26:34 Q+ cover the future and black hole of javascript 18:26:41 KF: Our guidelines are the superset of the basics that would be needed, for future proofing. 18:27:06 KF: need some good arguments on this 18:28:22 JA: with PF dodged a bullet using ARIA - may not be so lucky next time - developers doing so so much with JavaScript that there may be problems in the future. 18:28:45 http://www.w3.org/People/jeanne/ATIA2009/UAAG-final-letter.pdf 18:28:50 q+ 18:29:01 ack KFord 18:30:30 KF: UAAG 1 based on desktop - strides on eliminating the bias - desktop is still primary - but other devices must be included - need to make sure that our guidelines are not so biased. 18:31:15 JS: Like to take the time to re read for modularity - such that if a section applies to a W-Application or does the entire document applies - must be careful on this. 18:31:37 JA: in Conformance claim? 18:31:47 q+ 18:32:16 JS: Guidelines to make sure that (in application notes) we have the right boundaries around the user agent types. 18:33:04 ack mth 18:34:16 MH: Follow up on KF - most innovation on touch screen devices etc. need to look at the document now to see this. 18:34:48 boundary between (specific guidelines) for web-applications as browser and browser-application 18:34:56 SHarper: Talking about other browsing platforms like that used by phones from Google. 18:34:58 q+ 18:35:05 http://www.w3.org/People/jeanne/ATIA2009/WAI-Poster.png 18:35:22 q+ 18:35:31 Sharper: Also talking about json, javascript object notation. 18:36:11 ack mth 18:36:54 JR: +1 to kford's comments. Reason why we need to declare any kind of boundary is that in the end we are talking about agents where the contet is web content. 18:36:55 JR: +1 to KF comment about wide variety of platforms, tools, etc. 18:38:30 q+ 18:38:39 ackJR 18:38:48 ack KFord 18:38:59 ack JR 18:39:14 q+ 18:39:27 KF: Android technology could be the greater concern, JSON is more about the JS technology as it is about displaying information. 18:39:54 SH: JSON covered by ARIA? 18:40:38 KF: JSON more about the exchange as opposed to the display so would not effect this - as WCAG / UAAG / ARIA would still cover this. 18:40:54 ack mth 18:41:05 KF: more about background (lower-level) data transfer 18:41:20 MH: Android browser based on WebKit and more like chrome 18:42:52 MH: Times Article - TV Raman - touch screen technology working on user agents - ideas on this? 18:43:55 JSON definition/description http://en.wikipedia.org/wiki/Json 18:44:38 So JSON is just a format 18:46:10 RESOLVED: Still resolved to address Web Applications in the UAAG Guidelines as they are part of the browser. 18:47:57 RESOLVED: JA - Two sets of guidelines, these are for things that are for applications and another set are the Web Applications side (this is a possibility - re JS characterisations) in maybe a 2-tiered way. 18:49:24 TV Raman article from MY Times - http://www.nytimes.com/2009/01/04/business/04blind.html 18:50:05 +1 18:50:14 Action JR: Write-up a clarification of WHICH web apps are user agents and which are not. 18:50:14 Created ACTION-119 - Write-up a clarification of WHICH web apps are user agents and which are not. [on Jan Richards - due 2009-02-12]. 18:50:14 JR: Could you say when content is wrapped in content then it is just content - but when you transform something you're a user agent. 18:50:24 ISSUE: Future Formats - do we need to investigate these? 18:50:24 Created ISSUE-31 - Future Formats - do we need to investigate these? ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/31/edit . 18:51:34 q+ 18:52:11 MH: Pulling local database information (not Web) and wrapping in html but not web content 18:52:38 JR: is dataformat a web content format? HTML is ARIA is / word is not say 18:53:04 ack KFord 18:53:06 MH: pulling an XML doc into an XSLT system 18:54:56 KF: common for desktop applications - will use any web tech that is on the platform as it is easy to wrap and use. Problem, maybe getting AT to switch between these applications - is this covered - should it be? Also, problem getting out of the environment. 18:56:01 q+ 18:56:03 KF: Do we need a guideline saying - you've got to play nice with your neighbours. 18:57:16 q+ 18:57:48 JA: In new 508, did away with application guidelines and web guidelines - now they are just one. 18:58:28 JA: Seems like the compound document issues - (platform on a platform on a platform) 18:58:35 acl AllanJ 18:58:36 action: kf, mh to think about guideline to capture user agents embeded in desktop applications 18:58:36 Sorry, couldn't find user - kf, 18:58:42 ack AllanJ 18:59:12 ack JR 18:59:35 JR: Plugins are user agents embeded in a desktop application 19:00:40 action: kford,mht to think about guideline around ensuring embedded user agents work correctly. 19:00:40 Sorry, couldn't find user - kford,mht 19:01:22 mth 19:02:05 action: kford to think about guideline around ensuring embedded user agents work correctly (includes MTH). 19:02:05 Sorry, couldn't find user - kford 19:02:29 action: kelly to think about guideline around ensuring embedded user agents work correctly (includes MTH). 19:02:29 Created ACTION-120 - Think about guideline around ensuring embedded user agents work correctly (includes MTH). [on Kelly Ford - due 2009-02-12]. 19:03:01 zakim, close item 4 19:03:01 agendum 4, ATIA report on UAAG20 poster session, closed 19:03:02 zakim, next item 19:03:03 I see 4 items remaining on the agenda; the next one is 19:03:04 5. Glossary Review First 20 Items - [from AllanJ] 19:03:05 agendum 5. "Glossary Review First 20 Items -" taken up [from AllanJ] 19:04:29 zakim, close item 5 19:04:29 agendum 5, Glossary Review First 20 Items -, closed 19:04:29 zakim, next item 19:04:30 I see 3 items remaining on the agenda; the next one is 19:04:31 6. Draft Charter review http://www.w3.org/WAI/UA/2008/draft_uawg_charter_20mar08.html [from AllanJ] 19:04:34 agendum 6. "Draft Charter review http://www.w3.org/WAI/UA/2008/draft_uawg_charter_20mar08.html" taken up [from AllanJ] 19:06:43 q+ 19:06:56 JA: Last call June 09 atainable? 19:07:28 JS: need video, understanding doc, and couple of other things. 19:08:03 ack KFord 19:08:17 KFord: Need more comments on the draft 19:08:22 KF: June seems ambitious 19:09:07 KF: August / Sept seems more realistic 19:09:31 JA: we can have more than one last call 19:09:48 JR: don't want to plan many LC - means you haven't done your job 19:10:20 JR: Now have a Stabilisation Draft - then after this LC 19:10:21 q+ to talk about the importance of presenting and talking about the publications. 19:10:28 JR: need time for this 19:10:54 JR: 9 months from now to LC through SD 19:11:02 ack jeanne 19:11:02 jeanne, you wanted to talk about the importance of presenting and talking about the publications. 19:12:22 JS: Need to present and publicise the UAWG - maybe need to talk about this at conferences etc. Look at conference that you are attending for opportunities to promote this. 19:12:45 HS: Can do this via twitter, blogging, and youtube. 19:14:10 SHarper: what about WWW conference, I'll be going 19:14:24 HS: I will be there also 19:16:37 action: JS to research whether the draft charter dates can be updated at this time. 19:16:37 Created ACTION-121 - Research whether the draft charter dates can be updated at this time. [on Jeanne Spellman - due 2009-02-12]. 19:17:14 zakim, close item 5 19:17:14 agendum 5, Glossary Review First 20 Items -, closed 19:17:14 zakim, take up item 4 19:17:15 I see 3 items remaining on the agenda; the next one is 19:17:16 6. Draft Charter review http://www.w3.org/WAI/UA/2008/draft_uawg_charter_20mar08.html [from AllanJ] 19:17:18 agendum 4. "ATIA report on UAAG20 poster session" taken up [from AllanJ] 19:17:41 zakim, take up item 5 19:17:41 agendum 5. "Glossary Review First 20 Items -" taken up [from AllanJ] 19:18:18 http://lists.w3.org/Archives/Public/w3c-wai-ua/2009JanMar/att-0009/UAAG_glossary_review.doc 19:18:51 mth has joined #ua 19:19:06 To execute the behaviour(s) associated with an enabled element rendered content or component of the user agent user interface. 19:19:20 To execute the behaviour(s) associated with an enabled element in the rendered content or component of the user agent user interface. 19:21:11 mth has joined #ua 19:21:52 RESOLVED: Activate - To execute the behaviour(s) associated with an enabled element in the rendered content or component of the user agent user interface. 19:21:58 action: JS to update glossary with new definition 19:21:58 Created ACTION-122 - Update glossary with new definition [on Jeanne Spellman - due 2009-02-12]. 19:22:52 A programmatic interface that is specifically engineered to provide communication between mainstream applications and assistive technologies (e.g., MSAA and IAccessible2 for Windows applications, AXAPI for MacOSX applications, Gnome Accessibility Toolkit API for Gnome applications, Java Access for Java applications, etc.). On some platforms it may be conventional to enhance communication... 19:22:54 ...further by implementing a DOM. 19:23:28 mth has joined #ua 19:24:00 q+ 19:24:35 MH: why 'mainstream' 19:24:56 JR: Just to differentiate between AT etc 19:25:19 JR: Can dig the ATAG definition for Mainstream 19:25:24 ack KFord 19:25:27 From ATAG 2.0: mainstream applications 19:25:29 Software applications for which augmenting accessibility is secondary to some other purpose (as opposed to assistive technology where it is the primary purpose). Mainstream technologies may include direct accessibility features. 19:25:51 KF: should list UIautomation in examples 19:26:07 KF: what are we trying to get with the last sentence? 19:27:01 JR: attempt to reconcile that DOMs are important in some cases - compromise language. 19:27:29 JA: can more the last sentence to the DOM / or objections to stay where it is (KF)? 19:28:53 KF: -1 mainstream 19:29:16 WCAG 2.0: hardware and/or software that acts as a user agent, or along with a mainstream user agent, to provide functionality to meet the requirements of users with disabilities that go beyond those offered by mainstream user agents 19:29:32 JS: -1 mainstream, add another cognitive layer 19:30:03 -1 mainstream 19:30:56 A programmatic interface that is specifically engineered to provide communication between applications and assistive technologies (e.g., MSAA, UI Automation, and IAccessible2 for Windows applications, AXAPI for MacOSX applications, Gnome Accessibility Toolkit API for Gnome applications, Java Access for Java applications, etc.). On some platforms it may be conventional to enhance communication furt 19:30:58 her by implementing a DOM. 19:32:17 JR: to take back ro ATAG - what should we use on a general basis - application / software ? 19:32:33 Confirming UI Automation is as I indicated UI Automation http://msdn.microsoft.com/en-us/accessibility/bb892133.aspx 19:32:38 JA: application - we've been using this throughout 19:32:54 JA: Leave at application 19:33:45 JR: Applications OK for now 19:34:55 RESOLVED: JR will look at this over the next week - postponed to next meeting 19:34:56 Platform Accessibility Architecture - A programmatic interface that is specifically engineered to provide communication between applications and assistive technologies (e.g., MSAA, UI Automation, and IAccessible2 for Windows applications, AXAPI for MacOSX applications, Gnome Accessibility Toolkit API for Gnome applications, Java Access for Java applications, etc.). On some platforms it may be conventional to enhance communication further by implementing a DOM. 19:35:07 Action JR: Look at "application" in the defn of platform accessibility architecture 19:35:07 Created ACTION-123 - Look at \"application\" in the defn of platform accessibility architecture [on Jan Richards - due 2009-02-12]. 19:35:36 action: to put the revised definition of platform accessibility architecture into next week's survey 19:35:36 Sorry, couldn't find user - to 19:35:44 -Mark_Hakkinen 19:35:45 -JR 19:35:51 -??P18 19:35:57 action: JS to put the revised definition of platform accessibility architecture into next week's survey 19:35:57 Created ACTION-124 - Put the revised definition of platform accessibility architecture into next week's survey [on Jeanne Spellman - due 2009-02-12]. 19:36:07 -sharper 19:36:09 -[Microsoft] 19:36:20 zakim, who's here? 19:36:20 On the phone I see Jeanne, AllanJ 19:36:21 On IRC I see mth, KFord, sharper, jeanne, RRSAgent, Zakim, AllanJ, trackbot 19:37:06 rrsagent, draft minutes 19:37:06 I have made the request to generate http://www.w3.org/2009/02/05-ua-minutes.html sharper 19:37:34 zakim, please part 19:37:34 Zakim has left #ua 19:37:35 leaving. As of this point the attendees were Jeanne, [Microsoft], +1.512.206.aaaa, JR, AllanJ, sharper, Mark_Hakkinen 19:37:55 RRSAgent, draft minutes 19:37:55 I have made the request to generate http://www.w3.org/2009/02/05-ua-minutes.html sharper 19:39:12 rrsagent, please part 19:39:12 I see 10 open action items saved in http://www.w3.org/2009/02/05-ua-actions.rdf : 19:39:12 ACTION: JR to Write-up a clarification of WHICH web apps are user agents and which are not. [1] 19:39:12 recorded in http://www.w3.org/2009/02/05-ua-irc#T18-50-14 19:39:12 ACTION: kf, mh to think about guideline to capture user agents embeded in desktop applications [2] 19:39:12 recorded in http://www.w3.org/2009/02/05-ua-irc#T18-58-36 19:39:12 ACTION: kford,mht to think about guideline around ensuring embedded user agents work correctly. [3] 19:39:12 recorded in http://www.w3.org/2009/02/05-ua-irc#T19-00-40 19:39:12 ACTION: kford to think about guideline around ensuring embedded user agents work correctly (includes MTH). [4] 19:39:12 recorded in http://www.w3.org/2009/02/05-ua-irc#T19-02-05 19:39:12 ACTION: kelly to think about guideline around ensuring embedded user agents work correctly (includes MTH). [5] 19:39:12 recorded in http://www.w3.org/2009/02/05-ua-irc#T19-02-29 19:39:12 ACTION: JS to research whether the draft charter dates can be updated at this time. [6] 19:39:12 recorded in http://www.w3.org/2009/02/05-ua-irc#T19-16-37 19:39:12 ACTION: JS to update glossary with new definition [7] 19:39:12 recorded in http://www.w3.org/2009/02/05-ua-irc#T19-21-58 19:39:12 ACTION: JR to Look at "application" in the defn of platform accessibility architecture [8] 19:39:12 recorded in http://www.w3.org/2009/02/05-ua-irc#T19-35-07 19:39:12 ACTION: to put the revised definition of platform accessibility architecture into next week's survey [9] 19:39:12 recorded in http://www.w3.org/2009/02/05-ua-irc#T19-35-36 19:39:12 ACTION: JS to put the revised definition of platform accessibility architecture into next week's survey [10] 19:39:12 recorded in http://www.w3.org/2009/02/05-ua-irc#T19-35-57