W3C

- DRAFT -

EOWG

20 Aug 2010

See also: IRC log

Attendees

Present
Shawn, Andrew, Doyle, Yeliz, Liam
Regrets
Shadi, Sylvie, Ian, Emmanuelle, Sharron, Wayne, Jennifer
Chair
Shawn
Scribe
Doyle

Contents


<scribe> Scribe: Doyle

<scribe> ScribeNick: doylesaylor

Wow Summer time flu is getting serious

Shawn: Topics: Expanding-collapsing functionality beta- Developing Websites example
... Any comments?

Doyle: It looks fine to me. I like it's visual brevity.

Shawn: How should they appear visually, button not a link? comments

Liam: I'm not sure it matters.

Shawn: for screen readers it's a problem

Liam: Yes when I use a screen reader it is confusing.

andrew: a button gives you a clue about you get an action rather than following a link.

Liam: I think it should be a jump. It's hard to figure out what it is because you go to the button before the explanation. It could be CS how to set up. At the moment in the face element that does collapse or expand is set before the heading. The heading should do that itself.
... button is good and toggle is good.

Shawn: even for the heading level?

Liam: yes I don't think for the heading level it is difficult for the screen reader.

Shawn: we'll get the first pass from Jennifer and Sylvie - and from more later.

Liam: from the logical point of view is it is hard to figure out what to do.

Andrew: They all start with expand. It could be logically after and visually before. The best of both worlds.

Liam: Yes, and the other possibility, is it useful to have expand collapse. Maybe to use CSS to hide the screen. From the screen reader point of view they don't need to hide.

Andrew: the CSS is to hide?

Liam: Yes, to put to the side or what have you?

<Andrew> possibly use CSS to move off/on screen with +/- rather than doing a disply:none etc - would possibly work better for screen reader users who typically navigate by heading

<LiamM> suggest exp/collapse fnality not needed for screenreader user naving by heding so instead use display none/block use position rel/abs and shunt offscreen to left for collapse.

Shawn: The third point is visual indication what is clickable. Currently if you cover over the plus minus icon. the text is also clickable, but the mouse pointer is not changing when hovering. I didn't know any reason to do that, to not have the mouse pointer change on hover, or focus of the heading text. Any reason not to do that?

Andrew: Why they didn't go there, on the same line they would have other links that would be include, with a bigger clickable link from similar reports.

Shawn: The main reporting elements would get the active points, and not for the ...

andrew: My response is that the mouse hover is only for those points and doesn't affect the main points.

Shawn: On some browsers you can click on the plus minus, but you can also click the text.

Andrew: You only know that by trial and error at the moment.

<yeliz> I didn't knw that either

Liam: what is the logic about having the heading above the expand collapse. Not with parenthesis?
... you don't know to put the final bit of text visually for sighted users?

Andrew: Sighted users need some clue but it will expand and collapse.

Liam: if we want the heading to usable it should change at that point.

Shawn: Just wanted to check. Any other comments?

Topics: Slide sets

<shawn> subtopic: Business Case http://www.w3.org/WAI/presentations/bcase/bcase-presentation-format.ppt

<yeliz> I am also downloading it

Shawn: the first bullet is for CSS version. The second bullet is business case slide set. This is an early draft.

<yeliz> I opened it OK

<yeliz> Mine is working OK with Office in Mac

<yeliz> I use Microsoft office 2004 in Mac

Shawn: First reactions?

<yeliz> me too

<yeliz> I like it

Liam: I like the one I am seeing. First reaction vaguely negative, the first quote, the legal and general quote, double the number?

Shawn: Ok.
... what do you like or don't like?

Andrew: in this business case well known people you don't know would have disabilities.

Shawn: I would like to see more ethnic and geographic diversity. And the other thing to put to presenter is what your audience would know better put that instead. I didn't know the Fonz had dyslexia. he has written childrens books about dyslexia.

Doyle: Chuck Close the painter with Dyslexia, and face blindness.

Liam: essentially nothing costs, the presentation graph, it's a time cost and training cost has to be budgeted for. With large companies it's cheap but not neglgible. The graphic at the end is not huge but presents something they can knock down.

Shawn: Is it with the graph, I was trying to get across yes there will be an initital investment, the investment will take time but go down and return goes up.

Liam: for a business audience they'll think well yes. That is how investments work. They know that well. What you want to know which investments get priority? The whole they could spend money on so give them real numbers or don't present anything. They can get quite grumpy at. Too simple.

<yeliz> Shawn, you can also use "Andrea Bocelli"'s picture: http://en.wikipedia.org/wiki/Andrea_Bocelli

Liam: we are trying to get them to learn ABCs.

Doyle: something they know.

Shawn: how would they know what they get from accessibility?

Andrew: yes from everything we have said already.

Liam: It would be much more powerful to have numbers here, over time you will get much more than you spend is not helpful there.

Shawn: If people knew that they would do it?

