See also: IRC log
<scribe> scribe: Wayne
<shawn> who is muted?
<Henny> Apologies I have to dial out via reception and they are not answering.
<shawn> meeting: EOWG
<shawn> chair: Judy
<shawn> "WAI-AGE" (Web Accessibility Initiative: Ageing Education and Harmonisation), a European Commission funded project
judy: The initial work on WAI-AGE will be literature review. We want to look across EO materials with update for individuals who are aging.
<shawn> ACTION: Judy fill in background on WAI-AGE project in the minutes [recorded in http://www.w3.org/2007/02/09-eo-minutes.html#action01]
William: Is this associated with American Association of Retired People involved (AARP)?
Judy: Not at this time.
Jack: What is the time frame and outcomes.
Judy: This is a three year project starting January 2007. Add in outreach to aging to related documents. Sometines take issues to other WAI groups.
William: Is aging going to be loss of vision, mobility ... rather than aging as a disability?
Judy: We are hoping that we can
includes many of the functional disabilities of aging. There is
a history of how these are addressed. Often separately... More
together in Europe ... More separate in US.. many people in EO
are interestes.
... Who is interested and how about concerns?
Doyle: There is really not a distinction between aging related disabilities and ordinary disability.
Judy: Sometimes we write in a way that is geared to disability community and people with aging ralated disabilities often don't find the information.
Alan: Aging being excluded because of lack of training to us IT. Services are provided on the Web rather than face to face and individual who are aging may be excluded.
Andrew: Lack of familliarity is being considered in Austrailia. They did not grow up with IT, and they don't change between interfaces very well.
Doyle: Many tools will be wearable. Emergency services on the web will be accessible.
<shawn> is shawn
Shawn: We have the document on
the Task Force working group.
... This was discussed at a general discussion of the
face-to-face and at a small working group.
<Harvey> Temporary inaccessibilities I encountered: see under my accessibility page:
Jack: Does not see the connection between the audience and the purpose goals and objectives.
Judy: Are you saying that this resource would not be for Mom and Pop websites.
Shaw: There were two points of view: [Guidelines in plain language or a tutorial on how to make the website accessible.]
<Harvey> http://www.hbingham.com/accessibility/index.htm link under Motivation to Inaccessibilities and Ways to Overcome Them
Shawn: Breakout group found some need for explanation as well as just simplified guidelines.
Alan: We need a simplified document for people like the press.
Judy: Do you mean that we need to control the simplification.
<judy> ACTION: cl-basics -- add to "audience" -- journalists needing to write something quickly [recorded in http://www.w3.org/2007/02/09-eo-minutes.html#action02]
Alan: Yes. Someone who is writing in public policy without deep web knowledge.
Justin: What would a reader take away?
<judy> ACTION: cl-basics -- add to "purpose" -- be able to control the simplification -- write it before someone else does. [recorded in http://www.w3.org/2007/02/09-eo-minutes.html#action03]
Shawn: A quick reader will look to wee what WCAG is about.
Justin: If I wanted to say how to make a data table accessible would that be here.
Andrew: Take out specialize language like "programatically determined" will be converted comon language.
Shawn: To simplify the document you must limit the scope.
<judy> ACTION: cl-basics -- add to purpose -- limit the scope so that we can simplify the language. [recorded in http://www.w3.org/2007/02/09-eo-minutes.html#action04]
Justin: Would this be like quick tip document?
Shawn: Kind of..
<judy> ACTION: cl-basics -- add to purpose??? -- turn all of wcag 2.0 into quick-tip type language [recorded in http://www.w3.org/2007/02/09-eo-minutes.html#action05]
Jack: How are we limiting the scope to focus on a particular group of people.
Shawn: Many people say, "I tried
to read WCAG 2.0 and couldn't read it."
... These were Web Accessbility exerts making the same
comments.
Shadi: Have heard the same comments. Those developers should be able to read the guidelines. I think thisis a problem with the guidelines, not the need for a separate document.
Judy: If that is the kind of feedback we are getting, then we still need to work on the language in the WCAG documents.
z
Andrew: I have problems reading the technical requirements of any kind. I am not sure that we should change the WCAG.
<Andrew> Andrew: wgac is a Tech Rec, not a how to do accessibility. Like the XHTML TR is not about how to buide a web site
Justin: People have a mental model is that WCAG will show you how to get your website accessible. It is being played up as something it not is.
Shadi: Technical specifications are for developers and should be readable by developers. If developers cannot read them then maybe we should change it.
Judy: Let's look very honestly at
the kind of feedback we are getting at home, and explore
language... See what could be done with the wording to preserve
the eaning. Don't want to get stuck in the assumption that
technical specification must be [difficult].
... We need to be careful about how technical specifications
need to be difficult.
<shawn> wayne: wcag is pretty hard for me to read
Shawn: If WCAG becomes clear then this will not be necessary.
Doyle: This is a basic problem with how we commuicate with each other. Text based communication. This is the most important conversation we can have.
<shawn> http://www.webstandards.org/2007/02/08/what-to-do-with-wcag-2/
Justin: Web Standards Post. Look at a public perspective.
<Andrew> Justin: http://www.webstandards.org/2007/02/08/what-to-do-with-wcag-2/
This is scribe.perl Revision: 1.127 of Date: 2005/08/16 15:12:03 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/Topic: Update on Aging/Topic: Update on WAI-AGE project/ Succeeded: s/getting the we do need to fix/getting, then we still need to work on the language in/ Found Scribe: Wayne Inferring ScribeNick: Wayne Default Present: doyle, Jack, Shadi, Alan, Bingham, Judy, Wayne_Dick, Shawn_Henry, Loughborough, Andrew_Arch, Justin, Henny_Swan, Sylvie_Duchateau\Tanguy_Lohéac, +1.604.689.aaaa, shawn Present: Alan doyle Jack Shadi Bingham Judy Wayne_Dick Shawn_Henry Loughborough Andrew_Arch Justin Henny_Swan Sylvie_Duchateau Regrets: [scriber pls pull from mailing list] Agenda: http://lists.w3.org/Archives/Public/w3c-wai-eo/2007JanMar/0034.html Got date from IRC log name: 9 Feb 2007 Guessing minutes URL: http://www.w3.org/2007/02/09-eo-minutes.html People with action items: -- add cl-basics judy WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]