12:33:00 RRSAgent has joined #eo 12:33:00 logging to http://www.w3.org/2005/05/20-eo-irc 12:33:02 +Henk 12:33:44 zakim, aaaa is Ron_Armstrong 12:33:44 +Ron_Armstrong; got it 12:34:26 Harvey has joined #eo 12:34:51 +Carol 12:35:15 +Jack 12:35:32 zakim, who is here? 12:35:32 On the phone I see Doyle_Saylor, Ron_Armstrong, Sylvie_Duchateau (muted), Judy, ??P4, Bingham, ??P6, ??P7, ??P8, Shawn, Henk, Carol, Jack 12:35:34 On IRC I see Harvey, RRSAgent, Zakim, JackW, Wayne, Andrew, shawn, judy, pasquale, shadi 12:35:56 present: Pasquale, Barry, Andrew, Carol, Jack, Ron, Wayne, Judy, Shawn, Henk, Doyle, Sylvie 12:36:09 carol has joined #eo 12:37:28 Present+ Harvey 12:37:43 meeting: EOWG 12:37:46 chair: Judy 12:38:28 +Shadi 12:39:32 scribe: Wayne 12:40:04 present+ Shadi 12:40:21 +Helle_Bjarno 12:40:30 present+ Helle 12:41:09 Topic Outreach 12:41:30 Helle has joined #eo 12:41:36 aegnda: http://lists.w3.org/Archives/Public/w3c-wai-eo/2005AprJun/0084.html 12:41:37 There was no activity this week. 12:43:36 Topic Introduction 12:45:45 achuter has joined #eo 12:47:01 zakim, please mute me 12:47:01 Helle_Bjarno should now be muted 12:47:05 Justin has joined #eo 12:48:54 Topic: Outreach 12:49:02 Topic: Introduction 12:49:51 +Loughborough 12:50:09 -Loughborough 12:50:55 +??P14 12:50:56 +Loughborough 12:51:11 Topic: (changed from agenda order) Lexicon 12:51:40 zakim, ??P14 is Justin 12:51:40 +Justin; got it 12:51:46 zakim, please mute me 12:51:46 Justin should now be muted 12:52:29 +Alan 12:53:23 zakim, please unmute me 12:53:23 Helle_Bjarno should no longer be muted 12:55:54 Henk: Sent around updated version of Lexicon final words. There are four choices of two definitions that are not agreed upon. 12:56:17 i prefer a) 12:56:39 I prefer A as well 12:56:51 First word Assistive Technology (a) More detail (b) less detail --- (a) wins the vote. 12:57:42 zakim, mute me 12:57:42 sorry, achuter, I do not see a party named 'achuter' 12:57:44 -Loughborough 12:58:06 informative: i prefer a) 12:58:53 I vote for three times a) 12:59:52 Informative: (a) , (b) starts with describing... (a) 13:00:18 non-normative: i prefer a) 13:01:16 Present+ Alan, Justin 13:02:11 zakim, please mute me 13:02:11 Helle_Bjarno should now be muted 13:02:51 For non-normative and normative ... (a) without the describing 13:03:21 normative. vote for a) 13:03:42 ack shawn 13:06:55 Shawn Proposed and it was approved that the Lexicon be mailed around for a 48 hour last time comment. 13:07:24 action: shawn & henk coordinate on getting final version in latest format and email list for "last call" 13:08:18 Judy: The Lexicon will hold off on extending the lexicon so that EO can pesue other priorities 13:09:30 jb: any closing comments on Lexicon 13:09:31 Shawn: Will send around the Lex to other interested working groups 13:09:37 harvey: whoopie 13:09:38 :) 13:09:39 Harvey: Woopy 13:09:49 mcmullin has joined #eo 13:10:28 Topic: Retrofitting 13:10:40 Hi shawn - finally back in the real world... 13:12:42 Judy: Introduced the Retrofitting Document and identifed basic isues 13:14:21 Shadi: We need to do scoping and identify the audience. Where does this fit in the EO documents. Higher leve approach: what to consider; Should we target developers? 13:15:39 Judy: Look at the requirements section, do we have the audience? 13:16:35 Jack: The audiences are correct, but the title doesn't match 13:16:58 Henk and Andrew: Agree 13:17:25 suggestion: Developing a Plan to Retrofit... 13:18:00 aa: title implies that we're going to be told how to do it, rather than things to think about when we need to do it 13:19:38 Shadi: If we go down the direction for "Developing a Plan for Retrofitting". Where would we fit it. 13:19:51 I agree...by repeating everyone will get the message. 13:20:20 Andrew: Repeating information may anoy a few users, but will ensure that it can be found. 13:20:56 Andrew: There is little overlapping. 13:21:59 Judy: the draft will change so we should be asking about what do we need that fills gaps in existing documents? 13:22:24 zakim, who's making noise? 13:22:37 shawn, listening for 11 seconds I heard sound from the following: Judy (90%), ??P4 (17%) 13:23:19 Judy: Is planning enough; do we need to say how to? That is a controvercial question. 13:24:17 Andrew: Address the complaint "where do we start", "are some check points more important", people need a guide through the path. 13:25:23 Jack: That is in line with concerns at Boeing. We have a lot of pages, but willingness is overwhelmed by the size of the task. People need to know what to do, details... 13:26:18 Genreal agreement with Andrew and Jack's comments. 13:27:29 Judy: Formalize "Now what do we do" to "Next Steps" 13:29:09 zakim, please unmute me 13:29:09 Justin should no longer be muted 13:29:47 Suggestion: the road ahead; towards an accessible web site; the way forward... 13:29:56 Carol: Has done this and the steps were similar but not so formal. 13:30:47 -??P7 13:31:15 minuting 13:31:25 \nick wayne 13:31:34 -Carol 13:32:11 wayne, can you drop off irc please? 13:32:19 -Alan 13:32:46 scribe: Andrew 13:33:57 FOR THE RECORD: Andrew changed nick to Wayne in order to maintain scribe notation in minute generator :) 13:34:42 scribe: Wayne 13:35:27 JB: "audience" discussion - primary/secondary 13:36:34 Barry: Q - not clear from change log, waht is the definitive diferfence between this doc and others? 13:37:39 JB: v.different from Implementation Planning - it was much broader, this could be much more focussed on a particular step 13:39:14 JB: 'policies' section could be dropeed as covevred in detail, but overall should be sharper for retrofitting 13:39:39 Barry: if it is going to get "down and dirty" then audience should be flipped 13:40:38 +Henk.a 13:40:46 Shadi: doc is somewhere inbetween Implementation Planning and "how to fix code" 13:41:12 Shadi: a collection of strategies and steps on how to tackle the task 13:42:38 Shadi: JT: managers make the decisions - what/how much effort/what do we want to acomplish 13:43:18 zakim, please unmute me 13:43:18 Helle_Bjarno should no longer be muted 13:43:23 AA: agrees with JT 13:43:56 Helle: agree that we need to approach the higher level initially 13:44:16 Shadi: how high a level? 13:44:50 Helle: important to target the funders and decision makers rather than the coders 13:45:54 Helle: Q - when would you read this? After an eveluation tells you there is a problem with your site? 13:46:28 q+ to suggest adding to requirements when we expect people to read this document (like Helle just said) 13:46:29 JB: certainly this is one scenario - how to orient yourself after an evaluation has been conducted, or complaints made 13:47:32 Pasquale: this should be for decision makers. We have an implementaio planning suite for when we start to develop a web site - this is for an existing site that needs fixing 13:48:13 Pasquale: can re just call it "accessibility updates" 13:48:33 Henk: what about "upgrading your web site for accessibility" 13:49:04 q+ to say yes with redesign! 13:49:27 zakim, please mute me 13:49:27 Helle_Bjarno should now be muted 13:49:50 JB: gets phone calls caknowledging they have accessibility problems, but wanting guidance on where to start 13:50:55 ack me 13:50:55 shawn, you wanted to suggest adding to requirements when we expect people to read this document (like Helle just said) and to say yes with redesign! 13:51:26 SLH: documents more discioverable with site redesign - definitely 13:51:45 zakim, please unmute me 13:51:45 Helle_Bjarno should no longer be muted 13:52:07 SLH: discussion is helpful - expand requirements to say when we expect people to use the document 13:53:23 Helle: what about adding in some FAQs - we all get these type of questions 13:54:11 JB: FAQ idea - can we explore? What are some of the questions? 13:55:18 Henk: they do not ask is what is the code solution - trust their developers to do this - want guidance on where to start & right procedure 13:55:50 Henk: not which part to start with, but more about procedure 13:56:26 Helle: more concrete - what is the most important thing to do - eg title VS alt attributes 13:58:23 XX: are there a few things that would have a big impact 13:58:37 s/XX/SAZ 13:59:59 Q? 14:00:00 AA: how to preioritise depends often on contwext as well as WCAG priority levels 14:00:25 Shadi: and also on what can be done site-wide with the CMS 14:01:00 Justin: get asked: how much will it affect the visual look of the page? 14:01:46 general agreement 14:02:46 Barry: Q - "how do we get MS Word to genrate accessibility HTML" - have to break the [bad] news gently 14:03:37 Barry: also get - "we don't have an PWD using the site" - so suggest a dedicated feedback chanel to get feedback on specific barriers 14:03:51 good point 14:03:52 AA: we also suggest this 14:04:37 JB: yes - capture this for suggested process 14:05:27 JB: tools - "selecting" has discussion on work-arounds, but without specific recomendations - should cross-ref this 14:06:06 JB: should also link to Bus Case as motivator for feedback channel 14:06:44 JB: look again at draft requirements (http://www.w3.org/WAI/EO/Drafts/retrofit/retrofitting-changelog.html) 14:06:52 Justin has left #eo 14:07:03 Justin has joined #eo 14:07:16 JB: any specific reactions to 'approach' section? 14:08:10 JB: could we use the questions we have just brainstaormed as practical approach, ratehr than the role, etc approach 14:08:46 AA: likes the practical appraoch sugegstion from Helle & JB 14:08:57 zakim, please mute me 14:08:57 Justin should now be muted 14:09:10 Pasqale: "practical" is the right approach 14:11:02 Shadi: helpful discussion to guide re-write 14:11:29 JB: audience clarity - needs more discussion? 14:12:03 JB: sure - managers are important, but often develoeprs get handed the task 14:12:34 SLH: large org VS small org (managers VS developers) 14:13:37 SLH: if doc is how to decide what to do, then bottom line is that job title doesn't matter, it is what role you have 14:17:23 AA: if you got caught out (by not building in from he start), then this is an approach to make some amends 14:18:37 JB: any wrap up thoughts on audience? 14:19:27 sounds good 14:20:08 Shadi: will bring revised descriptions back to EO 14:20:44 JB: anything that jumps out from Shadi's draft (http://www.w3.org/WAI/EO/Drafts/retrofit/)? 14:21:33 people seem hapy to wait until next time 14:22:12 JB: comments on overlap with other docs? 14:22:51 JB: should it be a side-step from "implementation plan" 14:23:18 Henk: it is a specific subset of the "implementation plan" 14:23:40 Pasquale: agrees with Henk - as do others 14:24:05 Helle: also fits with "Evaluation Suite"? 14:24:16 Henk: it is the next step/phase 14:26:43 JB: will IA for new site accommodate these relationships? 14:27:17 SLH: most probably - can draft for next meeting in site map 14:27:27 I have to quit regrets for next meeting June 3 14:27:35 -Helle_Bjarno 14:28:15 Topic: June meeting schedule 14:28:35 no meeting 27th May, but all through June 14:29:13 rrsagent, make logs world 14:29:14 Meeting closed 14:29:16 -Doyle_Saylor 14:29:17 -Shadi 14:29:20 -??P8 14:29:21 -Bingham 14:29:23 -Jack 14:29:24 -Sylvie_Duchateau 14:29:25 -Judy 14:29:26 -Henk.a 14:29:27 -Shawn 14:29:30 -Justin 14:29:32 -??P4 14:29:33 -Ron_Armstrong 14:29:35 -??P6 14:31:47 Shawn, can you pass the IRC log along to Wayne? 14:33:24 zakim, bye 14:33:24 leaving. As of this point the attendees were Doyle_Saylor, +1.714.649.aaaa, Sylvie_Duchateau, Judy, Bingham, Shawn, Henk, Ron_Armstrong, Carol, Jack, Shadi, Helle_Bjarno, 14:33:24 Zakim has left #eo 14:33:27 yes. will do 14:33:27 ... Loughborough, Justin, Alan 14:33:37 rrsagent, draft minutes 14:33:37 I have made the request to generate http://www.w3.org/2005/05/20-eo-minutes.html shawn 14:35:33 hi all, have a good week end 14:38:44 judy has left #eo 14:39:00 Justin has left #eo 14:39:47 shawn has left #eo 16:38:57 rrsagent, bye 16:38:57 I see 1 open action item: 16:38:57 ACTION: shawn & henk coordinate on getting final version in latest format and email list for "last call" [1] 16:38:57 recorded in http://www.w3.org/2005/05/20-eo-irc#T13-07-24