17:31:23 <RRSAgent> RRSAgent has joined #ua
17:31:23 <RRSAgent> logging to http://www.w3.org/2006/10/12-ua-irc
17:31:41 <jallan> Meeting: UAWG teleconference
17:31:48 <jallan> scribe: JA
17:31:59 <jallan> regrets: JR
17:33:28 <jallan> agenda: http://lists.w3.org/Archives/Public/w3c-wai-ua/2006OctDec/0005.html
18:00:32 <Zakim> WAI_UAWG()2:00PM has now started
18:00:39 <Zakim> +Jim_Allan
18:01:48 <Zakim> +[IBM]
18:02:07 <parente> parente has joined #ua
18:02:13 <jallan> zakim, [IBM] is parente
18:02:13 <Zakim> +parente; got it
18:03:21 <Zakim> +[IBM]
18:03:44 <cklaws> cklaws has joined #ua
18:03:45 <jallan> zakim, [IBM] is cklaws
18:03:45 <Zakim> +cklaws; got it
18:05:29 <jallan> PP: reviewed mozilla and Gnome conference...
18:05:44 <jallan> scribe: jallan
18:06:21 <parente> WAI-ARIA
18:06:31 <jallan> there was some discussion about AJAX and ARIA
18:06:47 <jallan> http://www.w3.org/2006/08/backplane/
18:11:40 <jallan> http://www.w3.org/2005/Incubator/wcl/XGR-report/
18:14:57 <jallan> topic:  8.1 Implement Accessiblity Features (P1)
18:15:59 <jallan> add references to HTML and XHTML
18:17:27 <jallan> CL: not clear how <col> and <colgroup> enable accessibility
18:20:19 <jallan> CL: UAAG test suite item #195 about <col> and <colgroup>, does not make sense
18:21:31 <jallan> what kind of information are we trying to convey to the user about the relationship of columns in a colgroup. what is the UA supposed to communicate to the user?
18:22:25 <jallan> CL: need to figure out how they benefit accessibiltiy., if no benefit then remove from techniques. 
18:23:08 <jallan> if beneficial, then describe information provided to the user
18:23:23 <jallan> need to provide examples
18:24:23 <jallan> Should we include tabindex and accesskey. both are confusing to end users
18:30:17 <jallan> Action: JA add references to HTML and XHTML
18:32:06 <jallan> Action: JA issues col, colgroup, thead, tbody, tfoot, accesskey, tabindex. benefit accessibilty? are there accessibilty examples in WCAG or HTML?
18:33:41 <jallan> CL: although tabindex=-1 and accesskey are used significantly in AJAX and HTML
18:33:55 <jallan> thats DHTML not html
18:34:22 <jallan> Action: JA add comments - although tabindex=-1 and accesskey are used significantly in AJAX and HTML
18:34:48 <jallan> topic: 8.2 conform to specifications (p2)
18:39:43 <jallan> this is very vague and confusing. You can pick and choose which specification to conform 
18:40:50 <jallan> action: JA issue: does 8.2 need to be removed due to vagueness
18:42:20 <jallan> Topic: 9.1 Provide content focus (p1)
18:43:14 <jallan> no techniques.  
18:44:17 <jallan> CL: AJAX and DHTML using tabindex=-1 to allow focus on non-focusable elements
18:44:57 <jallan> there is work on style guide for DHTML elements for keyboard navigation and focus
18:46:11 <jallan> CL: may need techniques for using javascript to move content focus
18:49:51 <jallan> action: JA issue: update defintions of "enabled elements" and "interactive elements" to provide for components used in DHTML
18:50:19 <jallan> action: JA reference WCAG 2 for techniques
18:51:12 <jallan> CL: where is the line drawn between what the UA vs author coding should do to provide for accessibility
18:51:35 <jallan> action: JA issue where is the line drawn between what the UA vs author coding should do to provide for accessibility
18:53:30 <jallan> CL: UA responsibiltiy to generate focus for elements so accessiblity api can provide info to the AT
18:56:37 <jallan> discussion of caret browsing in documents
19:03:32 <Zakim> -cklaws
19:03:34 <Zakim> -parente
19:03:36 <Zakim> -Jim_Allan
19:03:37 <Zakim> WAI_UAWG()2:00PM has ended
19:03:38 <Zakim> Attendees were Jim_Allan, parente, cklaws
19:04:04 <jallan> rrsagent, make minutes
19:04:04 <RRSAgent> I have made the request to generate http://www.w3.org/2006/10/12-ua-minutes.html jallan
19:04:23 <jallan> rrsagent, set logs public
19:09:51 <jallan> jallan has left #ua
20:20:14 <Zakim> Zakim has left #ua