EOWG -- 09 Jan 2009

<scribe> Scribe: Doyle

<scribe> ScribeNick: doylesaylor

Shawn: Happy New Year

WCAG 2.0 reactions

Shawn: Any discussion on anything new about WCAG 2 coming or ideas for follow up for January?

Andrew: I was looking at Australia, in Vision Australia turned up 125 at a meeting and indicates a lot of interest in Australia.

Helle: I am working on the idea of workshop, with web developer who know the technology, we are thinking about doing something in Denmark.

Shawn: we are thinking about providing reusable materials, and looking to EO about that.

Wayne: Tom ? are looking at doing a speech about local guidelines in relation to WCAG 2 what to put into the local and selling web products how far away from WCAG 2 they are.

Shawn: do you have paper related to that?

Wayne: a while back yes.

Shawn: who is planning on going to CSUN this year?

Helle: I am going to Wellington in New Zealand. About standards and eLearning.

Shawn: several countries are looking at adopting to WCAG 2. Any other general comments?

Helle: we are waiting for feed back about the translation of WCAG 2. Or money.

Shawn: that is going really well authorized translations.

Helle: we have the general idea of who is going to who we would ask to become members of the group. I am working with the standards group and working with Shadi to make a translation.

Shawn: anything else?
... ATAG and UAG are going good. Realistically we will have a couple of months following up on WCAG and then yes there is a lot of interest to work with ATAG and UAAG and WAI ARIA.
... potentital WCAG day. Input? We still have a rough idea, we want more if we do in January. More ideas from EOWG to form something doable. WCAG 2 day.
... we had a rough idea basically regenerating buzz. People who heard about in December and spreading the word in December. A lot we didn't do. That is the introduction. Welcome any ideas on what might work. Promoting it.

Sharron: remember the global CSS reboot. Design the site. Remember?
... announce a showcase what you have done to your web site using WCAG 2.

Shawn: what would that look like?

Sharron: the CSF reboot was just an annoucement. I don't know if there was prize, but hundreds of sites participated from all over the world. Something in that model. A WCAG 2 reboot.

<shawn> http://www.cssreboot.com/about

Sharron: there was a deadline, no cash prize. They featured a lot of the sites that were redone. I was thinking about that one. I thought about that reboot. Could do globally and virtually and no real expense. Depends upon blogging. Might get people talking again.

William: a boiler plate email, to all the members, corporations. A version of the testimonial to the W3C member page.

Wayne: I like the idea of a reboot. We wouldn't want to be too big a part of the site. see if they start WCAG 1 or 508 would work nicely.

Shawn: I am looking at the reboot page. They set up a page where they link to these sites. With votes and comments for each. If we did something would we publish a list of sites? What would be the challenges? Accessible but missed something. Do with limiting our maintenance? Or time commitment.

Sharron: a volunteer group of peopl.e to monitor and maintain. Would have to submit during the candidate recommendation a good place to start. A commentary maybe voting. More monitored by the community than W3C.

Shawn: good point.

<Zakim> shawn, you wanted to ask how long you need to give people

Shawn: Another question what is your feeling to announce in January to redesign by X how long would X need to be?

William: hopefully realistically?

Shawn: realistically. We want them to succeed. Liam? Sites you work with, how long realistically take?

Liam: already meet WCAG 1 AA and AAA not very long.
... only thing in time, measuring the readability. That is more time consuming. That is a long track to follow on that. Look up literacy levels. To measure in some automated way.

Shawn: what about some organizations would be hesitant to make a big declaration to meet WCAG 2 being unsure to meet and don't want to be criticized?

Liam: trying to meet?

Shawn: we are working really hard a commitment to do a really good job.

Liam: a commitment to notice what you missed and put right if you can.

Wayne: the reboot restart, there was not any thing for months. Announce in January and follow up in four months. Send out a really intensive mailer. Evaluate then a lot of sites.

Sharron: go by the votes. Give the community the feedback instead of W3C.

Shawn: they only have 23 sites for the CSS reboot.
... if they only have 23 sites.??? Something like this we would need commitments from popular people to make this work.
... Good ideas any other thoughts on something like this?

Liam: we are proposing in the WCAG site?

Shawn: we need to be careful about doing this. My first reaction but not sure we want to maintain this.

Liam: I am thinking of use the power to the relevance toward this. WCAG reboot links to ...from the commercial point of view, if we want to be known for web accessible. Releasing a site according to standards. If we know we get recognition worth getting more. Otherwise another industry award. But promoting by W3C is more important.

Wayne: that would be true.

Shawn: we have talked about this type thing for years. Specifically related to WCAG 2 we spent a lot of time, like Sharron, but dozens who evaluated sites for WCAG 2 candidate recommendation, hours and hours, most of the sites had things needing fixing. We are small staff. Too many things to do like ATAG promotion.
... I am thinking it would be nice to do. A lis of sites or gallery of sites to showcase. But don't have time to evalujate. If we could manage so it is clear to not approve the sites. Instead this is a community working together. When we try we haven't succeeded. I want to relook at again.

