W3C home > Mailing lists > Public > w3c-wai-au@w3.org > April to June 2011

Minutes from AUWG Teleconference on 13 June 2011 4:00pm-5pm ET

From: Richards, Jan <jrichards@ocad.ca>
Date: Mon, 13 Jun 2011 17:12:09 -0400
To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <F2C77FB59A1A4840A01EF5F59B1826E20A3F3B4D70@ocadmail.ocad.ca>
http://www.w3.org/2011/06/13-au-minutes.html

WAI AU
13 Jun 2011

Agenda

See also: IRC log
Attendees

Present
    Jeanne, Alex, Jan, +1.571.765.aaaa, Greg, Jutta, +1.561.200.aabb, Sueann, Tim_Boland
Regrets
    Cherie_E., Allessandro_M.
Chair
    Jutta Treviranus
Scribe
    Jan

Contents

    Topics
        1. The survey for reviewing the AA comments
        B.2.5 - GL41
        B.3.2 - WCAGWG27
        B.3.2 - MS57
        B.3.2 - MS58
        B.3.2 - GL19
        B.3.2 - OC31
        B.3.4 - MS59
    Summary of Action Items

<scribe> Scribe: Jan
1. The survey for reviewing the AA comments
B.2.5 - GL41

JR: Has a proposal
B.3.2 - WCAGWG27

Resolution: Accept response to B.3.2 - WCAGWG27
B.3.2 - MS57

JT: B.3.2.4 At Least as Prominent: Accessible content support features are at least as prominent as features related to other types of web content problems (e.g., invalid markup, syntax errors, spelling and grammar errors).
... B.3.2.4 At Least as Prominent: Accessible content support features are at least as prominent as features related to other types of web content problems (i.e., invalid markup, syntax errors, spelling and grammar errors).
... B.3.2.4 At Least as Prominent: Accessible content support features are at least as prominent as features related to either invalid markup, syntax errors, spelling or grammar errors.

Resolution: Accept new wording " B.3.2.4 At Least as Prominent: Accessible content support features are at least as prominent as features related to either invalid markup, syntax errors, spelling or grammar errors."

<scribe> ACTION: JR to Change wording to resolved for B.3.2.4 [recorded in http://www.w3.org/2011/06/13-au-minutes.html#action01]

<trackbot> Created ACTION-347 - Change wording to resolved for B.3.2.4 [on Jan Richards - due 2011-06-20].
B.3.2 - MS58

AL: Resolved above.
B.3.2 - GL19

Resolution: Accept response to B.3.2 - GL19
B.3.2 - OC31

JR: Resolved above.
B.3.4 - MS59

1. Explain use of "range"

<scribe> NEW DEFINITON: "Range":

More than one item within a set that is also more than one item. See also "Range" in the (informative) Introduction.

<scribe> NEW SECTION IN THE (INFORMATIVE) INTRODUCTION:

ATAG 2.0 uses the term "range" in several success criteria in which absolute measurements may not be practical (e.g. the set of all help documentation examples, the set of all templates, etc.). While the strict testable requirement is the definition "More than one item within a set that is also more than one item", implementers are strongly encouraged to implement the success criteria more widely.

OLDER VERSION

<scribe> NEW DEFINITON: "Range":

More than one item within a multi-item set.

(Informative) Note: ATAG 2.0 uses the term "range" in several success criteria in which absolute measurements may not be practical (e.g. the set of all help documentation examples, the set of all templates, etc.). While the strict testable requirement is the definition "More than one item within a multi-item set ", implementers are strongly encouraged to implement the success criteria more...

scribe: broadly.

source: http://lists.w3.org/Archives/Public/w3c-wai-au/2011AprJun/0061.html

JT: But it would be just as a unacceptable to show inaccessible step as bad xyntax in example

GP: But it could be a different point in timeline

JT: Right, so then examples of breaking accessibility at publishing

GP: How do you test that?

JT: Test what?

GP: How do you know you've done that...lots of actions having to do with images....at some point you need accessibility demonstrated other times not important
... Sampling wouldn't work...

JT: Not suggesting sampling
... Proposing to turn it around and to say don't do harm

JR: So the class of documentation at the end

JT: Or some things that heppen in the middle...like images of text in some context

<scribe> ACTION: JR to attempt to propose text taking into account context of inaccessible examples and testing practicality. [recorded in http://www.w3.org/2011/06/13-au-minutes.html#action02]

<trackbot> Created ACTION-348 - Attempt to propose text taking into account context of inaccessible examples and testing practicality. [on Jan Richards - due 2011-06-20].
Summary of Action Items
[NEW] ACTION: JR to attempt to propose text taking into account context of inaccessible examples and testing practicality. [recorded in http://www.w3.org/2011/06/13-au-minutes.html#action02]
[NEW] ACTION: JR to Change wording to resolved for B.3.2.4 [recorded in http://www.w3.org/2011/06/13-au-minutes.html#action01]


-- 
(Mr) Jan Richards, M.Sc.
jrichards@ocad.ca | 416-977-6000 ext. 3957 | fax: 416-977-9844
Inclusive Design Research Centre (IDRC) | http://idrc.ocad.ca/
Faculty of Design | OCAD University
Received on Monday, 13 June 2011 21:12:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 13 June 2011 21:12:16 GMT