15:49:03 RRSAgent has joined #ua 15:49:03 logging to http://www.w3.org/2010/10/07-ua-irc 15:49:05 RRSAgent, make logs public 15:49:05 Zakim has joined #ua 15:49:07 Zakim, this will be WAI_UAWG 15:49:07 I do not see a conference matching that name scheduled within the next hour, trackbot 15:49:08 Meeting: User Agent Accessibility Guidelines Working Group Teleconference 15:49:08 Date: 07 October 2010 16:04:09 zakim, this will be UA 16:04:09 ok, jallan; I see WAI_UAWG()1:00PM scheduled to start in 56 minutes 16:16:59 chair: JimAllan_KellyFord 16:26:45 Agenda+ Action Item Review Agenda+ Are Smart Phone Apps user agents? Agenda+ Media Review followup - possible additions to UAAG http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0002.html Agenda+ Tooltips - device agnosticism [bug 10873] http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0003.html Agenda+ November F2F Agenda+ Browser Implementations 16:27:41 zakim, agenda? 16:27:41 I see 1 item remaining on the agenda: 16:27:43 1. Action Item Review Agenda+ Are Smart Phone Apps user agents? Agenda+ Media Review followup - possible additions to UAAG 16:27:46 ... http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0002.html Agenda+ Tooltips - device agnosticism [bug 10873] 16:27:48 ... http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0003.html Agenda+ November F2F Agenda+ Browser Implementations [from jallan] 16:28:07 zakim, remove item 1 16:28:07 agendum 1, Action Item Review Agenda+ Are Smart Phone Apps user agents? Agenda+ Media Review followup - possible additions to UAAG 16:28:09 ... http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0002.html Agenda+ Tooltips - device agnosticism [bug 10873] 16:28:12 ... http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0003.html Agenda+ November F2F Agenda+ Browser Implementations, dropped 16:28:38 Agenda+ Action Item Review 16:28:50 Agenda+ Are Smart Phone Apps user agents? 16:29:04 Agenda+ Media Review followup - possible additions to UAAG http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0002.html 16:29:18 Agenda+ Tooltips - device agnosticism [bug 10873] http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0003.html 16:32:09 Agenda+ November F2F 16:32:22 Agenda+ Browser Implementations 16:56:54 patrickhlauke has joined #ua 16:58:09 Greg has joined #ua 16:58:40 WAI_UAWG()1:00PM has now started 16:58:48 + +44.797.663.aaaa 16:58:51 + +1.512.206.aabb 16:59:33 zalo, aabb is really jallan 16:59:46 zakim, aabb is really jallan 16:59:46 +jallan; got it 16:59:58 + +1.425.895.aacc 17:00:00 -jallan 17:00:03 zakim, aaaa is patrickhlauke 17:00:03 +patrickhlauke; got it 17:00:27 zakim, aacc is really me 17:00:27 +Greg; got it 17:00:32 is my microphone not working, or is it the phone bridge? 17:00:32 +jallan 17:00:34 +[Microsoft] 17:01:02 i can hear you folks, but you can't hear me 17:01:06 hmm 17:01:11 ok 17:01:14 -patrickhlauke 17:02:02 sharper has joined #ua 17:02:20 +patrickhlauke 17:02:30 Zakim, code? 17:02:30 the conference code is 82941 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), sharper 17:03:26 +??P8 17:03:51 zakim, ??P8 is sharper 17:03:51 +sharper; got it 17:04:46 +Jeanne 17:05:30 jeanne has joined #ua 17:06:18 zakim, who is here? 17:06:18 On the phone I see Greg, [Microsoft], jallan, patrickhlauke, sharper, Jeanne 17:06:20 On IRC I see jeanne, sharper, Greg, patrickhlauke, Zakim, RRSAgent, jallan, trackbot 17:06:57 scribe: jallan 17:07:09 zakim, Microsoft is kford 17:07:09 +kford; got it 17:08:11 zakim, agenda? 17:08:11 I see 6 items remaining on the agenda: 17:08:12 2. Action Item Review [from jallan] 17:08:14 3. Are Smart Phone Apps user agents? [from jallan] 17:08:16 4. Media Review followup - possible additions to UAAG http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0002.html [from jallan] 17:08:20 5. Tooltips - device agnosticism [bug 10873] http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0003.html [from jallan] 17:08:23 6. November F2F [from jallan] 17:08:24 7. Browser Implementations [from jallan] 17:08:29 zakim, take up item 2 17:08:29 agendum 2. "Action Item Review" taken up [from jallan] 17:15:55 discussion of action items 17:27:11 +Kim_Patch 17:30:01 close action-247 17:30:01 ACTION-247 And MH to create techniques for 4.9 by December 3 closed 17:30:35 KimPatch has joined #ua 17:36:00 close action-268 17:36:00 ACTION-268 Craft request for input on synthesized speech inclusion in the document closed 17:36:06 close action-269 17:36:06 ACTION-269 Answer comment saying that we think section 3.6.1 covers the comment. closed 17:36:19 close action-286 17:36:19 ACTION-286 Create use case for no-script etc. for implementation doc closed 17:36:35 close action-289 17:36:36 ACTION-289 Write a success criteria for viewport scaling (text, images) closed 17:38:09 close action-291 17:38:09 ACTION-291 Write SC for user ability to open a plugin or open external player. closed 17:43:32 close action-319 17:43:32 ACTION-319 Copy edit draft with JS to normalize document and establish conventions closed 17:44:08 http://www.w3.org/2010/03/04-ua-minutes.html#item06 17:46:29 stopped review at item 329 (start with this next time) 17:46:38 zakim, close item 2 17:46:38 agendum 2, Action Item Review, closed 17:46:39 I see 5 items remaining on the agenda; the next one is 17:46:40 3. Are Smart Phone Apps user agents? [from jallan] 17:46:57 zakim, agenda? 17:46:57 I see 5 items remaining on the agenda: 17:46:58 3. Are Smart Phone Apps user agents? [from jallan] 17:47:00 4. Media Review followup - possible additions to UAAG http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0002.html [from jallan] 17:47:04 5. Tooltips - device agnosticism [bug 10873] http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0003.html [from jallan] 17:47:07 6. November F2F [from jallan] 17:47:08 7. Browser Implementations [from jallan] 17:47:44 zakim, open item 5 17:47:44 agendum 5. "Tooltips - device agnosticism [bug 10873] http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0003.html" taken up [from jallan] 17:48:40 gl: do we need an example about tooltips 17:49:22 ja: no hover on touch screens 17:49:49 pl: there is some discussion on how to implement hover in OS 17:51:25 js: should not decrease functionality because it is not suppored in tablets 17:51:48 js: would rather touchscreen develop a hover function 17:52:30 gl: does make sense to have an efficient UI for commonly used functions 17:53:02 GL: things that people want to do a lot should also have a pointer-only method of accomplishing it. 17:53:32 ... for headpointer, and voice input etc. need a hover function 17:54:34 Should we add a recommendation to include an efficient method of carrying out frequently-used tasks using each supported input mode (e.g. keyboard, mouse, touch screen, speech). Keyboard (or keyboard equivalent)” is of course the most important because keyboard equivalent makes it device independent, but the others can be recommendations. 17:55:31 Having optimized methods for pointing device and touchscreen are very useful for people using head pointers, etc. 17:55:47 pl: been talking for years about not using mouse over, etc, nobody listened. now with iphone, they have begun to listen. 17:57:01 ...how to rework GL 4.1 to make more device agnostic. change to 'keyboard and keyboard like interfaces (pointers, touch screen, etc) 17:58:02 gl: in ISO use keybard or keybard equivelent throught the ISO document 17:58:43 sh: no matter the interface, the os generates keyboard scan code, and sends that to the OS for activation 17:58:56 The answer is that by “keyboard” we always mean “keyboard or keyboard equivalent”; however, it is true that (a) this only makes features accessible, not necessarily convenient, and (b) UAAG20 does not currently *say* that keyboard means “keyboard (or keyboard-equivalent)”. ISO 9241-171 actually uses the phrase “keyboard (or keyboard-equivalent)” throughout. I recommend we do... 17:58:58 ...the same. 17:59:29 ...all keys have a scan code, when you select something the scancode is sent to the OS for activation 17:59:44 ...even mouse clicks do this 18:01:11 I don't support using the term "scan code" because that really applies only to low-level keyboard emulation, but keyboard emulation can also be done at a high level (e.g. events). Also, most readers won't understand the term "scan code" whereas most would understand "keyboard (or keyboard emulator)". 18:01:12 pl: problem with touchscreen, functions much like a mouse, but no hover. poor heurestics-touch and smear, or have a long touch 18:02:19 sh: voiceover users keyboard emulation 18:03:00 gl: scancode only applies to low level activity 18:03:43 still not sure how touchscreen navigation (scrolling, activating with a tap, long-tapping for context) can be squared with keyboard/keyboard-like language 18:03:58 kf: UAAG wants to be device agnostic. yet, 4.1 is all keyboard. 18:04:07 and in fact, do we need guidance on mouse interfaces? 18:04:13 sharper has left #ua 18:04:34 ...how to not waterdown 4.1, yet cover nne keyboard devices 18:05:14 ... things that happen on webpages today were not functional with smartphones a year ago. 18:05:45 if i was a radical, i'd say the title of guideline 4.1 should be "ensure full access" (with all available input modalities) 18:05:52 ... smartphone UA have gotten smarter (js, etc.) 18:06:13 kf: what do we say to cover present functioning and the future. 18:06:28 -sharper 18:06:50 and then split into the various prominent modalities, with explanation (e.g. what is keyboard, with definition of kbd-like modalities) 18:06:55 ...topic for face to face- touch tablet 18:07:10 kf: also do we write a response. 18:08:54 action: Jeanne to draft a response to the HTML5 bug on device independence, tooltip and hover functions. 18:08:55 Created ACTION-454 - Draft a response to the HTML5 bug on device independence, tooltip and hover functions. [on Jeanne Spellman - due 2010-10-14]. 18:09:06 zakim, close item 5 18:09:06 agendum 5, Tooltips - device agnosticism [bug 10873] http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0003.html, closed 18:09:09 I see 4 items remaining on the agenda; the next one is 18:09:10 3. Are Smart Phone Apps user agents? [from jallan] 18:09:50 zakim, open item 6 18:09:50 agendum 6. "November F2F" taken up [from jallan] 18:10:43 dates are November 9 & 10 18:10:55 zakim, close item 6 18:10:55 agendum 6, November F2F, closed 18:10:56 I see 3 items remaining on the agenda; the next one is 18:10:57 3. Are Smart Phone Apps user agents? [from jallan] 18:11:05 zakim, agenda? 18:11:05 I see 3 items remaining on the agenda: 18:11:07 3. Are Smart Phone Apps user agents? [from jallan] 18:11:08 4. Media Review followup - possible additions to UAAG http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0002.html [from jallan] 18:11:10 7. Browser Implementations [from jallan] 18:11:34 zakim, open item 3 18:11:34 agendum 3. "Are Smart Phone Apps user agents?" taken up [from jallan] 18:12:54 gl: don't understand question. they all sit on the OS 18:13:06 js: some are 18:13:55 kf: example of traffic detail app, it is using web servicess. 18:14:22 gl: some apps use internet applications, others use web protocols and are user agents 18:14:57 "user agent 18:14:57 A user agent is any software that retrieves, renders and facilitates end user interaction with Web content." 18:14:59 ja: http is web app, but udp is not 18:15:17 is that the cut-off point? 18:16:03 js: this is related to secondlife. general concensus...if something uses uri then it needs a user agent 18:16:52 pl: perhaps need to define 'web content' (html, css, js, flash, etc.) 18:16:55 ...interaction with content 18:17:12 kf: what about twitter apps 18:17:33 js: it uses webconent, it facilitates interaction 18:18:14 pl: not a webapp, just pulling info out of a ddatabase, in an app 18:18:35 ...may be splitting hairs. 18:18:36 ja: its all about splitting hairs. 18:18:38 It seems that all applications--for any platforms--fits into one of three categories: stand-alone apps that don't interact with the network or use W3C protocols or formats (i.e. standalone apps); apps that use networking but not W3C protocols or formats (i.e. Internet apps); and those that do use W3C protocols or formats (i.e. Web apps). The problem is that these distinctions are usually... 18:18:40 ...transparent to the user. Two apps might be entirely identical to the user, but because one uses W3C standards "under the hood" while the other does not, only one is theoretically covered by UAAG. 18:18:55 kf: many tweets have urls, that can be opened with full browser 18:20:03 pl: twitter sending url to UA is still not a UA, if the url opens in twitter, then it is a UA and should comply 18:21:41 "content (web content) includes empty content 18:21:41 Information and sensory experience to be communicated to the user by means of a user agent, including code or markup that defines the content's structure, presentation, and interactions [adapted from WCAG 2.0] 18:21:41 empty content (which may be alternative content) is either a null value or an empty string (e.g. one that is zero characters long). For instance, in HTML, alt="" sets the value of the alt attribute to the empty string. In some markup languages, an element may have empty content (e.g., the HR element in HTML)." 18:21:47 I sort of want to avoid the term "web application", because I believe UAAG is supposed to apply to, say, SVG viewers even if they don't have any built-in network or Web awareness, *because* SVG is a W3C standard. 18:22:03 ja: need to define 'web content' , just because something goes over the ethernet cable does not make it webcontent (skype, im, etc) 18:23:08 pl: pl: murky definition 18:24:45 js: web content = has uri/url 18:26:06 gl: standalone app that plays flash. but if it transfers stuff over web, using w3 protocols 18:26:23 pl: looking at wcag2, define webpage, but not content 18:26:59 http://www.w3.org/TR/WCAG20/#webpagedef 18:27:24 wcag skirted around "what is web content" and instead defines "web page" though their intro text still talks about web content 18:27:28 So, my current leaning is still towards saying UAAG applies to any software that uses W3C protocols or formats. (But I agree that leaves out software that renders proprietary formats such as Flash players, unless they transfer data over using Web protocols such as using URIs.) 18:29:00 pl: if we don't define what we apply to, we leave ourselve open for ?criticism? 18:29:22 gl: but compliance is voluntary, so may not need to define. 18:30:17 I hope we don't need to provide an objective definition of what UAAG applies to because it's up to a developer to decide whether or not they want to claim compliance, and up to a purchasing organization to decide for which products or product categories they want to require compliance. 18:31:27 pl: we don't give athorative definintion of webcontent, here is what we think it is, if you think your device, applicatoin covers this then it is a UA 18:33:07 suggest saying specifically in UAAG intro to say we don't give authoritive definition of "what is web content", and that UA authors need to decide for themselves, if they want to claim compliance, if their UA is using "web content" 18:33:47 s/athorative/authoratative 18:35:14 gl: discuss 'raising the floor" and/or NPII to see how we can leverage, or overlap 18:35:50 s/definintion/definition 18:42:50 (gonna have to dip out, not wanting to break up your interesting - though offlist - discussion ... speak soon tho) 18:42:56 -patrickhlauke 18:43:46 patrickhlauke has left #ua 18:47:10 zakim, who is here? 18:47:10 On the phone I see Greg, kford, jallan, Jeanne, Kim_Patch 18:47:11 On IRC I see KimPatch, jeanne, Greg, Zakim, RRSAgent, jallan, trackbot 18:53:18 -Kim_Patch 18:53:19 -kford 18:53:21 -jallan 18:53:31 -Greg 18:53:41 -Jeanne 18:53:42 WAI_UAWG()1:00PM has ended 18:53:44 Attendees were +44.797.663.aaaa, +1.512.206.aabb, jallan, +1.425.895.aacc, patrickhlauke, Greg, sharper, Jeanne, kford, Kim_Patch 18:54:05 rrsagent, make minutes 18:54:05 I have made the request to generate http://www.w3.org/2010/10/07-ua-minutes.html jeanne 18:54:14 rrsagent, make logs public 20:43:01 jeanne has joined #ua