See also: IRC log
<shawn> justin - are you up for scribing?
<scribe> Scribe: Justin
<scribe> ScribeNick: Justin
<shawn> REVISED agenda: http://lists.w3.org/Archives/Public/w3c-wai-eo/2005AprJun/0142.html
Helle: We have done the first part of translations of the australian accessibility bar.
Judy: What are you translating?
Helle: Microsoft is helping us out with this.
Alan: I am translating this also.
Judy: A lot of people are looking for help getting assistive technology translated.
<judy_away> s/what are you translating?/how is microsoft covering this?
<Andrew> The toolbar (origial version) is available at http://www.nils.org.au/ais/web/resources/toolbar/index.html
Judy: We have done some of these
before. We have been rotating the location and the format. This
one is less exchange and more best practices.
... It will be focused on evaluation and retrofitting.
... This will be more of a beginning level.
... We have gotten some very valuable feedback on the program before. We'd like any feedback that EOWG might have on the program.
BPE Program: http://www.w3.org/WAI/EO/2005/07/training.html
Harvey: Is this information going to Brazil also?
Judy: The people who are organizing this have lots of contacts over in Brazil.
Alan: This seems to be largely about evaluation but it's not clear in the title.
Judy: We can try and make that more clear.
Sylvie: In the announcement it talks a lot about evaluation but not as much about retrofitting. The program talks a lot about retrofitting.
Helle: Who is doing it?
Judy: Shadi and Shawn.
Helle: Maybe we should do this in the nordic countries.
Judy: We need to do one in the fall. We are looking at one location but it's not set yet.
Helle: A lot is happening.
Judy: We are looking the announcements in a box on the right column.
Shawn: Check out the prototype
with the announcements & highlights.
... We had talked about where to put the announcements and be able to list upcoming meetings and some of the documents in progress.
... We didn't want the highlights to be below the scroll.
... A lot of people really liked the meetings and documents in progress on the home page.
... PRO - this gets the highlights way up on the top. It gets the announcements above the scroll.
... What do people think about the new placement of things
Doyle: I like it. I tend to this of the right side of the page as less important or less timely.
Judy: What is happening when the page is linearized?
Shawn: Now it is before the H1 and we will fix it so it is after the H1.
Andrew: Someone with a screen reader or an older browser it will be a different order then how I see it now.
Shawn: Site Nav, the H1, What WAI
Does, Announcements and then Highlights.
... The way we designed it is, that What WAI Does would be easy to see and then easy to mask out once you were familiar with the site.
... Doyle's comment is true. Whenever we have an annoucement of note those will be a highlight.
<Zakim> shawn, you wanted to agree with doyle and to clarify that some announcements will be in highlights
Barry: I have a small screen, with firefox, and when i turn the text up one level the annoucnements dropped below the scroll. But because key announcements will be highlights, I think that should be ok.
Shawn: I changed Working Group
meetings to Events, Meeting, and Presentations.
... I want to confirm that everyone is comfortable with the new parameters.
Shawn: (Going over
... Worded in a way to be a lead-in to get people to follow the link and read the document.
... We wanted to make sure that targeted the different audiences.
Shawn: The prototype has some
... We need to know what topics we want to cover and how this will play out.
Judy; What are people's thoughts when we look at this abstractly? This is to get people to come back to the home page.
Barry: I like the highlights that
are there. I like the lead-in. It works as bait for me.
... The RSS feeds are the first thing that I look for.
Barry you and I think the same way. :)
<shawn> ACTION: shawn & WSTF look at putting RSS feed link at top [recorded in http://www.w3.org/2005/06/10-eo-minutes.html#action01]
Judy: I really like the zing of the title's of the leadins.
Andrew: I think they are well written and i like the titles.
Barry: I think the first one is a little hard to read.
Judy: Maybe it didn't make the zing transformation.
Judy; What do people think of the last one?
Judy: The blog one.
Doyle: The brackets caught my attention.
Shawn: That was more of a note to
... What about using graphical element for this highlight?
How about Blogging Tool
Shawn: I think for the Captcha highlight will need an image.
Doyle: The graphical element can make a huge difference. (eg Slashdot)
Shawn: Comments on size.
Barry: Just right.
Doyle: The one at the bottom that spreads off the right. The fact that it spreads out to the right that makes it possible to see...the top one seems too long because it can't go across into the second third column.
Helle: How would I look at this if I were a foreign language newbie? This might be a little high level for me.
Judy: It seems like the WSTF wanted to have a mix of knowledge levels.
Shawn: Maybe add a parameter that the top item be more newbie friendly.
<shawn> ACTION: shawn/justin - add to highlights parameter that usually first highlight should be newbie-friendly [recorded in http://www.w3.org/2005/06/10-eo-minutes.html#action02]
Sylvie: The text of the highlight is not easy to understnad.
Andrew: I think they are very
... I prefer them shorter rather than longer.
Judy: The short ones I am more likely to read.
<shawn> ACTION: shawn/justin - add to highlights parameter that usually first highlight would [recorded in http://www.w3.org/2005/06/10-eo-minutes.html#action03]
Barry: When I come to this page first...the first one is so long that i don't know that there is a highlight below.
Justin: Putting one sentence to a
paragraph to make it shorter to skim.
... Making it more of a personal voice instead of formal corporate.
Helle: I like the breaking it up.
Barry: Maybe even putting a by line to make it more like a group blog.
Helle: Where do these highlights come from? Are they from WAI working groups are they from certain people?
Judy: The staff would be writing
... It would be about WAI work.
... We might do some work with the Mobile Web Initiative.
Shawn: We might have some past highlights...where it could be explained.
Helle: The fellowship of the components should identify who is working on the components document.
Judy: Are there highlights people wish we were doing?
Judy: Is the text on the W3C home page easier to read?
Helle: I think the language is ok...you know they are having this work shop.
Shawn: with the RSS feeds you
have the latest at the top.
... with the W3C home page you can get the really important stuff to stay at the top.
... Maybe have a newbie box at the top?
Andrew: Would it change regularly?
Shawn: Just stay there.
Andrew: Im luke warm.
Helle: Would it be confusing because you have a highlight thats not really a highlight.
Judy: I think it did work.
... It was like an invisible technique.
Justin: With RSS, i wouldn't even go to the page if it didn't have a new entry because I wouldn't have gotten a notification in my reader.
Andrew: Do we want to have a similar style or format as the w3c home page?
Shawn: I made something simiar to internationalzation.
Shawn: Anyone interested in
... that was Judy.
Judy: This would help to off load
some of the work from EO
... The WSTF could handle some of the feedback as well.
... Shawn can contact some people offline to who might balance out the view points.
Shawn: Justin added a more customized prototype. I mocked up a more interim solution.
Harvey: Is there member-confidential stuff that would be included?
Shawn: This would be for public things only right now.
Judy: We could maybe do a parallel in member space some time.
<scribe> ACTION: Justin, look into google auto translation for search. [recorded in http://www.w3.org/2005/06/10-eo-minutes.html#action04]
Sylvie: I am getting the results in french.
Shawn: The one we sent on tuesday
is how might be able to customize it for the future.
... Probably won't have customized results right away.
Shawn: the first column just has
the acronym and the second column adds the word web
... Someone pointed out this is uses lowercase.
Harvey: I like lower case it doesn't shout.
Doyle: When its full written out,
i like the first letter fully written out
... in Web Accessibility Initative.
Andrew: Lower case comes across more friendly
Judy: Does wai in lower case make it look less authoritative?
Doyle: I don't think it would matter.
Judy: I think the letter options in lower case look more attractive.
Doyle: the word is initiative is right justified.
Shadi: I don't remember seeing a version with uppercase. It would be nice to have a comparison
Judy: Would be nice.
Shawn: A is not as refined.
... B is more refined from last week.
<Helle> zakim unmute helle
Justin: I like B. Its more fun and colorful
Shadi: I agree.
Andrew: I think the font is harder to read.
Helle: I think its harder to read.
Judy: What if the font were clearer?
Helle: I think it would help.
Judy: Any new volunteers?
Judy: June 17th
... hopefully be back on some of our documents.
This is scribe.perl Revision: 1.126 of Date: 2005/05/16 16:49:48 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) FAILED: s/what are you translating?/how is microsoft covering this?/ Found Scribe: Justin Inferring ScribeNick: Justin Found ScribeNick: Justin Default Present: Doyle_Saylor, Helle_Bjarno, Shawn, Justin, Judy, Shadi, Bingham, Andrew, Sylvie_Duchateau, Alan, Mullin, [IPcaller], Barry Present: Doyle_Saylor Helle_Bjarno Shawn Justin Judy Shadi Bingham Andrew Sylvie_Duchateau Alan Mullin [IPcaller] Barry Regrets: Henk Wayne Ron Agenda: http://lists.w3.org/Archives/Public/w3c-wai-eo/2005AprJun/0142.html Got date from IRC log name: 10 Jun 2005 Guessing minutes URL: http://www.w3.org/2005/06/10-eo-minutes.html People with action items: - add justin shawn WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]