Liam: a tool for the community to go through the site and meet and fail. The community can say it is ok. Dated conforms. Seems to be all right. Rather nice to I am really fed up with this site that is not really accessible. A place where the community can do that, but supported by the W3C. Not trivial thing to do.

Shawn: we would need time too.

Sharron: when you mention the candidate recommendation and we could comment on there was a evaluation tool to record and compare the results. People could demonnstrate how they self reporting. This common reporting tool. The guidelines in the same sort of rubric. Pretty helpful. Organzing your feedback.

Shawn: we have no ownership, we are happy to share what we do. Not robust enough for broad use though. Known issues, with small batch. We had planned to do. Something we thought of making more broadly useful. Put something out there and let someone polish up.
... no shortage of ideas, shortage of time.

Wayne: we have a pretty good protocal in terms of the Illinois test site, in half hour you can do 95% completed. They sent something out to the group you won't have someone say you are really gros.

Shawn: thanks for the thinking on that. I will see if anything gels. Come back next week if we have more ideas. What other ideas about WCAG 2 day or other promotion in January day. Like 'blue beany' or 'turn off your style sheet' days.

Liam: talk like a pirate day?

Shawn: if did something tied to a day in January what would it be, how would work?

Liam: a 24 hour code-a-thon. Rewrite their web sites in the day. With input from the W3C staff. Might be fun.

Shawn: we would provide support call in number or chat. Encourage people locally and set up a room and network?

Liam: name a time and place. The part of the problem getting the word quickly. When in January?

Shawn: we are open. Early or last week. In Vienna they have a monthly meeting of some group. They are having a WCAG2 party on 15 Jan

Liam: we had something in Switzerland.

Shawn: a code-a-thon is one idea.

Wayne: how does that work?

Liam: dividing people in a chat room. In that period, to work on that period, 12 hour or 24 do you get there or how close after you start off.

Shawn: with x amount of work I would get so this far. I'd like to have more data on.

Liam: WCAG staff and hangars on a possible thing to do.

Shawn: that is good thing, from various discussions the most reasonable.

Liam: if you can record what is going. A moderated forum place. To questions. A great big record. Throws up ambiguities, and can be addressed then.

Shawn: we could try to do. Monthly for four hours.
... threaded is interesting. In terms of practicalities of blog or email.

Liam: Google email works pretty. blog can be tricky. Quite hard to make work.
... email is ok. I would get a lot of samples of CSS groups.

Shawn: chat rooms would be great for people who use. But hard to follow. Three conversations is there a way to differenciate well?

Liam: in an ecommerce site, what sort of numbers are we expecting?

Shawn: if we could have hundreds.

Liam: not too bad at all.
... done on a regular basis you might build up those numbers. Not though in this January.

Wayne: we could get fifteen from our system. 15 people contributing from our system. Working on their site. A number of people who can answer questions. We could talk up next week.

Shawn: 12 through 15th?

Wayne: yes a lot of motivated people also.

Shawn: any other ideas?

Liam: run as a google group.

Wayne: yes.

Liam: are we keeping track of various bits of media out there usefully straight to keep track of.

Shawn: we have an internal list. Not a public list. What are your thoughts say more about that?

Liam: if you have media pieces more than puff pieces like technical piece, frequently asked, we should link to those. Make sure they get the publibicity.

<LiamMcGee> [clarification] I was thinking in terms of a Google Groups Developers Forum e.g. http://groups.google.com/group/google-checkout-developers-forum

Shawn: ok, other ideas?
... anything else?

Liam: any scope in allowing people automated alerts for the documentation?

Shawn: understanding the techniques? We will do a reasonable we said. We would send to the RSS feed. Given fairly low traffic list. We started to do with WCAG 2 but didn't really make sense.

Liam: an email telling me about what is updated.

Shawn: we thought about doing announcement, but would duplicate RSS and we think now it would be updated once a year. When we update, do the usually announcement channels and W3C newsletters, etc. and a list of being updated.
... have a way to add a comment as you look at?

Liam: I am trying to think user centered. What is missing here and they need it.

Shawn: actually Liam would you submit as a suggestion?

Liam: yes in what way?

Shawn: WCAG 2 public comments.
... make comments right there.

Liam: yes.

Shawn: How easy it is to find in the site. So...

<andrew> public-comments-wcag20@w3.org

Shawn: there is the online comment form which makes you comment on a specific document. If you put in Liam I will watch for and flag it. Good idea.
... anything else?
... we will work on over the next week. Any dates would be good. Towards the end of January and please send to the list or to me. Thank you for all the thoughts. Check on the general comments for the discussion?
... all right we done.

- DRAFT -

EOWG

09 Jan 2009

Attendees

Contents

WCAG 2.0 reactions

Summary of Action Items

Scribe.perl diagnostic output