14:04:13 RRSAgent has joined #wai-wcag 14:04:49 zakim, who's on the phone? 14:04:49 On the phone I see Don_Evans, [Microsoft], ??P4, Jim_Thatcher, Becky_Gibson, Michael_Cooper, Sailesh_Panchang 14:05:12 zakim, ??P4 is Chris_Ridpath 14:05:12 +Chris_Ridpath; got it 14:06:37 -- navigation approaches & use cases -- 14:06:38 http://lists.w3.org/Archives/Public/w3c-wai-gl/2004AprJun/0333.html 14:06:45 http://lists.w3.org/Archives/Public/w3c-wai-gl/2004AprJun/0457.html 14:07:57 Becky took Tom's personae and tried to make real world examles 14:08:59 zakim, [Microsoft] is temporarily Jenae_Andershonis 14:08:59 +Jenae_Andershonis; got it 14:09:33 would like to get from guidelines to techniques and back 14:09:39 or from guidelines to checklists 14:10:23 may need to go from document to document to get clarity on specific questions 14:10:30 tried one to use traffic cop 14:12:25 Same question as last week: not sure on difference between tech-independent techniques and techniques repository 14:12:52 Would like to be able to go directly from checklists to techniques repository 14:13:13 Not sure in diagram from last week what entry point into repository is 14:14:28 action: Becky create a revised picture based on her use cases 14:18:32 In last of Becky's scenarios, person comes from guideline and wants to go to techniques - how do they do that? 14:18:55 relates to linking guidelines to techniques http://lists.w3.org/Archives/Public/w3c-wai-gl/2004AprJun/0191.html 14:20:02 Process of linking guidelines to techniques through traffic cop 14:20:36 Do we link from traffic cop to guidelines? 14:20:47 Or do we also provide links to checklists and techniques? 14:21:25 Also when do you get from non-tech specific to tech-specific 14:22:13 Do we need to link out from guidelines to everything, or just to traffic cop? 14:23:54 We need to understand where there is a 1:1 vs. a 1:many relation 14:25:04 that can determine how we present linkages 14:28:04 Also there are possibly multiple guidelines per technique, therefore many:many relations 14:28:10 but need to keep things simple 14:28:59 make a constraint that we only define one guideline per technique - strongest one - to maintain the 1:many status 14:30:48 Perhaps everything links into traffic cop, from which you can get to whichever related document you want 14:30:56 It's two hops, but it might be clearer where you're going 14:33:59 David's traffic cop proposal: http://www.eramp.com/david/traffic_cop_prototype_staticc_no_rows.htm 14:34:44 add checklists to this 14:35:06 make guideline links live 14:35:21 How do people get to test cases? 14:36:02 Add a field to traffic cop for test cases? 14:36:09 Link from techniques? 14:37:21 Need updated prototypes of all this 14:38:06 action: Michael, Jenae: create updated prototype of Guidelines link to traffic cop, and links to techniques, checklists, and test cases 14:39:14 +??P0 14:39:33 zakim, ??P0 is David_MacDonald 14:39:33 +David_MacDonald; got it 14:40:37 If we have checklists, would they be in their own field or tied to the technology specific techniques? 14:46:39 action 1 = Becky, David create a revised picture based on her use cases 14:49:06 -- end-to-end -- 14:49:16 http://lists.w3.org/Archives/Public/w3c-wai-gl/2004AprJun/att-0054/gateway-outline.htm 14:49:23 http://lists.w3.org/Archives/Public/w3c-wai-gl/2004AprJun/0158.html 14:55:01 were expecting additional analysis from last week but not yet completed 14:55:09 postponing this agendum 14:59:40 -- table headers, layout vs css, and summary and caption -- 15:00:11 http://lists.w3.org/Archives/Public/w3c-wai-gl/2004AprJun/0327.html 15:00:55 Summary attribute gives additional information to an AT user 15:01:06 it describes something that visually you can take in at a glance 15:01:21 non-null summary therefore important for data tables 15:02:03 Is summary in addition to or instead of TH to identify data table? 15:04:42 not specifically either 15:05:01 Most recent list discussion was that summary was optional on data tables, and null/absent on layout tables 15:06:08 Should a summary that describes the data table always be present? 15:06:30 useful for large tables, less necessary for small tables 15:06:38 how onerous is it for developers? 15:07:18 Only require summary on complex tables? 15:07:22 then we have to define that 15:07:57 ...multiple rows/cols of headers, and heading for data cell is not in same row and column as the cell 15:08:22 Second part of that definition the only important part? 15:12:35 line between complexity for headers, and complexity for summary 15:13:11 CAPTION should describe what table contains, and summary should summarize the layout/organization of information 15:16:39 CAPTION is for everybody 15:16:45 summary is mainly for screen reader users 15:20:41 Imagine a "perfect" table: has a CAPTION, meaningful and brief summary, TH for all headers, and additional header markup if needed 15:20:55 Don't like to require CAPTION because of visual impact 15:21:14 CSS to hide possible, but current UA support leads to that being unavailable in screen readers also 15:23:53 BeckyG has joined #wai-wcag 15:24:22 If UA support were working, would we be comfortable requiring CAPTION but hiding it visually if desired? 15:24:40 No - it's defined as a visual element 15:24:55 Which of these features make an actual difference to users? 15:24:57 Summary 15:25:28 TH - UA will read "headers" even if absent but presence can still help 15:29:19 -Chris_Ridpath 15:29:24 ChrisR has left #wai-wcag 15:30:27 Do we unanimously agree that TH should always be required? 15:30:44 can live with it, but don't like to require something that doesn't make a measurable impact for users 15:30:54 Do we unanimously agree that summary should always be required? 15:31:13 no, should only be required for complex tables - but we need to define that 15:32:25 What if we say either caption or summary is required (caption preferred, and summary desired for complex tables) 15:32:49 summary *required* for complex tables 15:34:30 This doesn't draw the ideal distinction between caption (visual design element) and summary (*quick* description of what is available through a visual scan) 15:38:54 Two definitions of summary: 15:39:13 1) Summarizes what can be taken in at a glance - very short 15:39:42 2) Describes the organization, row/col headers, etc. to give navigational advice 15:46:00 refer to http://lists.w3.org/Archives/Public/w3c-wai-gl/2004AprJun/0377.html 15:49:47 action: Michael post the various definitions of summary and caption to get discussion started 15:53:03 -Jenae_Andershonis 15:57:11 TH is to be required for all data tables 15:57:31 notwithstanding objection that doesn't a difference in current UA 15:58:27 and even when in complex tables headers/id used, still the header cells need to be TH 15:59:54 -Becky_Gibson 15:59:55 -Don_Evans 15:59:55 -Jim_Thatcher 15:59:56 -Michael_Cooper 15:59:56 -Sailesh_Panchang 15:59:57 -David_MacDonald 15:59:57 WAI_WCAG(techniques)10:00AM has ended 15:59:59 Attendees were Don_Evans, Jim_Thatcher, Becky_Gibson, Michael_Cooper, Sailesh_Panchang, Chris_Ridpath, Jenae_Andershonis, David_MacDonald 16:00:11 rrsagent, make log world-visible 16:00:19 rrsagent, bye 16:00:19 I see 3 open action items: 16:00:19 ACTION: Becky, David create a revised picture based on her use cases [1] 16:00:19 recorded in http://www.w3.org/2004/05/19-wai-wcag-irc#T14-14-28 16:00:19 ACTION: Michael, Jenae: create updated prototype of Guidelines link to traffic cop, and links to techniques, checklists, and test cases [2] 16:00:19 recorded in http://www.w3.org/2004/05/19-wai-wcag-irc#T14-38-06 16:00:19 ACTION: Michael post the various definitions of summary and caption to get discussion started [3] 16:00:19 recorded in http://www.w3.org/2004/05/19-wai-wcag-irc#T15-49-47