Andrew: They would be trying to balance what to spend on like a spring line or a local representation.

Liam: Yes exactly. Structuring even you ditch that, captioning for example, but the take home is real money. You can do this much investment over this time span. For competing investments.

Shawn: Tesco?

Liam: happened too long ago.

Andrew: yes.

<yeliz> I agree it might be considered as an outdated use case

Shawn: The date? Ok. Costs essentially nothing, the things in that list. Does that even a lot of tools that don't do those things? Which?

Liam: home grown CMSs where they don't consider have alternatives. Usually people haven't managed what it needs to do. They may not be certainly cost free. Technically easy, trivial in an engineering sense, but the implementation is not trivial. Someone would think this is not true.

Shawn: can be essentially free? In some environment?

Liam: less than you think. It's tough, we spend a lot of time to get the web site sorted out, money to be spent and time to do the work.

Shawn: one point with the transcript for audio, that will costs money a little more for transcript.

Liam; it is an on going costs, not a capital investment.

Shawn: that was the other thing in the graph, there will be inititial investment, in any organization there is a minimum of training.

Liam: would it cost to do extra for the web site in a review.

Andrew: you can get the color and contrast ok with just a redesign, but the if the code is bad, you might need a complete new CMS.

Liam: for double A compliant. For a client that was for large number of users with JFWs support but they didn't implement right and it didn't work. The procurement system you buy is not is it capable of doing an accessible site. It can be made accessible but the bulk of sites are not, there is not a lot of support in the documentation which they need to be aware of.

Shawn: Are there other things you need to do?

Liam: make Double A compliance contractual. Not your problem after that, if they deliver which is not up to scratch. Then you can get what you want.

<yeliz> educate their developers

<yeliz> :)

Shawn: to get a good web site, what about maximizing return?

Liam: good web sites should maximize the return. A good web site gets a wider range of users.

Andrew: make sure your staff or change of staff get trained to put the material in correctly.

Liam: I'm inclined to down play that a bit. That is a on-going costs. Making it in the contract.

Shawn: what's missing the presentation of the main points.

Liam: another thing is where it fits, your usability guy or girl, your graphic guy or girl, all should be in a group and work together. To try to present to a bunch of businessmen, they ask if it is hard.

Shawn: other reactions to that? We have convinced them what are the key points thinking going forward.

Andrew: don't leave it to the end. It costs more to add at the end.

Liam: how do I get to X well not from the end.

Shawn: what else?

Liam: It is not a one off. Get the site accessible, now look at it again in 3 months. Nothing is finished. Especially dividing business clients who do 3 month cycles and 3 years cycle. The standards for what to do on schedule.

Shawn: What else?

Liam: figures on conversion rate, and visitor rate? Every day?

Shawn: do we have any?

Liam: did we get from legal and general? That was the most open. They would using out of publicity.

<shawn> http://www.w3.org/WAI/bcase/legal-and-general-case-study

Shawn: Legal and general. What specifically?

<Andrew> Within one month, Barcham Online was well ahead of its best sales expectations and ahead of schedule to fully return Barcham's capital investment within just six months. from http://www.nomensa.com/client-portfolio/case-studies/barcham-online

Liam: ROI is good. Doubles in three in month is a good demonstration of returns.
... we take the quotes right?

Shawn: yes. With paraphrase.

Liam: yes. I don't know giving them words they use is good. I can only speak for the UK market conversion rate is a biggie.

Doyle: conversion rate?

Liam: what percentage that hit your web site buying a widget or getting a newsletter, what percentage converts to customer.

Shawn: Ok.
... we should look at point to Barcham Online. One case study?

Andrew: no there are more, but that is just one.

Shawn: a fun way to start.

Liam: Make them work out their own financial benefits in three months. If you don't know the answer to that why are you in the room. If you can convert to 50% what does that mean to you/

Shawn: That is one reason I didn't like moving the Legal and General to the end because I wanted to a grabber at the beginning. That's a grabber you give us.

<yeliz> Daily mirror is a good example, http://www.nomensa.com/client-portfolio/case-studies/the-daily-mirror

<yeliz> Nomensa's recommendations have helped www.mirror.co.uk achieve dramatic results, experiencing a year-on-year uplift of 93% in unique users . www.mirror.co.uk has seen a significant return on its investment.

<yeliz> Good case studies

<yeliz> Nice examples

Andrew: maybe we could roll several of these together to make a case study.

Liam: you want to do these for individual web sites, not roll them up.

Shawn: we need to figure out what we want to do with that.

Andrew: The numbers come from somewhere. I know some people there at nomensa. I'll contact them.

Shawn: ok. Anything else. On this? Add a different way to start, doesn't come across well?
... Andrew there have been some changes, I have done some and made notes for others to do.

Andrew: yes.

Shawn: anything else? Yeliz?

<yeliz> no

<yeliz> I think all the suggestions were good

Shawn: look at the draft of the WCAG 2 now?

