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

Minutes from AUWG Teleconference on 7 March 2011 4:00pm-5pm ET and Survey

From: Richards, Jan <jrichards@ocad.ca>
Date: Mon, 7 Mar 2011 17:09:58 -0500
To: AUWG <w3c-wai-au@w3.org>
Message-ID: <F2C77FB59A1A4840A01EF5F59B1826E20A3C934D95@ocadmail.ocad.ca>
http://www.w3.org/2011/03/07-au-minutes.html


WAI AU
07 Mar 2011

Agenda

See also: IRC log
Attendees

Present
    Jeanne, Jan, AleMiele, Tim_Boland, Jutta, Sueann, Greg
Regrets
    Cherie, AndrewR, AlastairC
Chair
    Jutta Treviranus
Scribe
    Jan

Contents

    * Topics
         1. Survey
         2. Definition of author
         3. Definition of authoring tool
         4. Wording of B.1.1.2 Content Auto-Generation During Authoring Sessions
         5. 2. B.2.1.1 Accessible Content Possible (WCAG) Proposal
         6. 3. Series of long-waiting non-normative (and hopefully minor) edits marked with a single "@":
         7. Implementing Success Criterion B.1.2.1 Restructuring and Recoding Transformations (WCAG)
    * Summary of Action Items

zaki, code?
Survey

http://www.w3.org/2002/09/wbs/35520/20110302z/results

<scribe> Scribe: Jan
Definition of author

http://www.w3.org/2002/09/wbs/35520/20110302z/results#xq5

Resolution: All accept "People who use authoring tools to create or modify web content. The term may cover roles such as content authors, designers, programmers, publishers, testers, etc. (see also "Part B Conformance Applicability Note #6: Multiple author roles"). Some authoring tools control who may be an author by managing *author permissions*. "
Definition of authoring tool

http://www.w3.org/2002/09/wbs/35520/20110302z/results#xq7

Resolution: All accept the new definition.
Wording of B.1.1.2 Content Auto-Generation During Authoring Sessions

http://www.w3.org/2002/09/wbs/35520/20110302z/results#xq9

@@B.1.1.2 Content Auto-Generation During Authoring Sessions (WCAG): Authors have the default option that, when web content is automatically generated during an authoring session, then one of the following is true: [Implementing B.1.1.2]

Note 1: Automatic generation includes automatically selecting templates for authors.

Note 2: This success criterion applies only to automatic processes specified by the authoring tool developer. It does not apply when author actions prevent generation of accessible web content.

(a) Accessible: The content is accessible web content (WCAG) without author input; or (b) Prompting: During the automatic generation process, authors are prompted for any required accessibility information (WCAG); or (c) Automatic Checking: After the automatic generation process, accessibility checking is automatically performed; or (d) Checking Suggested: After the automatic generation...

scribe: process, the authoring tool prompts authors to perform accessibility checking. The WCAG 2.0 Level A success criteria are met (Level A); or

The WCAG 2.0 Level A and Level AA success criteria are met (Level AA); or

The WCAG 2.0 Level A, Level AA, and Level AAA success criteria are met (Level AAA).

Resolution: All accepts wording "Content Auto-Generation During Authoring Sessions (WCAG): Authors have the default option that, when web content is automatically generated during an authoring session, then one of the following is true:"
2. B.2.1.1 Accessible Content Possible (WCAG) Proposal

http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0076.html

Resolution: All accept: http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0076.html
3. Series of long-waiting non-normative (and hopefully minor) edits marked with a single "@":

Resolution: All accept: @The intent of this success criterion is to ensure that web content transformations intended only to optimize content do not result in the introduction of web content accessibility problems.
... All accept: @Pretty-print: A "pretty-print" tool reformats markup code to make it easier to read by programmers. The tool never makes changes to the markup tags.

@Video compression: A tool that compresses video does not automatically delete text tracks or secondary audio tracks since these may contain accessibility information.

Resolution: All accept @Video compression: A tool that compresses video does not automatically delete text tracks or secondary audio tracks since these may contain accessibility information.

@The intent of this success criterion is to increase the likelihood that text alternatives will be preserved by web content transformations. This is especially important because text alternatives, such as labels and long descriptions, can represent substantial investments of author effort.

Resolution: All accept: @The intent of this success criterion is to increase the likelihood that text alternatives will be preserved by web content transformations. This is especially important because text alternatives, such as labels and long descriptions, can represent substantial investments of author effort.

@Save as HTML: A word processor includes a "Save as Simple HTML" feature that re-codes word processor files into HTML where there is a one-to-one correspondence between elements. As a result, some word processor-specific content is lost (e.g., change tracking, footnotes). However, because of the existence of the <img> tag in HTML, images are preserved and, in order to meet this success...

scribe: criterion, the text alternatives associated with the image are also preserved in HTML.

Resolution: All accept: @Save as HTML: A word processor includes a "Save as Simple HTML" feature that re-codes word processor files into HTML where there is a one-to-one correspondence between elements. As a result, some word processor-specific content is lost (e.g., change tracking, footnotes). However, because of the existence of the <img> tag in HTML, images are preserved and, in order to...
... meet this success criterion, the text alternatives associated with the image are also preserved in HTML.

