Shadi: see http://www.w3.org/WAI/EO/Drafts/eval/tools/simple
<scribe> ACTION: changelog - add W3C (not WAI) to Web Content ... [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action01]
<scribe> ACTION: if any tools specifically support Italian or other laws, then add later. Need to check up. [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action02]
<scribe> ACTION: changelog - make sure there results report is very clear about how the selections have been combined [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action03]
<scribe> ACTION: changelog - consider that search become OR rather than AND, especially within language [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action04]
<scribe> ACTION: ensure that the language list matches the order on the W3C translations page [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action05]
Shadi: see advanced search - http://www.w3.org/WAI/EO/Drafts/eval/tools/advanced
... what about the way the Repair Options are listed?
All: ok as is
Shadi: look at Type of tool / on-line service
<scribe> ACTION: Shadi & Andrew to consider wording [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action06]
<shawn> ACTION: changelog, check "spelling" of Free Ware, Share Ware, etc. should be one word? [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action07]
Shadi: next steps?
Shawn: should circulate the results wording
before calling for survey (vote)
... is the title still appropriate? it is much more than a list now.
<shawn> Web Accessibility Evaluation Tools Search
<shawn> Web Accessibility Evaluation Tools Search
<shawn> Web Accessibility Evaluation Tools Database
<shawn> or even Web Accessibility Evaluation Tools List
<shawn> Web Accessibility Evaluation Tools Database Search
<shawn> Web Accessibility Evaluation Tools List Search
<judy> Web Accessibility Evaluation Tools
Jack: Simple Search of Web Accessibility
Evaluation Tools
... Advanced Search of Web Accessibility Evaluation Tools
<scribe> ACTION: long name - "Web Accessibility Evaluation Tools" [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action08]
<scribe> ACTION: short name for navigation - "Tools Search" [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action09]
<shawn> http://www.w3.org/WAI/EO/Drafts/retrofit/Overview.html
<shawn> scribe: shawn
http://www.w3.org/WAI/EO/Drafts/retrofit/Overview.html
<scribe> scribe: hbj
<scribe> scribenick: hbj
changelog: wish list suggestion to make more difference between H2 and H3
on the WAI web site
<scribe> ACTION: consider to use "elements that impact many pages" as subheading for Prioritizing by [area....] for [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action10]
<judy> wrt clarifying the responsibilities, perhaps this can be combined into distributed tasks...
<judy> hbj: or ...responsibilities... could be figuring out whose fault it is
<judy> slh: want to figure out how it got this way...
<judy> nl: combine distrib & clarif resp
<judy> ..leave out the blame
<judy> karima: use importance of awareness as a lead-in for distributing
<Andrew> Scribe: Andrew
<scribe> Scribenick: Andrew
Judy: delivery unit - proposed change is good
shadi: keep the term delivery unit in the glossary explanation for those who understand the term
Judy: "normative"
... no updates right now - still need to check
... "programmatically determined"
Shadi & Andrew: not just assistive technology - also user agent
Judy: "real-time event"
Shadi: event may be virtual - not necessarily real-world
Judy: see - http://lists.w3.org/Archives/Public/w3c-wai-eo/2006JanMar/0111.html
for suggestions
... we have other problems too - not no solutions
... "unicode"
Andrew: what about xref to something from i18n, eg http://www.w3.org/International/questions/qa-doc-charset
The universal character encoding [maintained by the Unicode Consortium],
which provides the basis for processing, storage and interchange of text
data in any language in all modern software and information technology
protocols.
<Jack> The universal character encoding [maintained by the Unicode Consortium], which provides the basis for processing, storage and interchange of text data in any natural in all modern software and information technology protocols.
<Jack> Modified: The universal character encoding [maintained by the Unicode Consortium], which provides the basis for processing, storage and interchange of text data in any natural in software and information technology protocols.
<shadi> http://www.unicode.org/standard/WhatIsUnicode.html
Judy: the universal character encoding [maintained by the unicode consortium] which provides the basis for processing, storage and interchange of text data in any natural language in software and information technology protocols
<shadi> [14:20] <r12a> how about "whose goal is to provide the means by which text of all forms and languages can be encoded for use by computers."
<shadi> [14:20] <r12a> taken from http://en.wikipedia.org/wiki/Unicode
<shadi> Unicode is an industry standard whose goal is to provide the means by which text of all forms and languages can be encoded for use by computers.
Shadi: see http://www.w3.org/WAI/EO/2005/Demo/report
... introduced the project briefly
... today's question is how do we structure the report on the changes
Andrew/Helle: should "features list" become part of the report?
Helle: intro is to the topic, not this report
discussion: the current ES is more of an intro. ES should stand alone and give a quick overview of the tests and the results and did they do ok, or really bad or ...
Shadi: background section
... looking over current template - http://
<scribe> ACTION: background section gets split to intro and other sections [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action11]
shadi: findings section
<judy> saz: w/in images, broken out different kinds of problems
<judy> ...would it be better to also group the examples, or to separate them?
<scribe> ACTION: findings should illustrate the problem and solution, with representative samples, rather than trying to be exhaustive/complete [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action12]
Judy: see http://www.w3.org/WAI/EO/Drafts/standard-harmon-20060301.html
... also the changelog - http://www.w3.org/WAI/EO/Drafts/standard-harmon-changelog.html
... talked us through the changelog
<scribe> ACTION: 1. bold "stds harmonisation" in para 1 overview; 2. bold "a consistent international set of technical standards for accessibility"; 3. breakout (and try bolding) web content etc to a list [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action13]
Judy: looking at the Current Situation section
<Jack> Here is another take on the 1st paragraph we were just discussing:
<Jack> This document uses "standards harmonization" to refer to the adoption of a consistent international set of technical standards for web accessibility. Technical standards for web accessibility refers to content, browsers and media players; authoring tools used to develop Web content, and the accessibility of the authoring tools themselves.
<scribe> ACTION: try presenting as a table of driver and answer - and shorter / more concise [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action14]
<scribe> ACTION: also a better intro sentence - maybe taking about "misconceptions that have contributed to ..." [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action15]
judy: looking at "consequences" section
<judy> ACTION: jb add something to resource section, as preface before policy links, such as: "While governmental laws and policies naturally will differ according to local needs, it is still possible to refer, within governmental policies, to a consistent set of international technical standards... see the following documents for examples of different ways that this can be done." [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action16]
<judy> ACTION: jb: [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action17]
<judy> ACTION: jb also add: "Similarly, organizational policies, which necessarily differing according to the circumstances of the org, can still reference a common set of technical guidelines" [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action18]
<judy> ACTION: jb add in references to wcag and atag 2.0 [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action19]
<judy> ACTION: stress more that it is a *world*wide*web and the rest of the world is looking at your material [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action20]
<scribe> ACTION: change the word "priority" to now/later etc, eg "For example, poor colour contrast in the main content is high priority, whereas in generic footers it may be low priority." to "For example, poor colour contrast in the main content is rectified immediately, whereas in generic footers it may be adressed later." [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action21]
<scribe> ACTION: consider another eg as for corporate this may be inappropriate [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action22]
Shawn: help please - Andrew & Henny volunteered
<scribe> ACTION: change "For example, repairing barriers in footers could require one change that is automatically propagated throughout your Web site, or could require changing every page." to "For example, repairing barriers in footers could require a simple change to the template that is automatically propagated throughout your Web site, or could require changing every page." [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action23]
<scribe> ACTION: try and contrast the type of skill rather than the level for CSS vs ALT [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action24]
<scribe> ACTION: in "Prioritizing by Barriers" keep the essence of the [] para - maybe move to after the list [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action25]
<scribe> ACTION: in "Prioritizing by Area" - The most important pages, and the path to get there from the common entry points. |or| Pages and functionality that serve the main purpose of the site, and the path to complete any transaction that serves the same purpose. - make wordy more friendly. try to keep 'main purpose', keep 'paths' change functionality to 'tasks' [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action26]
<scribe> ACTION: in "[content of particular relevance for people with disabilities]:" strengthen the "don't make assumptions" bit - maybe weave in with previous point [recorded in http://www.w3.org/2006/03/02-eo-minutes.html#action27]