See also: IRC log
Topic 1:
Outreach
<shawn> the new WAI site is up ! ! !
Shawn: Thanks to Justin for his help!!!
William: Talking signs are
included in transportation legislation on its way to the
president.
... The bill has gotten through both houses and conference
committee.
<shawn> http://www.w3.org/2002/09/wbs/35532/WAI_EOWG_F2F_S05/
Judy: Is the WBS usable? ...
overall yes
... Asked the group to fill out the WBS form on Face to Face
during the meeting time.
<shawn> http://www.w3.org/WAI/highlights/about-rss.html
Judy: The RSS page now is a placeholder, but it also attempts explain the meaning of RSS in plain language.
Alan: There are sites on RSS readers to link to.
Shawn: To find RSS readers on Google
William: Can this be a form. From an accessibility point of view this is a nightmare.
Shawn: There are different methods, so explaining all will be difficult
Justin: This keeps people up to date without having to reread lots of stuff.
<Andrew> from "blogspace.com/rss/readers" - RSS and Atom files provide news updates from a website in a simple form for your computer. You read these files in a program called an aggregator, which collects news from various websites and provides it to you in a simple form.
William: This (RSS) is very important... We need to explain it.
<judy> Waynethis is a mechanism to alert people when new information becomes available.
<judy> (that was from wayne)
Doyle: Take Andrew's comment without the aggregator term
<shawn> RSS reader (called an "aggregator")
Andrew: We need the concept of aggregation.
<shawn> Judy: "footer" type info - for more info on RSS... RSS stands for...
Judy: How do we tie this back to WAI?
Harvey: It would be nice to get a how to description.
<shawn> shawn: perhaps provide button to Google Search results for readers (not sure this was minuted earlier)
<Zakim> shawn, you wanted to ask when RSS page comes up: anyone able to test RSS feed ?
Judy: A lot of people would need it.
<Andrew> Andrew: we intend to use the feed to diplay WAI news on our website
Judy: We present it as a usefull new technology and give a gentle introduction.
<judy> jb: rss is something that's become available recently; it's a way of getting updates of new information from a site; it's fairly easy to sign up for; here's what we plan to deliver over it, and why that might be useful for you; here's how you find out more; here's how you sign up for it.
<judy> ...and you can even build the rss feed into your web siteShawn:
<judy> (last from shawn)
Shawn: We need to note the two uses is individual and site references.
<Harvey> Include how to subscribe to a variety of RSS sources
<shawn> sidenote: http://lists.w3.org/Archives/Public/w3c-wai-ig/2005JulSep/0000
<shawn> Call for WCAG 2.0 Working Draft review
William: RSS is deserving of an explanation and it use to accessibility.
<shawn> http://www.w3.org/WAI/intro/accessibility-new.php
<Justin> http://lists.w3.org/Archives/Public/w3c-wai-eo/2005JulSep/0043.html
<shawn> Judy: new WAI design uses interim logo....
<shawn> eowg suggestion: swap 2nd & 3rd paragraphs
<shawn> (shawn really likes that suggestion on first reaction!)
<Helle> http://www.w3.org/WAI/lexicon/
<Justin> http://www.w3.org/WAI/lexicon/Overview
<judy> from lexicon: Web accessibility means that the Web is designed so that people with disabilities can perceive, understand, navigate, and interact with it effectively, as well as create and contribute content to the Web.
<shawn> (which is in Version 1.1 of this doc: http://www.w3.org/WAI/intro/accessibility.php)
<shawn> eowg suggestion: ... and that they can contribute to the Web.
Why accessibility is important?
<shawn> question about grammar: An accessible Web can also help people with disabilities ?*TO*? more actively participate in society.
Shawn: People who don't know the issues of accessibility may not get the third paragraph a their first introduction to why web accessibility is important.
Judy: Reorder the paragraphs to
1, 3, 4, 2.
... Why are we reordering paragraphs: We are trying to present
all the concepts in one place. So, reordering may be
needed.
<shawn> eowg suggestion: "Why Web Accessibility is Important" section: swap order 1, 2 goes to 4, 3 goes to 2, 4 goes to 3... (result: 1 as is, 2 unprecedented, 3 Social, 4. legal)
<shawn> 1 p, 2nd sentence:
<shawn> It is essential that the Web is accessible in order to provide equal access and equal opportunity to people with disabilities.
Making the Web Accessible
<shawn> ...essential that the Web [is/be/become] accessible
<shawn> eowg suggestion: second section, first paragraph, second sentence ...essential that the Web @@be@@ accessible...
<shawn> ? "People developing Web sites need to know about and address Web accessibility."
<shawn> address ? implement ? adopt ?
<shawn> drop "know about"
<shawn> know about accessibility and build it into their sites
<judy> ...need to Wayne: know about accessibility adn build it into theri sites...
People developing web sites need to know about web accessiblity and build it into their sites.
Helle: The use of accessibility with web may be misleading.
Judy: Will using accessibility witout the pairing "web accessibility" cause translation problems.
<shawn> suugestion: careful about using "accessibility" without "Web"with it
<shawn> build > include
<shawn> part of process
<shawn> part of
<shawn> eowg suggestion: People developing Web sites need to know about and address Web accessibility. (see suggestions above)
Shawn: After pointing to "Implementation Plan" follow with a reference to the "Intro toWCAG".
<shawn> eowg suggestion: after "The document "Implementation Plan for Web Accessibility" lists basic steps for addressing accessibility in Web projects." add sentence pointing to wcag overview (implementation is management, point to developer stuff)
<Harvey> Does "standard XHTML" imply that HTML is deprecated?
<shawn> i wonder in response to Helle's comment, adding something about how tools can make it easier to "The document "Essential Components of Web Accessibility" describes the different responsibilities for Web accessibility, and how specific improvements could substantially improve Web accessibility."
Helle: It seem like a lot of excessive extra work... "The effort required to make a site accessible depends on many factors..."
Natasha: Web developers and web tools, here we only talk about developers.
Shawn and William disagree.
<shawn> "The effort required to make a site accessible depends on" > Making a site accessible can me simple or more complex depending on...
Shawn: Maybe the paragraph on web conponents on the "making an accesible web" should be stronger about factors other that the developers lead inaccessible web sites.
Judy: We need to move the
agenda
... Take task force issue first, Have Shawn look at survey
<judy> http://www.w3.org/WAI/EO/2005/erstf.html
<judy> http://www.w3.org/WAI/EO/2005/ers-req.html
Judy: Will send out a query on the documents with a simple multiple choice response.
We will not have a meeting next Friday
Post Meeting Notes:
<Justin> http://www.w3.org/WAI/intro/accessibility-new.php
<shawn> "The effort required to make a site accessible depends on" > Making a site accessible can me simple or more complex depending on...
<shawn> simple, easy...
<shawn> complex, complicaetd...
<Andrew> easy - difficult ??
<shawn> heading: Making a Web Site Accessible > an Individual Site, a Specific... Your
<shawn> eowg suggestion Making a Web Site Accessible > Making Your Web Site Accessible
<shawn> eowg suggestion: "The effort required to make a site accessible depends on" > Making a site accessible can be simple or complex depending on...
<shawn> eowg suggestion: Making the Web Accessible section - maybe add stronger the idea that it's not all the developer's responsibilities -- or transition in the beginin of the Making Your Web Site Accessible section
<shawn> Evaluating a Web site for Accessibility
<Andrew> evaluating the accessibility of a web site
<shawn> Evaluating the Accessibility of a Web Site or Evaluating the Accessibility of Your Web Site
<shawn> eowg suggestion: Evaluating the Accessibility of a Web Site
<Harvey> We have an EO outreach responsibility to point out to other
<Harvey> webmasters what they can do to recognize and improve the inaccessibility of their websites
<shawn> eowg suggestion: link 2nd word in resources on managing accessibility, to detailed technical references.
EO Suggestion: When the Lexicon is done include a pointer to the Lex document in the Terminology Section:
This is scribe.perl Revision: 1.126 of Date: 2005/05/16 16:49:48 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/.../Wayne/ Succeeded: s/.../Shawn:/ Succeeded: s/know about/ Wayne: know about/ No ScribeNick specified. Guessing ScribeNick: Wayne Inferring Scribes: Wayne Default Present: Shawn, +1.517.432.aaaa, Helle_Bjarno, Justin, Bingham, Loughborough, Doyle_Saylor, +40.39.147.3aabb, Andrew, Wayne, Chuck_Letourneau, Alan_maybe, Judy, Jack, Tanguy, Alan, Natasha Present: Shawn +1.517.432.aaaa Helle_Bjarno Justin Bingham Loughborough Doyle_Saylor +40.39.147.3aabb Andrew Wayne Chuck_Letourneau Alan_maybe Judy Jack Tanguy Alan Natasha Regrets: Liam Pasquale Ron Agenda: http://lists.w3.org/Archives/Public/w3c-wai-eo/2005JulSep/0041.html Got date from IRC log name: 29 Jul 2005 Guessing minutes URL: http://www.w3.org/2005/07/29-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]