17:32:24 RRSAgent has joined #ua 17:32:24 logging to http://www.w3.org/2006/09/14-ua-irc 17:32:35 rrsagent, make logs public 17:43:22 regrets: D Poehlman 17:45:23 zakim, this will be wai_u 17:45:23 ok, jallan; I see WAI_UAWG()2:00PM scheduled to start in 15 minutes 17:46:27 Meeting: WAI UA 17:56:37 WAI_UAWG()2:00PM has now started 17:56:43 +Jim_Allan 17:59:26 +[IBM] 17:59:59 parente has joined #ua 18:00:05 zakim, [IBM] is Pparente 18:00:05 +Pparente; got it 18:01:07 +[IBM] 18:01:13 JR has joined #ua 18:01:31 zakim, [IBM] is cklaws 18:01:31 +cklaws; got it 18:01:55 cklaws has joined #ua 18:02:15 +Jan_Richards 18:02:39 scribe: JR 18:05:27 JA, CL General comments on how quickly things are moving forward...same prob of people devving new techs not taking into account access 18:05:39 Topic: 6.8 API character encodings (P1) 18:06:26 JA: my note was just that Unix was missing 18:07:22 PP: Everything back from UTSPI in UTF-8 18:07:55 PP: Then based on users locale put in appropriate lang 18:08:18 PP: IBM speech engine expects unicode in char set it knows about 18:09:48 JR: does this really need to be here. checkpoint just supports the API 18:10:23 cl: get informatoin from DOM or accessibility interface. when you send info to speech engine, you must convert to ascii 18:10:48 CL: When getting info out of API and into speech engine etc. a conversion is often required 18:10:54 UA is not helping, AT does all the work 18:11:20 PP: If UTF-8 is being sent a locale also must be sent 18:11:40 JA: From HTML lang element? 18:11:44 CL, PP: No 18:11:53 ...but not sure from where 18:13:07 PP: Discussing with AL yesterday about how to deal with docs made of text in several langs 18:13:52 PP: Looking at defaults... 18:14:15 ...defaukts to ISO-8859 but there is also auto-detect setting 18:14:34 CL: AL they get it from HTTP or lang attribute 18:14:53 JA: Meta tag? 18:15:00 CL: Or doctype? 18:15:10 PP: In XML tag as well 18:15:27 CL: So yes coming from what author says in web page 18:15:44 JA: Checkpoint seems wide open 18:16:14 CL: But may want to say something about lang and locale...we should say who benefits...speech engines 18:16:45 action CL: Write a bit about speech engines and braille devices needing lang and locale info 18:17:46 JA: so 8859 is just latin languages. 18:18:39 PP: And yes there are Chinese and Japanese speech engines etc. 18:19:33 CL: Just saying browser has to be able to pick up info supplied by author and give it to the ATs 18:20:18 PP: Linux ATK tells locale 18:21:07 PP: UTF-16 is yet another unicode encoding 18:22:30 JA: Are speech engines moving towards additional char set supports? 18:23:45 PP: From actual checkpoint, browser has to be able to encode strings in form API wants 18:26:47 CL: Browesr could help out by providing the locale 18:27:27 Topic: 6.9 DOM access to CSS style sheets (P2) 18:28:02 JA: So AL said we can't necessarily do thi. 18:28:36 JR: CL's msg: http://lists.w3.org/Archives/Public/w3c-wai-ua/2006JulSep/0045.html 18:28:53 CL: DOM not supposed to worry about presentation info 18:29:17 JA: And prob is that CSS allows content to be added 18:30:51 JA: Really tied up in AJAX and DHTML 18:31:08 JA: Scripting changing style sheets... 18:31:16 CL: No solution yet 18:31:55 action JA: Follow up on 2 issues with 6.9 - events and content insertion 18:32:22 CL: In that conversatrion Rich suggests getting CSS people to look at it 18:33:42 JA: At plenary Rich was suggesting a joint meeting on this 18:34:44 JA: ALso concerned this is a p2...given the new stuff 18:34:57 JA: This stuff is going to be critical 18:35:17 Topic: 6.10 Timely exchanges through APIs (P2) 18:36:34 JA: HPR have font or colour ability? 18:36:48 CL: Possible to get this from native API 18:37:05 CL: But today the goal is to get everything via access API 18:37:51 JR: My comment is "WHat's timely?" - more of a technique for other checkpoints 18:38:14 JA: Yes...rationale just says "play well with others" 18:38:51 CL: To us this means providing via an engineered API rather than a text sream. 18:39:29 CL: Pref event when things happen rather than having to detect 18:40:29 cl: want api to send semantic information to other API rather than a text string 18:42:16 cl: semantics=content + event + location 18:43:50 CL: DOM spec is implemented by browser - that's the engineered API 18:44:04 cl: using DOM spec to design API for each UA, need to have semantics built in to UA implemented API 18:44:22 Barry F. says in ATAG 2.0 "accessibility platform architecture(s)" 18:44:24 http://www.w3.org/WAI/AU/2006/WD-ATAG20-20060629/WD-ATAG20-20060629.html#gl-tool-accessible-atfriendly 18:45:04 CL: If following DOM spec then semantics are built in 18:46:32 CL: eg. many Windows browsers expose both a DOM and to MSAA 18:47:32 CL: Firefox on Linux doesn't expose DOM, but instead exposes via access API 18:48:23 CL: Maybe will look at ATAG for possible wording 18:49:46 CL: "Timely" would seem to indicate events - otherwise how do you know 18:50:53 PP: ex. an instant message system that doesn't notify user of msg right away 18:52:52 JR: Maybe some objective limit based on response time research 18:53:13 CL: IBM testers were ok with delays of 2-3 seconds 18:54:07 JR: Also relates to input 18:54:24 CL: Many factors including internet communication etc. 18:54:40 JA: Maybe timely is the best word for now? 18:54:54 PP: We could provide examples of what not to do 18:56:43 action PP: Write up a few examples of situations where an API exchange is too slow 18:57:31 JA: Next mtg in 2 wks 18:57:38 JA: Will pick up with 7 18:58:38 action JA: update review chart and send to list 18:58:49 -cklaws 18:58:51 -Pparente 19:00:18 -Jim_Allan 19:00:20 -Jan_Richards 19:00:22 WAI_UAWG()2:00PM has ended 19:00:23 Attendees were Jim_Allan, Pparente, cklaws, Jan_Richards 19:00:45 jallan has left #ua 19:15:19 RRSAgent, make minutes 19:15:19 I have made the request to generate http://www.w3.org/2006/09/14-ua-minutes.html JR 19:15:25 RRSAgent, set logs public 19:15:33 Zakim, bye 19:15:33 Zakim has left #ua 19:15:56 RRSAgent, bye 19:15:56 I see 4 open action items saved in http://www.w3.org/2006/09/14-ua-actions.rdf : 19:15:56 ACTION: CL to Write a bit about speech engines and braille devices needing lang and locale info [1] 19:15:56 recorded in http://www.w3.org/2006/09/14-ua-irc#T18-16-45 19:15:56 ACTION: JA to Follow up on 2 issues with 6.9 - events and content insertion [2] 19:15:56 recorded in http://www.w3.org/2006/09/14-ua-irc#T18-31-55 19:15:56 ACTION: PP to Write up a few examples of situations where an API exchange is too slow [3] 19:15:56 recorded in http://www.w3.org/2006/09/14-ua-irc#T18-56-43 19:15:56 ACTION: JA to update review chart and send to list [4] 19:15:56 recorded in http://www.w3.org/2006/09/14-ua-irc#T18-58-38