<shawn> action, shawn: testing
<shawn> ACTION: testing [recorded in http://www.w3.org/2006/02/27-eo-minutes.html#action01]
<shawn> TESTING
Shawn: lets look at "Identifying the Issues"
... we have tried to point to related documents, rather than repeating it
here
... we need a note about sampling (and can point to Eval doc when it is
updated)
All: agree that we should include it here for now
Shawn: lets look at "Prioritizing the Repairs"
section
... Prioritize by impact and effort
Natasha: can we list the 'low hanging fruit'? If you don't know much about accessibility, then the 'impact' section is overwhelming
Shawn: partly waiting for WCAG2 - see the changelog for partial list
Judy: examples are good as provide guidance, BUT we need to get the document out - overall agree with the need for examples
Helle: need to be very careful with choice of examples
Shawn: see changelog for potential examples - http://www.w3.org/WAI/EO/Drafts/retrofit/retrofitting-changelog.html#about
All: discussion about examples
Meeting resumes after morning tea
Shawn: need to also discuss the various approaches - 'priority' vs 'priority + effort'
<scribe> ACTION: changelog - explain approach #2 'priority & effort' (and leave approach #1 off) [recorded in http://www.w3.org/2006/02/27-eo-minutes.html#action02]
shawn: lets look at "prioritizing by area/coverage" section
All: no immediate comments
Judy: "optimizing tools" section
... lets walk through from here to the end for any odd or missing things
Jack: maybe add in a sentence about retrofitting
<scribe> ACTION: changelog - add in mention about retrofitting in the intro about authoring tools [recorded in http://www.w3.org/2006/02/27-eo-minutes.html#action03]
Judy: look at "Evaluation and Repair Tools" section
All: basically ok, with a relation to retrofitting
<scribe> ACTION: changelog - add in mention about retrofitting in the intro about eval tools [recorded in http://www.w3.org/2006/02/27-eo-minutes.html#action04]
shawn: looking at headings & structure
Judy: feedback to the editor is welcome later -
alternatives to "optimizing"
... "distributing task"
Andrew: like Natasha, use a different example from 'alt text', eg 'clear links' that can often be distributed
Judy: 'validating solutions early'
<pasquale> hi from pasquale;
Hi Pasquale from EO f2f
<pasquale> hi andrew ;-)
Discussion: check your fixes before and as you implement them to ensure that they work and don't introduce new accessibility problems
judy: 'clarifying responsibilities'
Andrew: retrofitting needs to also address changes to existing material and the addition of new material
helle: needs to include this earlier on
shawn: maybe we cover this better later (next steps)
<scribe> ACTION: changelog - editors discretion to strengthen this section and relocate to a more appropriate place [recorded in http://www.w3.org/2006/02/27-eo-minutes.html#action05]
judy: "optimizing skills"
tangay: preference for second option for intro sentence
<scribe> ACTION: move "optimizing for retrofitting" above "prioritizing repairs" [recorded in http://www.w3.org/2006/02/27-eo-minutes.html#action06]
<scribe> ACTION: changelog - move "optimizing for retrofitting" above "prioritizing repairs" [recorded in http://www.w3.org/2006/02/27-eo-minutes.html#action07]
<scribe> ACTION: changelog - move "skills" above "tools" in "Optimizing for Retrofitting" [recorded in http://www.w3.org/2006/02/27-eo-minutes.html#action08]
<scribe> ACTION: changelog - remove text in [] in "optimizing skills" [recorded in http://www.w3.org/2006/02/27-eo-minutes.html#action09]
<scribe> ACTION: changelog - emphasize the need to being technical and writing and usability skills in the retrofitting team somehow [recorded in http://www.w3.org/2006/02/27-eo-minutes.html#action10]
judy: "addressing next steps"
... needs to ensure we have discussed the differences between small and large
sites
Natasha: can we reduce this section - talk about ongoing web health and just list the links without all the rationale
<AndrewA> Natasha: not sure that it speaks to an organization like HP
<AndrewA> Judy: we need to ensure that the intro is welcoming to owners of small/large sites and simple/complex sites
<AndrewA> Judy: break for lunch - resume at 13:40
judy: Meeting resumes at 13:46
Shawn: history - WAI glossary from years ago,
plus recent updates to a new, limited word, release
... requirements - http://www.w3.org/WAI/EO/changelogs/cl-lexicon
... notes - http://www.w3.org/WAI/EO/Drafts/glossary/2005-12-13#defs
Judy: QA group is interested in coordinating work on glossaries
Shawn: 'assistive technologies' term
Andrew: need the examples
Shawn: are the suggested ones ok?
All: agree
Shawn: 'equivalent alternative' term
... 'graceful transformation' term
judy" what should the term be? how is it uswd in WCAG 1.0?
Andrew: WCAG 1.0 uses "transform gracefully"
Shawn: lets use that then
... 'markup language' term
Andrew: likes the separation of semantics from presentation, but the eg probably do it for most people
All: agree with definition
Shawn: now we can take it back to ATAG for
approval
... 'real-time' event
Andrew: what about other 'real time' events, such as weather-radar?
Shawn: will they understand that it includes this? Probably
All: agree with proposed definition
Shawn: 'equivalent alternative' term
Tangay: what about "... information or functionality in a different format ..."
Shawn: what about - Information or functionality in a different format that provides the same purpose
Judy: what about - Information or functionality in a different format that provides the same purpose as the original
All: ok - shawn to reword along these lines
Shawn: what about the egs?
... change "For example, text captions provide an equivalent alternative for
an image or audio" to "For example, text provides an equivalent alternative
for images or audio"
... what about WCAG 2.0 glossary as it currently stands?
Judy: WCAG is considering EO's recent comments
All: ok for now
Judy: 'keyboard equivalent' term
... since 'emulators' look like keyboards to the application, authors do not
need to worry about all the different emulations
... also discussion about 'input device' as a term instead - but need to
concentrate on keyboards
... also 'keyboard interface' from WCAG 2.0
<scribe> ACTION: JB to recommend WCAG 2.0 include "keyboard emulator" in first sentence of the def'n of "keyboard interface" [recorded in http://www.w3.org/2006/02/27-eo-minutes.html#action11]
Judy: [live audio only & live video only]
still confusing - maybe need examples here to help clarify
... next term is "lower secondary education level"
... take a break until 1535
<scribe> ACTION: Helle to check for the origin of "keyboard equivalent" [recorded in http://www.w3.org/2006/02/27-eo-minutes.html#action12]
<scribe> ACTION: Helle to also check for different usage of the term as per UAAG & WCAG2 (and check glossary history & with task force as necessary) [recorded in http://www.w3.org/2006/02/27-eo-minutes.html#action13]
Shawn: "metadata" term
Andrew: add 'title' to examples
Shawn: what about "For example, metadata for a Web page may include title, description, language, and such."
discussion: add ... as included in the document <head> section
Judy: welcomes Dom HM (with his QA group hat)
discussion: add ... as included in the document <head> section of an HTML document
Judy: invites Dom to describe the QA glossary project
Dom: see www.w3.org/2003/glossary/ developed in
2003 with an intern in France
... brings up all uses of a term from all recommendations
<scribe> ACTION: Shawn to check back with the QA 'framework' document for approach consistency [recorded in http://www.w3.org/2006/02/27-eo-minutes.html#action14]
Dom: there is also a glossary mailing list (light traffic)
<shawn> ACTION: retrofitting changelog "edit: "affect of insufficient support" to "effect of insufficient support"" [recorded in http://www.w3.org/2006/02/27-eo-minutes.html#action15]