See also: IRC log
<scribe> Scribe: Doyle
<scribe> ScribeNick: doylesaylor
I am mute now.
Shawn: Bsuiness Case have two sections discussed in the WAI task force and bring back to EO for discussion before we wrap up and give approval.
I have to call back in.
<Sharron> scribe: Sharron
<doylesaylor> let me call back
Shawn: Changes are shown tracked
here, both the deleted and added from the original
William: Five pages? why are they
... are they separate documents? sections?
Shawn: It is one document presented in 5 webpages
Andrew: Broken out by topics.
William: Maybe doesn't matter.
Shawn: How about first of a series of five web pages?
Shawn: Let's look especially at the first three paragraphs.
William: why becoming esential rather than has become.
Andrew: Not as widely used in every country.
Shawn: Parts of the world where there is no internet access?
William: Even there it is deemed essential, hence the term digital divide. They are working hard to get it.
Shawn: True, but still is it essential if they don't have it?
William: It is recognized as essential and so they are working hard to get it.
Doyle: "Digital divide" refers to people who live in aculture that is online but lack access. If a culture does not use it, that's a different scenario.
Andrew: Most are moving in that direction, but have not attained.
Shawn: We have strengthened the
language in this version.
... the web is increasingly an essential resource
<scribe> ACTION: Andrew to consider ...the web is increasingly an essential resource [recorded in http://www.w3.org/2009/05/01-eo-minutes.html#action01]
Shawn: What else in the introduction? Need feedback especially on balance for intro to a business case?
Liam: Thinking about the sense of a document given by trigger words. Would like to see more words like ROI, sense that this doc will really give me what I need.
Shawn: Can add the acronym to the words already in the doc.
<scribe> ACTION: Andrew to add ROI [recorded in http://www.w3.org/2009/05/01-eo-minutes.html#action02]
Liam: Looking for ROI that is
more than what you put in, not simply neutral.
... however ROI can be significant.
... in third paragraph.
... don't only want to see costs offset, want to see a gain.
William: Rather than offset by...need more
Liam: When we are selling SEO, consultancy always note the increase in visitors
Doyle: How about exceeds the initial cost.
<shawn> "There are initial costs for organizations implementing Web accessibility; however, there can be a significant return on investment."
Liam: Yes that is implicit in notion of ROI
Doyle: Phrase initial costs might be the problem.
Shawn: "There are initial costs...but can be substantial ROI"
Liam: If you start with poorly marked up, poorly desinged site and implement WCAG 2, will see significant boost.
<shawn> ACTION: Andrew, bcase, Overview, Intro: "While there are initial costs for organizations implementing Web accessibility, there can be a substantial return on investment." [recorded in http://www.w3.org/2009/05/01-eo-minutes.html#action03]
Shawn: Overall, does this address
the business case?
... William you mentioned "with and without dicabilities" let's look at paragraph 2. Should we say "older users and people without disabilities
Liam: While it is implicit to us, it may not be to those not as familiar.
William: How about first paragraph?
Shawn: Treid to keep paragraph 1
... don't want to dilute the message.
Liam: It's difficult to get people thinking about conceptual models of disability. In intro more of a sense of what information will follow.
Shawn: it does kind of feel like mobile should be in there...
Andrew: It is included in second paragraph, could be emphasized.
<shawn> While accessibility focuses on people with disabilities, accessibility also benefits older users, mobile users and other individuals, as well as organizations that develop accessible products.
William: mobile devices
Doyle: mobile phone
<shawn> ACTION: Andrew, bcase intro: While accessibility focuses on people with disabilities, accessibility also benefits older users, mobile phone users and other individuals, as well as organizations that develop accessible products. [recorded in http://www.w3.org/2009/05/01-eo-minutes.html#action04]
Shawn: Is the sentence too complex?
Doyle: Good for me.
Andrew: Reads easily like a list.
Shawn: Anything else on intro?
Doyle: Paragraph 2: why do we need to say "can also realize" rather than "will realize"
Shawn: Because it will not in every case.
Andrew: can play with will because we do not say how much of a benefit.
Shawn: Can we back up every
statement? Maybe because we have done due diligence within the
document we can be a bit stronger in the intro?
... are we comfortable with that?
William: "will benefit from"
Doyle" be direect: "also realize"
Andrew: will realize
<shawn> Organizations with accessible Web sites also will realize business benefits such as search engine optimization,...
<shawn> Organizations with accessible Web sites benefit from search engine optimization,...
<andrew> Organizations with accessible Web sites also benefit from search engine optimization,...
<scribe> ACTION: Andrew to tersify beginning of sentence in Paragraph 2 about additional bus benefits. [recorded in http://www.w3.org/2009/05/01-eo-minutes.html#action05]
Shawn: Anthing other questions for the group Andrew?
Andrew: No, that's good for now.
<shawn> SUBTOPIC: Expanding coverage of olders users in the Social Factors page
Shawn: in socila factors, we have
a more complex question...how to include older users?
... in original we had major section refering to equal opportunities, barriers of use, overlap with digital divide and then the section "benefits for P with and with D"
... originally Andrew expanded the section Access for Older People. When we re-looked at it, it seems like expanding that section there, it doesn't flow with the naarative.
... also access for older users is a higher level issues because of equal access, overlap with accessibility, and growing demographic.
... specific question then is Agenda item 3
<shawn> Different option to add a higher subsection under "Web Accessibility is a Social Issue" section http://www.w3.org/WAI/EO/Drafts/bcase/soc-older_uses-slh.html#older
Doyle: My question is that if we move that to a higher level, another major social issue is the one for people with low literacy. How to address that?
Shawn: Is the overlap with accessibility as significant?
Doyle: I don't know.
Shawn: Keep that in mind Doyle as
we consider this.
... look at original as well as new draft with an added section. Compare and see how it would work to leave the orginal comments and link to the new section. Does it make sense? is it confusing?
Andrew: If it makes sense in principle I will make the change and see how it reads.
Liam: I agree with the priciple but can't follow the implementation.
Shawn: Look at second link in agenda. The h1 is "Social Factors..." scroll through there and I'll indicate where it would be inserted and you can judge the flow.
Liam: Suggest a more natural flow through...
<andrew> Liam: Overlap with Digital Divide Issues > Overlap with Design for Older Users > Web Accessibility Benefits People With and Without Disabilities > Access for Older People and move CSR to the bottom
Doyle: I think many disabilities are language related so when a page is presented in muti modes it is beneficial to many. I worry that much of what we focus on does not address cognitive issues, but not sure how it relates here.
<scribe> ACTION: Andrew to relook at flow especially with idea of having aging narative more integrated [recorded in http://www.w3.org/2009/05/01-eo-minutes.html#action06]
Shawn: anything else on
... plan for Business Case is for Andrew to make these changes on Monday, send out call for review to EO and WAI-AGE taks force. Please let us know by 5/13 if you have comments, approve or need more time.
... Does that work for the group? enough time?
Shawn: Everyone should speak up
if more time is needed, we can extend it.
... that wraps it up, thanks Andrew.
Andrew: Great, goodbye
Shawn: Back to agenda.
Shawn: William brought up the
fact that this is a W3C Note it is not proposed as a
Recommendation, although it is more formal that other
documents, such as Biz Case. Notes go through MUCH less
rigorous review process.
... so WAI or EO is not approving this document. We are in fact on record as saying it needs significant revision.
... does that help.
Sharron: What we know is different than the perception of the world. if it appears on the W3C site, there is implicit assumption of approval.
Shawn: What if we ask Sharron to
continue to serve on the IG.
... and continue to strongly advocate for a rewrite of the doc
Shawn: Yes, they run out in May
and expect to be rechartered.
... back to commenting on existing document
... positive note is that they have adopted our comments verbatim.
Sharron: Accessibility is well represented in the document.
Shawn: Judy recommended a section
in ToC on accessibility, that should help.
... let's review multi-channel delivery system
<shawn> Multi-Channel Delivery section http://www.w3.org/2007/eGov/IG/Group/docs/note#multi-channel
Shawn: all we focus on now is
... note accessibility coverage in new material.
Doyle: No mention of assistive
tech when mentioning various devices.
... in section "the web is a main channel..."
Shawn: what to add here?
Doyle: some mention of AT in addition to the PDAs etc
William: Maybe they do not think of it as a "wide-spread channel"
Shawn: Do we feel strongly that they should add AT here or can we accept that they are focused on mobile?
Liam: Multi channel basically
means they are talking about web, TV, mobile
... could argue that AT sits on top of that
William: Yes it sits on top of all of those
Shawn: So it is not itself a
separate channel and does it need a mention?
... may not fit specifically in this paragraph.
Liam: Yes, the very next paragraph mentions AT
Shawn: Let's look
Doyle: This is the only place where they mention accessibility in the entire section. "accessibility aspects" what does that mena in this context? It is very unclear what that means. I would like clarity rather than a vague phrase.
Shawn: Was it mentioned earlier in the document.
Doyle: If so, link to the defintion.
Liam: Difficult to comment out of context.
Shawn: Would be great if the IG
could publish an updated Working Draft, put it out for more
comment, breathe, recharter and get an editor.
... with a little more time, we could probably get them some strong expertise.
... feel free to ask and suggest.
William: The tentative tone is
... will make suggestions to their list
Shawn: Let's go through this
section and the next section, search for references to
accessibility and review.
... The section "facilitating..." needs to say soemthing like PWD are often found in this category but not ALL
Liam: It does apply to many with disabilities, because even though you may use a wheelchair and be perfectly able to use computers without AT, you still face the challenge of getting there.
<scribe> ACTION: Sharron to take a look and perhaps link to Biz case Overlap [recorded in http://www.w3.org/2009/05/01-eo-minutes.html#action07]
Shawn: They reference many many external documents can you see appropriate places for them to reference policies, Biz case, Intro, components, How PWD use the web intro, etc
Liam: Only one reference to WCAG
and omits fact that it is designed to be legally
... has good reference to accessibility but without seeing whole doc, hard to identify the gaps.
Shawn: Another mention of
accessibility under "Using Standards, Principles...."
... comments on that?
... broadly what we would want is that the first bullet be just accessibility, take out the second bit because it is covered below.
William: what is ...API?
Shawn: don't know but not relevant.
<scribe> ACTION: Sharron to suggest in accessibility bullet, take off the mobile reference and then leave bullet that has both together. [recorded in http://www.w3.org/2009/05/01-eo-minutes.html#action08]
<shawn> ACTION: Sharron: eGov under "Using standards, principles and best practices:" - accessibility bullet, take off mobile part. leave the bullet that has both together [recorded in http://www.w3.org/2009/05/01-eo-minutes.html#action09]
<shawn> "relationship between Web Content Accessibility and Mobile Web [WAI-MWI]."
Shawn: When they reference relationship of accessibility/mobile web, ask them to change that reference to something more like WCAG/MWBP
<shawn> ACTION: Sharron: change "relationship between Web Content Accessibility and Mobile Web [WAI-MWI]." to something like [WCAG-MWBP] [recorded in http://www.w3.org/2009/05/01-eo-minutes.html#action10]
Shawn: use of accessible outside of defintion...filter for that.
Liam: Casual conversation led to the conclusion tha the public sector emphasis is on usability more than accessibility.
William: In Madrid, Brussels,
CSUN shocked at the number of people whose profession is now
... in Brussels 30 or more were from the Commission
Shawn: We have been in reactive
mode and so in May as we look at what next, the issue of
usability and accessibility is one of the things we address in
... One of the issues is the overlap between accessibility and usability and may be next in the WAI-AGE agenda.
William: and should be a focus of e-Gov
Shawn: Keep in mind what you got from that and in May maybe even at the next meeting, where will EO put resources next, so be thinking about it.
William: At CSUN, much higher
number of Deaf participants.
... Deaf/blind as well. More participants by PWD at CSUN as opposed to Europe.
Shawn: Lisa Harrod, scenario girl
wrote a piece on Deaf issues and accessibility published on A
LIst Apart. Translation between Australian Sign and ASL at CSUN
and the experince made her giddy, despite a few
... Managed to make it to the end of this meeting, probably not meet next week. Will follow up with Sharron about eGov work.
... if meeting is needed, Judy will chair. Review Andrew's revisions next week and on May 15 we will look at plans for the next year.
<shawn> zaki, who is here?
<shawn> ACTION: Sharron look for appropraite places to reference WAI docs (which are listed at http://www.w3.org/WAI/Resources/Overview) [recorded in http://www.w3.org/2009/05/01-eo-minutes.html#action11]
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) Found Scribe: Doyle Found ScribeNick: doylesaylor Found Scribe: Sharron Inferring ScribeNick: Sharron Scribes: Doyle, Sharron ScribeNicks: doylesaylor, Sharron Default Present: doyle, Sharron, Shawn, Loughborough, +0137383aaaa, LiamMcGee, andrew Present: doyle Sharron Shawn Loughborough +0137383aaaa LiamMcGee andrew Got date from IRC log name: 01 May 2009 Guessing minutes URL: http://www.w3.org/2009/05/01-eo-minutes.html People with action items: . accessibility andrew appropraite between change content for look mobile places relationship sharron wai-mwi web[End of scribe.perl diagnostic output]