<scribe> scribe: char
Group has had various discussions about risk of legal actions.
Intention of these slides is that anyone using them will customize them before presenting them.
KarlGroves: It might be too problematic to include anything on risk because of differences between W3C and specific country regulations.
Shawn: We have to decide if we should remove this slide or keep some kind of version that people should customize
(referring to "Reduces risk of legal action", currently Slide 13)
<Vicki> Hmn, I don't particularly like the graphic... it is rather daunting
Shadi: Implementing standards reduces risk of legal action, no matter what country. This is still one of the major drivers.
... Slide should be presented as a benefit, not a negative. Slide should be included, likes the current wording.
Shawn: Vicki and Shadi both think the current photo is too daunting.
Helle: We could rework the presenters notes so that the "Notes to presenters" (about "deleting the slide if not necessary") is at the beginning, not more toward the end.
Shawn: Deck will be used online (without seeing presenters notes) and downloaded.
Helga: Maybe we could add a note to the slide itself then to cover this point so that all are aware.
Shawn: making notes to editor in PPT based on discussion
Shawn: Now talking about "Return from accessibility", currently slide 26. Graphic of "money tree" (using generic bills as leaves, although it's not really obvious).
<Vicki> if i were to choose between the tree and the graph (slide which follows), i would go for the slide with the graph.
Shadi: Some websites do not generate income, so this may not have meaning. Helle agrees, thinks social benefits should be emphasized.
... Perhaps we should rework these areas to greater emphasize all benefits at the beginning and then mention the financial/monetary aspect
Shawn: We could leave "Return from accessibility" as is, and then add more slides on the other benefits...these are mentioned at the beginning, but could be reiterated here
Note: Shawn is the editor for these slides
Shawn: Watch for new version coming soon. Char will convert to HTML, but we want to get content stable before conversion so that we don't have to make double-edits.
Judy: Current content doesn't yet include discussion items from last week.
Judy: Today we'll discuss the section on Web Accessibility and the Role of Standards
Wayne and Cliff: This section would make a great introduction. Helle agrees.
Shadi: Missing the role of standards in accessibility and their importance in this document.
Cliff When businesses can rely on local standards harmonizing with international standards, it is easier to do business in a global setting.
Shadi: Section is introductory and repetitive (from other docs).
Judy: Some of the basics need to be repeated, so this is deliberate. Trying to make sure that it isn't significantly redundant. Not expecting audience to chase links for more info.
Shawn: General preference is to not repeat info across documents, but we need to hit a balance. See http://www.w3.org/standards/webdesign/accessibility.
Judy: More links will be provided, they haven't been added yet.
Cliff: would like to see more subheads in this section, provide some quick examples.
Judy: Does first paragraph work as is? Needs input from group. The intent of this section is to explain W3C and guidelines. More about harmonization in rest of document.
Judy will look more carefully at paragraphs and flow in this section.
Cliff: People will want to know why they should use accessibility and how everything works together. This document must be self-inclusive because people probably won't click links to get more info.
Judy: There will be some links, but this will be a complete concise package.
... Recognizes the heading/content mismatch. Will talk to editor.
Shawn: Looks like this is taken from old content, updated content is available. See http://www.w3.org/standards/webdesign/accessibility.
Char hates semicolons
<Vicki> can we take out this wording "a broadly held goal among governments, people with disabilities, and many businesses. Access to information "
Shawn: Good to mention UN convention, not sure about "rapidly adopted by a number of countries".
<Vicki> i think there is a standard manner of quoting the rapidity of the adoption of this Treaty, and I will look into it for you.
Judy: (in response to Char) Have to be careful how much info we refer to (wrt UN conventions) so that we don't get into politics.
<Vicki> For me, the impact on the convention is lost
Shawn/Judy: Have to be careful using too many links, especially if someone prints the document. Shawn suggests using Shadi's "include" script to grab pieces that are needed.
Judy: How can we better refer to examples and references?
Wayne: Could use just one example instead of many.
<shawn> Examples of web accessibility http://www.w3.org/standards/webdesign/accessibility#examples
Judy: Trying to gracefully integrate all info on W3C accessibility initiatives in last part of this section; wonders if information is there but disjointed.
Judy: What are some different thoughts about what the heading of this section should be?
Shawn: "Introduction" (;-) )
Judy: Content will morph a bit.
Helle: If this section becomes part of introduction, then current Introduction section also needs to be reworked.
Char: Not sure we can help with heading text until we see reworked version.
Helle: Likes current heading ("Web Accessibility and the Role of Standards").
Judy: Look at Introduction section, which we discussed last week. Questions/concerns about statistics still to be addressed. Most people didn't like second paragraph, so editor has a request to rework it.
ShawnPeople may encounter barriers when going about essential tasks on the Web.
Cliff: Maybe use my earlier statement ("when businesses can rely on local standards harmonizing with international standards, it is easier to do business in a global setting") to present fragmentation more positively.
This concludes Harmonization document discussion.
Shawn will not be online at the next meeting, Judy will send out email on Thursday for discussion.
<shawn> Remember to update Availability for Upcoming EOWG Teleconferences http://www.w3.org/2002/09/wbs/35532/availability/