W3C

WCAG Weekly Telecon

12 Apr 2007

Agenda

See also: IRC log

Attendees

Present
John_Slatin, David_MacDonald, Don_Evans, Alex_Li, Michael_Cooper, Bengt_Farre, Andi_Snow_Weaver, Tim_Boland, Roberto_Ellero, Christophe_Strobbe, Loretta_Guarino_Reid, Gregg_and_Ben, Cynthia_Shelly, Katie_Haritos-Shea, Sean_Hayes, Andi_Snow-Weaver
Regrets
Bruce_Bailey
Chair
Gregg_Vanderheiden, Loretta_Guarino_Reid
Scribe
David

Contents


<Loretta> Not looking too promising for a scribe...

<bengt> 2 of them 703

<scribe> scribe: David

Announcements, Questions, and Updates

<ben> ack +1

Special Topics Survey of 12 April 2007

<Zakim> MichaelC_IAD, you wanted to say (via IRC only) my major concern with the B proposals is there aren't parallels for AA and AAA

Resolution: Accept #3 proposal as written on conformance

1283

<Zakim> MichaelC_IAD, you wanted to say (in IRC) that at L1 we should provide basic access, and at L2 look towards providing a more equivalent experience

<ben> ack ??P1

<Gregg> michael

<Zakim> MichaelC_IAD, you wanted to say I agree with movies vs books issue, but still feel it's difference between L1 and L2

<Sean> +q

Resolution: accept 1283, 1382 as proposed

Team B Survey for 5 April 2007

Resolution: Accept LC-628, LC-942, LC-1053: Level of SC 2.4.6

LC-608: captions and supplementary multi-media

Resolution: accept 608 as amended

865

<Loretta> WCAG is a set of guidelines for general use pages. WCAG 2 has been written assuming that authors can produce a single version of the content that could be made accessible to everyone, although assistive technology may be needed to transform the content into an appropriate rendering. Because of the danger of excluding people with multiple disabilities, the working group has been reluctant to...

<Loretta> We agree that there should be an activity that focuses on how to create pages just for people with learning disabilities. That is beyond the scope of WCAG itself. But we hope that related activities can develop techniques for content designed specifically for people with different cognitive, learning, and language disabilities. This would be important to determining whether we can achieve a...

<Loretta> ...require multiple versions of content targeted to different audiences. We are also concerned about the privacy issues involved in requiring people to self declare disabilities in order to get suitably tailored output. The guidelines permit alternate versions of web pages, but do not require them.

<Loretta> ...single version of content that is accessible to all, or whether multiple versions of content would be needed.

Resolution: LC-865: alternate SC for people with learning disabilities, as amended

<Loretta> We have attempted to make our processes and documents more accessible, but recognize that they have a long way to go. We have limited tools and resources and are open to specific suggestions for improvement.

LC-877: accessibility of WCAG processes

Resolution: accept 877 accessibility of WCAG processes as amended
... accept LC-878: British Standards Institute submission, as amended

LC-1085 LC-1085, LC-1237, LC-1286: Wording and level of SC 1.4.2

Resolution: accept > Topic: LC-1085 LC-1085, LC-1237, LC-1286: Wording and level of SC 1.4.2, as amended adding back in 3 seconds and moving to level 1

LC-840: General concern about Principle 3

Resolution: accept 840 (General concern about Principle 3) as amended

Advisory Technique for GL 3.1: illustrating content

<Loretta> Using images, illustrations, video, audio, or symbols to illustrate content.

Resolution: add an advisory technique for GL 3.1, Using images, illustrations, video, audio, or symbols to clarify meaning.

Advisory Technique for GL 3.1: provide examples

Resolution: accept advisory technique for for GL 3.1: provide examples

Advisory Technique for GL 3.1: justified text

Resolution: Add an advisory technique: Avoiding text that is fully justified (to both left and right margins) in a way that causes poor spacing between words or characters

Advisory Technique for GL 3.1 and SC 1.3.3: left-justified text

Resolution: Add as an advisory technique to GL 3.1 and SC 1.3.3: Using left-justified text for languages that are written left to right.

Advisory Technique for GL 3.1 and SC 1.3.3: right-justified text

Resolution: Add as an advisory technique to GL 3.1 and SC 1.3.3: Using appropriate justification for languages that are written right-to-left.

Advisory Technique for GL 3.1: column width

Resolution: Add as an advisory technique to GL 3.1: Limiting text column width.
... not accept the advisory technique to GL 3.1: Using a san-serif font
... Add as an advisory technique to GL 3.1, SC 1.4.1, SC 1.4.4: Using a light pastel background rather than a white background behind black text.
... Add as an advisory technique to GL 3.1: Highlighting a link or control when the mouse hovers over it.
... Add as an advisory technique to GL 3.1: Avoiding the use of unique interface controls unnecessarily

<Loretta> Canwe finish this survey, pick up the unanimous consent items, then stop?

<Loretta> One more question after this one on this survey.

<Christophe> The BIENE version I'm referring to says: check if upper and lower case are used according to the rules of orthography.

Resolution: Resolution: Add as an advisory technique to GL 3.1: Using upper and lower case according to the spelling rules of the text language.
... Add as an advisory technique to GL 3.1: Avoiding unusual foreign words. Note: that we will define unusual.
... accepted unanimous 1250, 1032, 1031, 1129, 528, 958, 818 as is
... accept 1247 by unanimous consent

<Loretta> Andi, I wish we had reached your proposal about AsCT.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.128 (CVS log)
$Date: 2007/04/12 23:27:13 $