<Jack> scribe: Jack

Going around the phone to do introductions with name, location, and organization being represented

Review of the WCAG 2.0 Quick Reference quide draft

Judy: Provides background of the WCAG 2.0 Quick Reference guide current version and the latest draft.
... Thanks for the comments people have already made. What general comments do people have?

Shawn: If people reply to an agenda, it is always helpful to add something to the subject line.

Henny: The title may cause people to land on the page without reading it completely.

Some feel that it takes too long to get to the substance.

Others feel it is all good and could easily add show/hid options for specific things.

<shawn> subtopic: Audience

Justin: Who is the audience?

Judy: We could take the WCAG 2 audience and make this document reflect that.

Shawn: The primary audience is web developers. Others are secondary.
... That is reflects edits that have probably not been done.

Judy: Should information be added about intended audience?

Henny: Perhaps add information about intended audience at the front of the document.

<shawn> ACTION: qui ref, note: help people who might land on this without knowing other documents -- mostly point to info elsewhere, not add much here [recorded in http://www.w3.org/2007/05/04-eo-minutes.html#action01]

Judy: What should we call it?

William: Perhaps Developer's Reference

<shawn> subtitle: title

<Zakim> shadi, you wanted to say that "reference" doesn't click with me but don't know why

William: Would let you tell the audience and get away from checklist

<Andrew> WCAG 2.0 customised checklist/guide?

<shawn> DEvelopers Guide... Developers Tool...

<judy> developers' reference

<judy> planner

<judy> implementation planner

<judy> quick reference

<Zakim> shawn, you wanted to say Al's comment

Judy: What else should title accomplish?

<shawn> shawn: some concerns with "quick"; however, a techie person said "Quick Reference" is good for developers as related to programmin languages

<judy> customized view

Justin: customized view is what we are selling as the primary focus

<shawn> developers desk reference

Shawn: talkes the existing material and adds the ability to customize

brainstorming ideas for title

<judy> customized...

title should include customizing

<judy> my wcag2 reference

My WCAG 2 reference

<judy> conformance reference

Customing WCAG 2 according to conformance claims

<Henny> customizing WCAG 2.0 based on your conformance claim

<judy> interactive reference

Interactive

Fast find reference

<judy> fast find reference

<Alan> query; criteria; view; schema

more accessible or available, easy access WCAG 2 guidelines

<judy> more accessible accessibility guidelines

<judy> streamlined reference

<judy> streamlined wcag 2.0

<judy> wcag 2.0 lite...

<judy> my daily wcag

<Alan> adaptive

<judy> desktop wcag

<judy> adaptive wcag

<shadi> [agree with shawn - "start here" kind of message]

<judy> "this is it wcag"

shawn: can look at this and if understood, don't have to follow links

my WCAG 2 fast assistant

<judy> my wcag fast assistance

<judy> my fast wcag?

<shawn> tool?

<shawn> checklist?

Henny: This is it. My WCAG @ based on my claim of conformance level

<Sylvie> customized guide on WCAG 2.0

<judy> guide

Sharon: Include the word guide in the title.

<judy> my everyday reference

<judy> my little wcag

Liam: My Little WCAG or My Little WCAG Reference

<Andrew> selection/selector

<Liam> My Everyday WCAG Reference

Sylvia: The word customize should be included in the title

Judy: The word customize or customizable may poise problems for translation

<judy> customized, planner, selector

Henny: Need a word that is a call to action such as customize or planner

<shadi> [dynamic checklist generator]

William: Customize is an important feature

<judy> advanced search

<Liam> bespoke, pick-your-own

<judy> simple search

Alan:

<Liam> tailored

Roll Your Own

Tailored

<Liam> 'customisable' is an ugly word though...

Interactive

Sharron: Doesn't the word 'My" suggest customizable

Andrew: Favors the word customizable

Judy: Need 3 parts - customizable or my upfront, WCAG 2, and tool or reference

<shawn> Customizable WCAG Checklist

<Andrew> guide

<Andrew> Customizable WCAG Guide

<shawn> first word: My|Customizable|Interactive

<shawn> second word: WCAG 2.0

<shawn> third word: ?

Jack: My WCAG 2 Customizable Tool

<Liam> WCAG 2 Fast Look-up

Judy: Customizable WCAG Tool

<Liam> WCAG 2.0 Hammer Drill

<Andrew> third word: guide/reference/selection/tool/look-up/criteria

Power Tool

<shawn> WCAG 2.0 Power Tool

My WCAG Power Tool

<shawn> The Guts of WCAG 2.0

The only tool quality is that only has the one feature of being customizable

Basic

My site my WCAG

<judy> customizable wcag checklist

Customizable WCAG Checklist

<shawn> shawn: this is the summary of *all* the WCAg info

<shawn> scribe: Liam

Judy: now looking at the organisation of the doc, not the title.

Henny: chunky at the start, heading doesn't tell you what it is
... might be worth having an initial landing page to do the customisation, then output a customisable form
... useful to have it in a table to chek things as pass/fail

<shawn> ACTION: qui ref, note: most people will print this off -- consider putting intro material separate [recorded in http://www.w3.org/2007/05/04-eo-minutes.html#action02]

Note that the ouput should be a referenceable URL

for bookmarking...

Andrew: separate results from what's it all about
... TOC should follow the custom selections

<shawn> ACTION: qui ref, note: put selections before TOC. [recorded in http://www.w3.org/2007/05/04-eo-minutes.html#action03]

Sylvie: selection and deselection of different buttons - not sure it's working properly. Deselecting priority 3 still displays all 3 priorities.
... having 2 checkboxes is confusing

<shawn> ACTION: qui ref, note: clarify the subcheckboxes [recorded in http://www.w3.org/2007/05/04-eo-minutes.html#action04]

Sylvie: unchecking scripting produces...

removal of next checkbox. This is confusing.

Sylvie: you have twice the text explaining what you have selected -- once beofre the form and once after.

<shawn> ACTION: qui ref, note: "Save Settings" should be button? (Sylvie) [recorded in http://www.w3.org/2007/05/04-eo-minutes.html#action05]

Alan: dynamic (another descriptor)
... 'display only those tech' doesn't work well... maybe display only SC relating to...

<shawn> Alan's comments in email: http://lists.w3.org/Archives/Public/w3c-wai-eo/2007AprJun/0030.html

<shawn> Sylvie's comments in email: http://lists.w3.org/Archives/Public/w3c-wai-eo/2007AprJun/0033.html

<shawn> Andrew's comments in email: http://lists.w3.org/Archives/Public/w3c-wai-eo/2007AprJun/0032.html

William: option to remove introduction would be good

<shawn> Henny's comments in email: http://lists.w3.org/Archives/Public/w3c-wai-eo/2007AprJun/0029.html & http://lists.w3.org/Archives/Public/w3c-wai-eo/2007AprJun/0034.html

Doyle: Build up from a simple start

Andrew: agree that building up is a good idea (as this is aimed at semi-experts)

Terse but expandable

<shawn> ACTION: qui ref, note: ability to turn off the intro stuff with a checkbox ? and maybe even at each SC be able to turn on or off the techniques. [recorded in http://www.w3.org/2007/05/04-eo-minutes.html#action06]

Would be good to be able to use it as a super-terse checklist with areas that can be expanded.

<judy> (my customizable wcag reference...)

<Harvey> We have to get to the third paragraph to find out the first link to what WCAG means [link to WDCAG 2.0]

Justin: Good to be able to tell it not to show as many 'first time user' prompts as possible

Shadi: WCAG checklist generator

<judy> (wcag checklist generator)

<shawn> [My WCAG Generator]

Liam likes Shadi's idea

Judy: now discussing tagline: A summary of all WCAG 2.0 requirements (success criteria) and techniques sufficient to meet them (using HTML, and any combination of CSS, Multimedia, and Scripts.)

Andrew: Ditch the content in brackets

William: it doesn't mention the key point that it's customisable

Shawn: subtitle is trying to be specific that it isn;t all-inclusive and that there may be other vesrions developed that cover other technologies.

<Harvey> I note that there is no mention of XML; the basis of the Digital Talking Book effortk e

General: it's long.

Justin: get rid of the TOC if its a checklist

Henny: Agrees. Jettison TOC.

William: suggests Hide/unhide

Andrew: TOC is useful but should follow, not precede, the customise form.

Judy: Document status could go in footer.

Sylvie: Agrees with Andrew

<shawn> ACTION: qui ref, note: move TOC after customization & allow show/hide [recorded in http://www.w3.org/2007/05/04-eo-minutes.html#action07]

Liam agrees with Justin

Judy: now discussing 'customising this quick reference'

William: more fanfare for customisation process

<Zakim> Liam, you wanted to note feedback at Internet World

<shawn> shawn: Need to link to description of "is relied upon" clearly

Justin and emails: 'CSS is not relied upon' not clear.

William: clarify that unchecking CSS does not equal checking CSS is not relied upon

<shawn> ACTION: qui ref, note: first label: CSS is used... idea for "relied upon" > "My users will need CSS" [recorded in http://www.w3.org/2007/05/04-eo-minutes.html#action08]

Liam: 'my users will need CSS' 'my users benefit from but not need CSS' 'my users will not use CSS'

primary audience will know what a cookie is

Shawn: remove 'save settings' and just place it as a button.

<shawn> ACTION: qui ref, note: "This Quick Reference is currently customized to include:" not needed. Maybe Save Settings it button (Sylvie) [recorded in http://www.w3.org/2007/05/04-eo-minutes.html#action09]

<Andrew> liam: wants a show/hide the show/hide options - and Andrew concurs

Andrew: show/hide the intro

Judy: a lot of this should go into a disclaimer section

<shawn> ACTION: qui ref, note: keep in mind primary users will probably use this a lot and don't want to wade through stuff. Have other stuff either on separate "page" or make all hideable. [recorded in http://www.w3.org/2007/05/04-eo-minutes.html#action10]

general: remove redundancies

Liam: move to footer anything that can be

<shawn> ACTION: qui ref, note: "Introduction" - eliminate redundancy, cut out what not needed here, point to elsewhere. Move to top. (also with show/hide) [recorded in http://www.w3.org/2007/05/04-eo-minutes.html#action11]

Justin: are we covering the user interface?

Shawn: yes.

Liam: collapse everything right down to guidelines. Can expand individual branches.

General approbation. Shawn waves a flag.

Shawn: May not be do-able immediately but if done well could solve other problems.

<shawn> ACTION: qui ref, note: addition of Advisory & Failures make this much longer. Ability to turn this off, as well as Sufficient... Request to have the entire thing collapsable, then can expand individual nodes. (*strong* support all around) [recorded in http://www.w3.org/2007/05/04-eo-minutes.html#action12]

Justin: not highly usable at present.

Liam: re expand/collapse nodes, should remember state via cookie.

William: provide short form for each SC?

Justin: makes it easier to run as a checklist when you're used to it.

<shawn> ACTION: qui ref, note: perhaps make handles/shortname prominent, then the full text less -- to make skimming easier & feel more simple [recorded in http://www.w3.org/2007/05/04-eo-minutes.html#action13]

Justin: good to be able to use as checklist

Liam: strongly agrees

<shawn> ACTION: qui ref, note: rethink facilitating using this as a checklist... [recorded in http://www.w3.org/2007/05/04-eo-minutes.html#action14]

<judy> wcag checklist generation

<judy> dynamic checklist generator

<judy> wcag 2 dynamic checklist

<shawn> dynamic checklist superhero !

<shawn> * Liam Dynamic Checklist brought to you by... CAPTAAAAAIN WCAAAAAG!!!

Harvey: need WCAG simple acronym expansion

<shawn> ACTION: qui ref, note: acronym expansion at first reference, link to Overview up top [recorded in http://www.w3.org/2007/05/04-eo-minutes.html#action15]

<shawn> http://www.w3.org/WAI/EO/2003/template.html

This is scribe.perl Revision: 1.128  of Date: 2007/02/23 21:38:13  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/Perhaps make the primary audience web developers./The primary audience is web developers. Others are secondary./
Succeeded: s/Andrew: The document refers to web unit. Is that correct.//
Succeeded: s/Sharon/Sharron/
Succeeded: s/ability to turn off the intro stuff with a checkbox ?/ability to turn off the intro stuff with a checkbox ? and maybe even at each SC be able to turn on or off the techniques./
Succeeded: s/Harvey:/Justin:/
Found Scribe: Jack
Inferring ScribeNick: Jack
Found Scribe: Liam
Inferring ScribeNick: Liam
Scribes: Jack, Liam
ScribeNicks: Jack, Liam
Present: doyle Shawn Alan Judy Sharron Henny_Swan Jack Liam_McGee Andrew Sylvie_Duchateau Shadi Loughborough Harvey Justin
Regrets: Wayne
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-eo/2007AprJun/0028.html
Got date from IRC log name: 4 May 2007
Guessing minutes URL: http://www.w3.org/2007/05/04-eo-minutes.html
People with action items: - ability acronym addition advisory at currently customized cut eliminate expansion failures first here introduction is link longer. make much needed not note of out point qui quick redundancy ref reference this what

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