|
EOWG Home
Page
WL: At the Interface Device Independent Authoring Workshop I gave my standard "Programmers are Cheaper than Lawyers" talk.
HS: We have set up appointments with Fortis bank which is planning to develop an E-bank program that they want to have accessible to visually impaired customers. Their plan is to make the March rollout accessible, not the first version.
DC: The W3C guidelines are being referenced in a lot of court settlements.
JB: Many settlements are confidential, but sometimes one part of the settlement that is made public is that the W3C guidelines are referenced.
DC: I know . . I think we need to refer to this in our training of trainers and consultants.
JB: We don't really cover this in the training material and perhaps we should.
CV: Is W3C responsible for translating the Quick Tips?
JB: The reprint we need to discuss today is specific to the English version. We are aware of some of the changes we need to make in some of the other language cards.
DD: I didn't think we were running low yet.
HS: We ran out and I think Eric ordered some more.
CV: Is DD responsible for the German version?
DD: Yes.
JB: Please send all requests to WAI-Quicktips because we track those request. In my internal query about the state of the Quick Tip cards, I got responses from Chuck and Daniel. One request was to drop the period at the end of an entry containing an URL. Some people type the period as part of the URL.
DD: Is the URL in a differnt font? Bold?
JB: It just looks wider. The other cthing that came up is that the 'map' and 'noframes' are in upper case.
DD: To be consistent with xml, we can just change it to lower case. It seems to be a no brainer.
JB: In the past, we've thought we were making simple changes, and thought we'd found everything, to find after we have printed them, that we missed something. We also want to add 'EN' and two spaces before the date to indicate the language, English.
DD: I think it's better to have the URI at the end in bold. That's the way it is in all the European versions.
HS: Is it possible to know how many Dutch cards are left so we can be sure to discuss the needed changes before they are reprinted?
JB: It's better to discuss that earlier than later so let's not wait.
JB: At the face to face, almost every document we touched we managed to flip around. We decided to do one page of curricula and one page of tips. The nav bar should be on the right hand side for everyone who has CSS support. We have a change log that was sent out last night, which contains everything from the 10/5 session, as well as the content from the 9/29 phone call. There are a few items in the change log that haven't been done on the page yet.
KA: I am looking at the page in Netscape 6 and it's looking pretty good.
JB: The content on the curricula page needs to be looked at. The first change request about the 20 minute presentation needs to be reviewed. Does linking to the modules page work, or is it confusing?
KA: The fragment anchors don't seem to be working in Netscape 6. Well, some of them work, but not others.
JH: I just refreshed and it's working now.
(Minutes tempararily suspended while this was discussed.)
DC: I am unclear how the learning objectives are going to be different for number 2 from number 1.
JB: There will be some redundancies, and it's a question of how much we want to live with.
DC: It seems like we need an adjective like highlighted or primary added in there..
JB: The content containing "heterogeneous . . ." should be part of the H2 instead of H3? Do others have comments on this suggestion?
JH: I think it's fine as it is.
JB: I will try it in a draft but not commit to making the change. Are people okay with that?
WL: The 20 minute presentation only has 16 minutes accounted for, and no myth debunking, which should be a part of any 20 minute presentation.
KA: I agree, and it's part of the 10 minute presentation.
JH: could you add the link to the business case document?
JB: The third example, the 10 minute overview, is fairly impossible to accomplish in ten minutes. Would people please comment online on this? Chuck, does this seem practical?
CL: Yes, and I agree that it's important to reherse ahead of time.
JH: Can we change the order so the 10 minute presentation is in a place that makes more sense?
JB: Let's try changing the order with a mini-talk up front.
DC: I think even having a 10 minute presentation on the page could do a disservice to us because it requires a trainer who knows the material inside and out.
JB: Perhaps just adding a stronger warning would cover it? I'd like us to keep focused on some of the content. Perhaps we should focus on the 3-hour workshop on designing accessible sites.
KA: Is it hands on?
JB: Let's do that since none of the others have attempted that yet. How many people would be present?
DC: 20 online participants.
JB: How do we start the workshop? What skill levels do they have?
KA: They know html--web designers. Let's have them bring up an inaccessible site and let them hear it in Jaws. Ask them to navigate that site just using their keyboards.
WL: Should we look at the full day training and decide what should be left out for the three hour one?
JH: Ask them to fix it.
JB: Before introducing the guidelines?
KA: I would show them the guidelines, and then take them to a page that does not conform, and then one that does. It would be important to use whatever tools they are used to when you ask them to do the remediation.
JB: How about if we have them design an accessible web site from scratch with some pre-prepared content that you provide. We only have a few minutes left so we've got to wrap up. We need to move this out so people can start to use it. Please comment online, and I'd like to be able to ping you individually to keep working on this. We are scheduled to meet again next Friday, and for several more following Fridays into the future.
Last updated 9 Nov 2000 by Judy Brewer jbrewer@w3.org
Copyright © 2000 W3C ® ( MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.