<andrew> scribe nick: wayne

<scribe> scribe: wayne

Status of EO comments on WCAG 2.0

Shawn: [Queried the group regarding individual comments and comments from EO]

Each member gave personal status on 2.0 comments. If members do not have changes to report, then reporting that fact to WBS would be helpful.

Accessibility-Supporting Technologies

Shawn: Accessibility-Supported is a descriptor. EO agrees this is a descriptor, but thinks the term should be accessibility supporting.

William: The group discussed this and many arguments were in the minutes.

Wayne: Will write up the group logic regarding this change.

Quick Reference

Shawn: Consider thtle change "How to Meet WCAG 2.0".

<shawn> "How to Meet WCAG 2.0: A customizable list of WCAG 2.0 requirements (Success Criteria) and techniques"

Liam: Agrees, wanted to see a conflict with requirements document...

<shawn> Wayne: How to IMplement WCAG 2.0

Liam: question "How to meet..." why doesn't WCAG 2.0 tell us how to meet it?

Justin: This implies that it is a tutorial.

<andrew> Andrew: what about just "Meeting Wcag 2.0: ...."

Liam: this is a tutorial... web based.

Shawn: the subtitle really differientates this from a guided tutorial.

Lisa: The customizability is important.

Shawn: Suggested introduction text...

<shawn> http://www.w3.org/WAI/WCAG20/quickref/

william: Understanding and Techniques are different documents.

<achuter> ack

<Zakim> achuter, you wanted to say that it should start by explaining that there is a set of related documents

Alan: this is organized by Tecniques and Understanding.

William: Topic sentence: you can customize the list and here is how...

<Zakim> Liam, you wanted to suggest a couple of simplifications

Liam: The last paragraph unwrapt the information and makes it understandable... not exact quote..

<shawn> http://www.w3.org/WAI/WCAG20/quickref

Shawn: Can you go directly to Quick Reference and then look at the four technical paragraphs that have to do with informative and other stuff....

Liam: This is appendix stuff not introduction.

<shawn> <p>

<shawn> This WCAG 2.0 Quick Reference lists all of the requirements (called "success criteria") from the latest _Web Content Accessibility Guidelines (WCAG) 2.0 Working Draft_. It also lists techniques to meet the requirements, and "Understanding" links to descriptions, examples, and resources. You can customize the list for your specific situation by selecting which technologies you are using in your Web project, and the _levels_ and techniques that you want included in the

<shawn> <p>

<shawn> See the _Overview of WCAG 2.0 Documents_ for an introduction to WCAG 2.0 and supporting documents, including more information about this Quick Reference.

<shawn> <p>

<shawn> Note that all techniques are informative; that is, you don�t have to follow them. <strong>Please see the _�Sufficient and Advisory Techniques� section of Introduction to Understanding WCAG 2.0_ for important information about the techniques.</strong>

<shawn> </p>

Shawn: Proposes replacing the 4 paragraphs with the single sentence above.

<shawn> The "sufficient techniques" listed below are considered sufficient by the WCAG Working Group to meet the success criteria.

<shawn> The "sufficient techniques" listed below are considered sufficient to meet the success criteria.

<shawn> The "sufficient techniques" listed below are considered sufficient to satisfy the success criteria.

Summary: Recommendation of Andrew. See Action below.

William: First time users will not understand the customizing box.

<andrew> ACTION: Quick Ref - split our proposed into replacement into two submissions [recorded in http://www.w3.org/2008/01/25-eo-minutes.html#action01]

Andrew: We may not want first time users customizing.

<andrew> ACTION: Quick Ref - pt2 - suggest they tighten up the last 2 paras, with our very short para as an extreme suggestion [recorded in http://www.w3.org/2008/01/25-eo-minutes.html#action02]

This is scribe.perl Revision: 1.133  of Date: 2008/01/18 18:48:51  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/sugegstion/suggestion/
Found Scribe: wayne
Inferring ScribeNick: Wayne
Default Present: doyle, Wayne_Dick, Loughborough, +1.919.523.aaaa, achuter, shawn, lisa, andrew, Liam, Justin
Present: doyle Wayne_Dick Loughborough +1.919.523.aaaa achuter shawn lisa andrew Liam Justin

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 25 Jan 2008
Guessing minutes URL: http://www.w3.org/2008/01/25-eo-minutes.html
People with action items: quick

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