Group: Accepts the EO deliverables
<shawn> http://www.w3.org/WAI/intro/wcag20-new
Shawn: The overview document has more of an
introductory approach.
... address the feedback that WCAG 2.0 is hard to understand; there is too
much information; sift the technical report document; communicate what we are
doing;
... Focus on the second section; different WCAG 2.0 Documents
Judy: Is it too long? Is it too formal?
Shawn: From audience: the primary audience is
beginners; the goal is to be short and readable; use plain language.
... What do people feel about contractions.
<Zakim> shawn, you wanted to ask about contractions (It is > It's)
Harvey: prefers it is to it's.
Judy: Perhaps contractions are too informal. We want something between.
<shawn> Alan: [against contractions]
Alan: The reference to success criteria is not
clear, but not what the effect of them will be.
... How will the success criteria effect people.
<shawn> ACTION, shawn: CHANGELOG Overview: new Baseline wording (w/o author assumes)
<shawn> ACTION: shawn, CHANGELOG Overview: new Baseline wording (w/o author assumes) [recorded in http://www.w3.org/2006/06/30-eo-minutes.html#action01]
<shawn> ACTION: shawn, CHANGELOG Overview: look at less formal wording [recorded in http://www.w3.org/2006/06/30-eo-minutes.html#action02]
Alan: To make shorter: planned changes and additions... Is it need to know?
shawn: The things listed here are definite
actions..
... Overall approach; how does it work or not work?
Alan: Apply to more advance web technologies...
use of term... not clear. do they mean non-W3C technology...
... Do not want to imply that non-W3C are less advanced...
Shawn: Following the link does imply that concern...
<Alan> (Alan leaving call now...)
Judy: Move from passive voice to active voice.
More illustration.
... Shift from first to second paragraph is jarring. Seems to jump from
informal to very formal.
<judy> jb clarification: 1st paragraph sounds formal & could be more informal/warmer. 2nd paragraph doesn't seem needed here.
Judy: "Currently the best place to start
working with…" implies that the standard is accepted…
... Navigating WCAG 2.0… finds troubling… How 2.0 differs from
1.0… break robust into plain language…
Shawn: Please send comments by Tuesday for inclusion.
Group: Judy, Doyle and Wayne will send comments to Shawn.
<judy> [jb comes up w/ more language-tone suggestion: instead of "this page introduces" how about "this page will give you"
<judy> e.g."this page will give you an overview of wcag 2.0 and its supporting documents, and highlight some differences between..."
Shawn: In sending comments include reason for difficulty and suggested change. Both rationale and wording are helpful.
Judy: Get user materials written; we need a task force to get this moving. The document is a normal list of charges, time co User Materials Task Force com User Materials Task Force commitment, goals,… The objectives section attempts to identify the kind of materials covered. Initial work: setting priorities, scope and focus.
<shawn> wwoooo +1 to Liam's idea!!!
<shawn> Liam: write a doc like "Accessibility on this Site" that sites can point to. That is, if they meet guidelines, then these things will work. e.g., Headings
<shawn> Judy: we already have, somewhat related: http://www.w3.org/WAI/changedesign
Liam: Suggestions for other objectives: Low expectations of users; about accessibility on pages; What users can expect;
Judy: 2) gives marked up heading; 3) what can people expect;
Liam: This complies with standard x and so you can expect y.
<Andrew> Andrew: see also the BBC's "my web, my way" (http://www.bbc.co.uk/accessibility/) for ways to use your computer
<Henny> agreed. not only useful ideas to support the user but if explained on the WAI conformance pages it may prevent erroneous claims of conformance by site owners/authors
Andrew: Likes a ticket/marker with expectation. Again improves accessibility accountability.
<shawn> here's one that I did for text scaling a long time ago: http://www.uiaccess.com/notice-1.html
<Liam> Here is a brief and elderly one on the Communis web site: http://www.communis.co.uk/accessibility.html
<shawn> (note that was before common browsers overrode absolute text sizes)
Judy: On complaints.
Doyle: Like regulatory nature.
<Liam> That should have read brief and elderly.
<Andrew> here's a complaints process from an Australia university: http://www.swin.edu.au/accessibility_policy.htm
<Liam> Extending notes on expectations deliverable: needs to give info on AT, OS and browser capabilities, should be the destination of the existing WAI buttons
<Liam> ...such as http://www.w3.org/WAI/WCAG1AAA-Conformance
Judy and William: Peer expertise development…Networking…
Shawn: 7 July
<Andrew> attend
Attend
<Henny> Attend
<Liam> Attend
<Andrew> doyle - attend
<Harvey> no schedule problems
<Andrew> sylvie - attend
<Liam> Sylvie - attend
Shawn: 14 july
<shawn> wl: attend
<Andrew> regrets
wayne: attend
<judy> regrets (icchp)
<Henny> Possible regrets
Doyle: Attend
Sylvie: regrets
<Harvey> attend
<Liam> attend
<shadi> regrets
<Andrew> regrets (icchp)
<shadi> (ICCHP)
Shawn: July 21
<shadi> attend
<Andrew> regrets (holiday)
Doyle: Attend
<judy> attend
Sylvie: Attend
<Harvey> OK
<Liam> attend
Attend
<shawn> wl: attend
<Henny> Attend
<Andrew> sylvie - attend
Shawn: 28 July
<Henny> Attend
<Harvey> ok
regrets
<Andrew> attend
<Liam> hope to attend
<shawn> wl: attend
<shawn> ds: attend
<shadi> attend
<shawn> sylvie: attend
Shawn: 4 August
<shadi> attend
<Andrew> attend
regrets
<shawn> wl: attend
<Harvey> attend
<Liam> regrets
<shawn> ds: attend
<shawn> sylvie: regrets
<Henny> Regrets
Shawn: 11 August
<Andrew> attend
<Liam> regrets
<shawn> sylvie: regrets
attend
<shawn> ds: attend
<Henny> Regrets
<Harvey> attend
<shawn> wl: attend
<shadi> probable regrets
Shawn: 18 August
<Liam> possible regrets
<shadi> probable regrets
attend
<Andrew> attend
<Harvey> attende
<shawn> sylvie: regrets
<Henny> Attend
<shawn> wl: attend
<shawn> ds: attend
Shawn: 25 August
<Andrew> attend
attend
<Harvey> attend
<shawn> ds: attend
<shawn> wl: attend
<shawn> sylvie: attend
<Henny> Attend
<Liam> clueless
<shadi> possible attend
Shawn: 1 September
attend
<shadi> possible attend
<Andrew> umm
<Henny> Attend
<shawn> sylvie: attend
<Liam> still clueless
sylvie: attend
<Harvey> who knows
doyle: attend
<shawn> ds: attend
<Andrew> probably attend
<shawn> wl: attend
<Henny> correction, possible regrets