See also: IRC log
<shawn> agenda: http://lists.w3.org/Archives/Public/w3c-wai-eo/2006OctDec/0056.html, flyer questions: http://lists.w3.org/Archives/Public/w3c-wai-eo/2006OctDec/0058.html, correct URIs: http://lists.w3.org/Archives/Public/w3c-wai-eo/2006OctDec/0061.html
<shawn> scribe: Wayne
<shawn> scribenick: Wayne
zakim mute me
Judy: We had a long discussion on the opening and closing paragraph. ... addressed the comments that had been raised. [this did not seem to read correctly so we will look at a view variations]
<shawn> http://www.w3.org/WAI/EO/changelogs/cl-flyer.html
Judy: Look at flyerfron6
<shawn> http://www.w3.org/WAI/EO/Drafts/flyerfront6.en.html
This uses the paragraph: The World Wide Web Consortium is the international standards body for the Web. The W3C's Web Accessibility Initiative (WAI) develops strategies, guidelines, and resources to make the Web accessible to people with disabilities..
In the closing paragraph: WAI welcomes your participation and support. WAI develops accessibility solutions through a consensus process with industry, disability organizations, accessibility researchers, governments and others. To learn more, visit http://www.w3.org/WAI/participation, there may be added language describing the disabiities.
Note: There were technical problems and Judy describes alternatives.
<Helle> me/zakim, unmute me
<Helle> me/ zakim unmute me
<Helle> me/ zakim, unmute me
<shawn> refresh
William: Supports just saying "people with disabiities"
<Harvey> To disability list, I'd add "dexterity"
Judy: the point of more delineated language is to educate audiences that don't percieve the need.
<Alan> +1 for 6
Justin: is for 5 (more detail)
<Alan> +1 for 5, sorry
Doyle: Works to improve in shorter version, developes guideline in other sentence.
Henny: prefers listing disabilities. could be used internationally and the iformation can't be taken for granted.
<shawn> CHANGELOG: if go with version6, need to add "(W3C)" in the first sentence
Helle: Prefers the standards
sentence and mildly prefers listing disabilities.
... also expressed a wish for an aging item.
<Alan> akc Alan
<shawn> W3C's Web Accessibility Initiative (WAI) works to improve Web accessibility for people with visual, auditory, physical, cognitive and neurological disabilities, and people with accessibility issues due to aging.
<judy> here's one possible sentence to look at:
<judy> W3C's Web Accessibility Initiative (WAI) works to improve Web accessibility for people with visual, auditory, physical, cognitive and neurological disabilities, and people with accessibility needs due to ageing.
<shawn> WAI develops strategies, guidelines, and resources to make the Web accessible to people with disabilities. This includes people with visual, auditory, physical, cognitive and neurological disabilities, and people with accessibility needs due to ageing.
<judy> W3C's Web Accessibility Initiative (WAI) works to improve Web accessibility for people with visual, auditory, physical, cognitive and neurological disabilities, and people with accessibility needs due to ageing.
<judy> W3C's Web Accessibility Initiative (WAI) works to improve access to the Web for people with visual, auditory, physical, cognitive and neurological disabilities, and with accessibility needs due to ageing
Group: Accessibility needs due to aging seems to be acceptible.
yes, Helle
Liam: disagrees with inclusion of aging... Aging seems to be included with othe disabilities...
William: [with emphasis] Aging is a disability on its own.
<Harvey> Harvey is also in favor of aging!
<Liam> Ohter categorisations too though... acute illness, childhood etc...
<shawn> consensus: add ageing (most strongly in favor, one OK with group decision)
Judy: Conclusion: Listing the disabilities is needed for educating peope with little experience, and adding aging is important.
<shawn> WAI develops strategies, guidelines, and resources to make the Web accessible to people with disabilities. This includes people with visual, auditory, physical, cognitive and neurological disabilities, and people with accessibility needs due to ageing.
Judy: this may impact the physical fit of the one page flyer. Suggest: leave this issue to editors with the graphic designer.
<shawn> [several participants said "good" to: "WAI develops strategies, guidelines, and resources to make the Web accessible to people with disabilities. This includes people with visual, auditory, physical, cognitive and neurological disabilities, and people with accessibility needs due to ageing."]
Helle's Email
<shawn> http://lists.w3.org/Archives/Public/w3c-wai-eo/2006OctDec/0063.html
Helle: All the items seem to be titles... The term resources to doesn't translate directly.
<shawn> Shawn: it is out of balance with a sentence between "WAI Activities" and the bullets below, and not between "WAI Resources" and the bullets below
<shawn> decision: no sentence between headings and bullets
Group: No leading lines for Activity and Resource list. Helle may translate "resources" differently.
<shawn> minutes from previous discussion: http://www.w3.org/2006/10/27-eo-minutes.html#item02
Judy: [would like comments on changes in how people are understanding and working on web accessibility]
William: Web phoebia... how extensive is this.
Liam: Clients are asking about accessible web and standards complients.
Judy: Accessibility is becoming a quality indicator for web development.
Henny: People are focusing on the business case.. In UK the legal impact .... gotten it in the press. Some large entities have published business cases and [case studies]. Business benefits...
<Zakim> shawn, you wanted to ask -- what's needed now
Shawn: What do you see as needed now [from WAI].
Liam: Best practice is more important. People get WCAG 1. Care will need to be taken in rolling out WCAG 2.0. May upset a market where WCAG 1 is accepted as best practice.
Judy: [The benefit of the acceptance of standards may be risked by the roll out of WCAG 2.0]
Liam: ... a formal communications strategy is needed... where the obsticals are and how do address them.
William: CSS came out a while back and patience is needed.
<judy> wayne: people do accept wcag 1.0 as best practice. wcag 2.0 will be an improvement, but we need to transition people's undestanding of that as a leading quality indicator of web design
Justin: Web development opion makers (A-List Developer Authors) have a disroprotional impact. We need to identify our own A-list authors to express support for WCAG 2.0
Wayne: 562-493-8210
Harvey: Nov 14th World Usability Day
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) Found Scribe: Wayne Found ScribeNick: Wayne Default Present: Judy, Wayne_Dick, Shawn, Doyle_Saylor, Loughborough, Bingham, Henny_Swan, Helle_Bjarno, Alan, Liam_McGee, Justin Present: Judy Wayne_Dick Shawn Doyle_Saylor Loughborough Bingham Justin Alan(first_half) Liam_McGee Henny_Swan Got date from IRC log name: 3 Nov 2006 Guessing minutes URL: http://www.w3.org/2006/11/03-eo-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]