W3C

- DRAFT -

EOW2 Task Force

23 Oct 2006

Agenda

See also: IRC log

Attendees

Present
William, Ben, Henny, Shawn
Regrets
Andrew
Chair
shawn
Scribe
shawn

Contents


 

zaki, with will be eow2

Transitioning Web Sites from WCAG 1.0 to WCAG 2.0

hum...

william: good, focused content, or target for audience

ben: good. some details may change with changes in WCAG 2.0

<scribe> ACTION: changelog, under approach, add a new doc (under first one, so new #2) Benefits of Transitioning from WCAG 2.0 from WCAG 1.0 -- and note that it might be its own doc, or combined with "How WCAG 2.0 Compares to WCAG 1.0" [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action01]

<scribe> ACTION: changelog: consider changing "Key steps for transitioning from WCAG 1.0 to 2.0" to something warm and friendly and encouraging, "You Can Do It" perhaps "Perspectives"... [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action02]

note: most WAi docs have <h2 right after <h1, and many are "introduction

exception: http://www.w3.org/WAI/intro/components.php

<scribe> ACTION: changelog: add link to (new) Benefits doc [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action03]

<scribe> ACTION: changelog: when get to worswmithing, try to cut down 10-20% ot more :) [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action04]

<scribe> ACTION: changelog: under "1. Learn the Basic Difference" change the 4 bullets to just a simple list, something like: "Key differrences include, baseline, conformance, and some technical requirements." [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action05]

<scribe> ACTION: changelog: edit first paragraph under "Clarify Your Baseline and Conformance Goals" since many readers' organizations' don't have accessibility policies [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action06]

<scribe> ACTION: changelog: remove <h3 Accessibility Policies, as this is tangential for most readers. Consider what you would say *if* we had "Transitioning Web Accessibility Policies from WCAG 1.0 to WCAG 2.0" doc done. THEn consider if want to put a little in here now, until that doc is done. [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action07]

<scribe> ACTION: changelog: change: "The Baselines defines what technologies will be supported in your Web site(s)." to "Baseline [1 sentence evelvator pitch goes here]." [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action08]

<scribe> ACTION: changelog: move the steps under "Baseline" to changelog, in new "Archives" section. [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action09]

<scribe> ACTION: changelog: under "Baseline" add note before steps, something like "<em>[this will be revised after About Baselines in WCAG 2.0 is updated] [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action10]

<scribe> ACTION: changelog: delete paragraph under "WCAG 2.0 Conformance scheme" [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action11]

<scribe> ACTION: changelog: under "Conformance" add note before steps, something like "<em>[these steps will be revised after Conformance WCAG 2.0 is updated] [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action12]

<scribe> ACTION: changelog: under "Baseline" and "Conformance", tweak the steps [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action13]

<scribe> ACTION: changelog: leave just "requirements" in the headings. right after resources, add a sentence (probably in a paragrpah by itself so it stadns out), something like: WCAG 1.0 requirements were in Checkpoints, and WCAG 2.0 requirements are in Success Criteria. [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action14]

<scribe> ACTION: changelog for the OVERVIEW/"How WCAG 2.0 Drafts Differ from WCAG 1.0", consider including the principles themselves [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action15]

<scribe> ACTION: changelog: under 3.1, add something like "Note that there are requirements in WCAG 1.0 that are no longer requirements in WCAG 2.0" [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action16]

<scribe> ACTION: changelog: under 3.1, 3rd bullet: edit to clarify "that you site didn't meet" in WCAG 1.0 that they can meet in WCAG 2.0 [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action17]

http://www.w3.org/TR/WCAG20/appendixD.html

<scribe> ACTION: changelog: try for different example under "Which new WCAG 2.0 Success Criteria are already implemented in your existing site?" prefer Level 2, perhaps 1.3.5 Information required to understand and operate content does not rely on shape, size, visual location, or orientation of components. (Level 2) [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action18]

<scribe> ACTION: changelog: include all in the linked text: ""Prioritizing the Repairs" section of Improving the Accessibility of Your Web Site." [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action19]

<scribe> ACTION: changelog: consider changing "tes the site against WCAG 2.0" to soemthing like "Evaluate how your current site meets WCAG 2.0" [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action20]

<scribe> ACTION: changelog: also link to http://www.w3.org/WAI/impl/improving.html#eval [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action21]

<scribe> ACTION: changelog: delete <h2 5. Update any Internal Guidance, and integrate the idea below [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action22]

<scribe> ACTION: changelog: consider at the end adding something like "when technicaues are updated, Wai will announce at home page & IG mailing list. to subscribe..." from the end of http://www.w3.org/WAI/intro/w3c-process [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action23]

cation: changelog: add <h2 s under Page Contents

<scribe> ACTION: changelog: add <h2 s under Page Contents [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action24]

Summary of Action Items