OLD: The intent of this success criterion is to ensure that if authoring tools only allow authors the ability to modify a subset of the properties of a content element, then the properties required for conformance to WCAG 2.0 are included in that subset.

@The intent of this success criterion is to ensure that if authoring tools provide authors with content authoring support that goes beyond source editing (e.g., property dialogs, etc.) then accessibility information that is required for the content are similarly supported. In many cases, authoring tools support a subset of all of the possible properties that technologies might offer. This...

scribe: success criterion requires that the subset of supported properties must include properties required for conformance to WCAG 2.0.

Resolution: All accept: @The intent of this success criterion is to ensure that if authoring tools provide authors with content authoring support that goes beyond source editing (e.g., property dialogs, etc.) then accessibility information that is required for the content are similarly supported. In many cases, authoring tools support a subset of all of the possible properties that technologies mi

ght offer. This success criterion requires that the subset of supported properties must include properties required for conformance to WCAG 2.0.

Resolution: All accept: @ (e.g. an "Image Properties" dialog).
... All accept @Silverlight, Flex

http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20110228/#sc_b121
Implementing Success Criterion B.1.2.1 Restructuring and Recoding Transformations (WCAG)

<scribe> ACTION: JR to Replace value judgement term with negative connotation term and flesh out a, b,s,d a bit morew [recorded in http://www.w3.org/2011/03/07-au-minutes.html#action01]

<trackbot> Created ACTION-325 - Replace value judgement term with negative connotation term and flesh out a, b,s,d a bit morew [on Jan Richards - due 2011-03-14].

JT: All members, esp from large companies, please make sure you have no more issues
... Next steps as well comment responses, implementation research

JS: Also we need to highlight what we think are the biggest changes
... For the status section

JT: We of course have considered all the comments, but we'd prefer not to have to approve comment reponsese point by point so will a 2 week window be sufficient?

SN: 2 weeks is pretty tough
... Esp with CSUN and spring break

JT: We be after CSUN
... What about splitting them into A and B
... Will talk to everyone next wk - Mar 14


-- 
(Mr) Jan Richards, M.Sc.
jrichards@ocad.ca | 416-977-6000 ext. 3957 | fax: 416-977-9844
Inclusive Design Research Centre (IDRC) | http://inclusivedesign.ca/
Faculty of Design | OCAD University


> -----Original Message-----
> From: w3c-wai-au-request@w3.org [mailto:w3c-wai-au-request@w3.org] On Behalf
> Of Richards, Jan
> Sent: March 4, 2011 5:08 PM
> To: AUWG
> Subject: AUWG Teleconference on 7 March 2011 4:00pm-5pm ET and Survey
> 
> There will be an AUWG teleconference on Monday 7 March 2011 at 4:00 pm - 5:00
> pm ET:
> 
> Call: (617) 761-6200 ext. 2894#
> IRC: server: irc.w3.org, port: 6665, channel: #au
> 
> If people think they will arrive more than 15 minutes late, please send
> me an email beforehand.
> 
> Editor's Draft:
> ===============
> http://www.w3.org/WAI/AU/2011/ED-ATAG20-20110228/
> http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20110228/
> 
> The dial-in numbers for Zakim are now:
> ======================================
> +1.617.761.6200	(Boston)
> +33.4.26.46.79.03	(Paris)
> +44.203.318.0479	(London)
> 
> Agenda:
> ========
> 
> 1. Survey:
> http://www.w3.org/2002/09/wbs/35520/20110302z/
> 
> 2. B.2.1.1 Accessible Content Possible (WCAG) Proposal
> http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0069.html
> 
> 3. Series of long-waiting non-normative (and hopefully minor) edits marked
> with a single "@":
> - @Warning when text is converted to graphics (meets (b)):
> - @Copy and paste as transformation (meets (b)):
> - @ Intent of Success Criterion B.1.2.2: The intent of this success criterion
> is to ensure that web content transformations intended only to optimize
> content do not result in the introduction of web content accessibility
> problems.
> - @Pretty-print: A "pretty-print" tool reformats markup code to make it easier
> to read by programmers. The tool never makes changes to the markup tags.
> - @Video compression: A tool that compresses video does not automatically
> delete text tracks or secondary audio tracks.
> - @ Intent of Success Criterion B.1.2.3: The intent of this success criterion
> is to increase the likelihood that text alternatives will be preserved by web
> content transformations. This is especially important because text
> alternatives, such as labels and long descriptions, can represent substantial
> investments of author effort.
> - @Save as HTML: A word processor includes a "Save as Simple HTML"...
> - @Intent of Success Criterion B.2.2.2: The intent of this success criterion
> - @ (e.g. an "Image Properties" dialog).
> - @Silverlight, Flex
> 
> 
> Future meetings:
> ================
> Mar. 14
> Mar. 21
> Mar. 28
> 
> Cheers,
> Jan
> 
> 
> --
> (Mr) Jan Richards, M.Sc.
> jrichards@ocad.ca | 416-977-6000 ext. 3957 | fax: 416-977-9844
> Inclusive Design Research Centre (IDRC) | http://inclusivedesign.ca/
> Faculty of Design | OCAD University
> 
> 
Received on Monday, 7 March 2011 22:10:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 March 2011 22:10:36 GMT