<yeliz> Shawn, I have to leave early today:(

Liam: a quick quote of the market page. why is the web site successful about bringing in the numbers to present in that kind of format. Not good to make think but better to show it really happened, and some of the reasons why that happened. Here is a slide backing that up. In the business case presentation we start with the idea, you can double visitiors, you can double conversions. the next question is why making these improvements and the answer is
... A line of reasoning.

shawn: the weaving together the approach to the information?

Liam: yes

Shawn: Anything else?
... business case is done. Using WCAG 2 do the same thing with that now?

<yeliz> Shawn, I have to leave early today

Liam: let's do now.

<yeliz> :)

<shawn> Using WCAG 2

<shawn> http://www.w3.org/WAI/presentations/WCAG2_using/UsingWCAG2-presentation-format.ppt

Shawn: let's go to WCAG 2 page.

Liam: is there a reason you picked that? It's a scary one to present to people. Not common on websites.

Shawn: I grabbed something to show the guidelines are general. I'll find something better.
... I won't list all the success criteria under the guideline.

Liam: you are just looking for a technical error.

Andrew: 4.1 about contrast is one I use. The developers and designers doing the color selection.

Shawn: maybe you take another step further and in the documention there are tools you can use, to go next to the other resources.

<Andrew> 2.1.1 All functionality of the content is operable through a keyboard interface ...

Liam: 2.1.1 actually doesn't work that well.
... 3.1.1 works though. It's easy.

Shawn: programmatically determined scares people.

<yeliz> :)

<LiamM> 3.3.1

Liam: I can see why we don't want people to read the guidelines. 3.3.1 error on the form issue. That's good.

Andrew: It's good, the example is short, and the success criteria is good and short.

<Andrew> 3.3.1 If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.

<Andrew> Guideline 3.3 Help users avoid and correct mistakes.

shawn: what else? Is slide 17 too complex?

Liam: yes.

Yeliz: yes, I was looking at that slide. Useful at the beginning to show how the different documents are related. A way to move in these documents. It is complicated.

Shawn: 17 is trying to show what you get from trying to meet say quick reference here is what information is there.

Andrew: does it help by showing the other documents?

Liam: the notes are perfect but the image is scary.

Shawn: ok. the next one be enough to show, but it is not quite.

<yeliz> :)

Liam: show the standards is a big scary document and the how to meet is the friendly cop.

Shawn: what else?

<yeliz> Ohh I have to go now, Shawn I can clean up the minutes

Liam: slide 18 is great. the only question why is the ellipses around three of them?

Andrew: we want the ellipses to hight light the success criteria. The success is highlighted here where it isn't elsewhere.
... adding the words success criteria, and the circling include the SC titles or numbers, and actually circle advisory techniques all apply to this 2.4.2?

Shawn: maybe

Andrew: I've used a similar screen grab myself.

Shawn: Maybe use this specific example later instead of slides 21 and 22 to show how to make understanding of the techniques, to reuse and process less information. I'll ask Yeliz to email her comment.
... other things on this one on using WCAG 2. How does this fit in with the training resource suite Andrew?

Andrew: I think it would fit in very well.
... the closing slide 24 WCAG overview, whereas the reference as use as a quick reference. The final message is use this. On the same slide.

Shawn: good.
... anything else?
... I'll take another pass at it. Going gone. I will check with Yeliz about her ATAG comment. The last two things

Topics: Reminder of review survey: Training Resource Suite for review by 31 August

Shawn: do by August 31 would be good also. Andrew has the developing websites for older people ready as well. Any questions?

Topics: Ready for review: Developing Websites for Older People - please send comments to the list

Shawn: anything else. Yeliz will do notes. Have a lovely weekend.

Doyle wish Sharron well for me.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2010/08/20 14:04:10 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/go somewhere/get an action rather than following a link/
Succeeded: s/first pass from Jennifer and Sylvie./first pass from Jennifer and Sylvie - and from more later./
Succeeded: s/you can get the color and contrast ok, but the code is bad, so you save over the long perspective/you can get the color and contrast ok with just a redesign, but the if the code is bad, you might need a complete new CMS/
Succeeded: s/3.1.1/3.3.1/
Succeeded: s/3.4.2/2.4.2/
Succeeded: s/include and page titles/include the SC titles or numbers/
Found Scribe: Doyle
Found ScribeNick: doylesaylor

WARNING: No "Topic:" lines found.

Default Present: Shawn, doyle, Andrew, Liam_McGee, yeliz

WARNING: Replacing previous Present list. (Old list: Doyle, Shawn, Andrew, Liam, Yeliz)
Use 'Present+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Present+ Shawn, Andrew, Doyle, Yeliz

Present: Shawn Andrew Doyle Yeliz Liam
Regrets: Shadi Sylvie Ian Emmanuelle Sharron Wayne Jennifer
Got date from IRC log name: 20 Aug 2010
Guessing minutes URL: http://www.w3.org/2010/08/20-eo-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]