[NEW] ACTION: changelog for the OVERVIEW/"How WCAG 2.0 Drafts Differ from WCAG 1.0", consider including the principles themselves [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action15]
[NEW] ACTION: changelog, under approach, add a new doc (under first one, so new #2) Benefits of Transitioning from WCAG 2.0 from WCAG 1.0 -- and note that it might be its own doc, or combined with "How WCAG 2.0 Compares to WCAG 1.0" [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action01]
[NEW] ACTION: changelog: add

http://www.w3.org/2006/10/23-eow2-minutes.html#action24]
[NEW] ACTION: changelog: add link to (new) Benefits doc [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action03]
[NEW] ACTION: changelog: also link to http://www.w3.org/WAI/impl/improving.html#eval [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action21]
[NEW] ACTION: changelog: change: "The Baselines defines what technologies will be supported in your Web site(s)." to "Baseline [1 sentence evelvator pitch goes here]." [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action08]
[NEW] ACTION: changelog: consider at the end adding something like "when technicaues are updated, Wai will announce at home page & IG mailing list. to subscribe..." from the end of http://www.w3.org/WAI/intro/w3c-process [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action23]
[NEW] ACTION: changelog: consider changing "Key steps for transitioning from WCAG 1.0 to 2.0" to something warm and friendly and encouraging, "You Can Do It" perhaps "Perspectives"... [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action02]
[NEW] ACTION: changelog: consider changing "tes the site against WCAG 2.0" to soemthing like "Evaluate how your current site meets WCAG 2.0" [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action20]
[NEW] ACTION: changelog: delete

http://www.w3.org/2006/10/23-eow2-minutes.html#action22]
[NEW] ACTION: changelog: delete paragraph under "WCAG 2.0 Conformance scheme" [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action11]
[NEW] ACTION: changelog: edit first paragraph under "Clarify Your Baseline and Conformance Goals" since many readers' organizations' don't have accessibility policies [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action06]
[NEW] ACTION: changelog: include all in the linked text: ""Prioritizing the Repairs" section of Improving the Accessibility of Your Web Site." [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action19]
[NEW] ACTION: changelog: leave just "requirements" in the headings. right after resources, add a sentence (probably in a paragrpah by itself so it stadns out), something like: WCAG 1.0 requirements were in Checkpoints, and WCAG 2.0 requirements are in Success Criteria. [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action14]
[NEW] ACTION: changelog: move the steps under "Baseline" to changelog, in new "Archives" section. [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action09]
[NEW] ACTION: changelog: remove

http://www.w3.org/2006/10/23-eow2-minutes.html#action07]
[NEW] ACTION: changelog: try for different example under "Which new WCAG 2.0 Success Criteria are already implemented in your existing site?" prefer Level 2, perhaps 1.3.5 Information required to understand and operate content does not rely on shape, size, visual location, or orientation of components. (Level 2) [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action18]
[NEW] ACTION: changelog: under "1. Learn the Basic Difference" change the 4 bullets to just a simple list, something like: "Key differrences include, baseline, conformance, and some technical requirements." [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action05]
[NEW] ACTION: changelog: under "Baseline" add note before steps, something like "[this will be revised after About Baselines in WCAG 2.0 is updated] [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action10]
[NEW] ACTION: changelog: under "Baseline" and "Conformance", tweak the steps [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action13]
[NEW] ACTION: changelog: under "Conformance" add note before steps, something like "
[these steps will be revised after Conformance WCAG 2.0 is updated] [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action12]
[NEW] ACTION: changelog: under 3.1, 3rd bullet: edit to clarify "that you site didn't meet" in WCAG 1.0 that they can meet in WCAG 2.0 [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action17]
[NEW] ACTION: changelog: under 3.1, add something like "Note that there are requirements in WCAG 1.0 that are no longer requirements in WCAG 2.0" [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action16]
[NEW] ACTION: changelog: when get to worswmithing, try to cut down 10-20% ot more :) [recorded in http://www.w3.org/2006/10/23-eow2-minutes.html#action04]
 
[End of minutes]


Minutes formatted by David Booth's scribe.perl version 1.127 (CVS log)
$Date: 2006/10/23 23:30:28 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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)

Succeeded: s/>[this will be revised/>[these steps will be revised/
No ScribeNick specified.  Guessing ScribeNick: shawn
Inferring Scribes: shawn

WARNING: Replacing list of attendees.
Old list: [IPcaller]
New list: Loughborough Shawn Ben Henny

Default Present: Loughborough, Shawn, Ben, Henny
Present: William Ben Henny Shawn
Regrets: Andrew
Agenda: http://lists.w3.org/Archives/Public/public-wai-eo-wcag2tf/2006Oct/0006.html
Got date from IRC log name: 23 Oct 2006
Guessing minutes URL: http://www.w3.org/2006/10/23-eow2-minutes.html
People with action items: 1.0 3.1 3rd accessibility add also as bullet changelog changing consider edit for from get h3 had if is key link most policies readers. remove say steps tangential this transitioning under wcag we web what when would you

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]