Minutes from AUWG Teleconference on 7 February 2011 4:00pm-5pm ET

http://www.w3.org/2011/02/07-au-minutes.html

WAI AU
07 Feb 2011

Agenda

See also: IRC log
Attendees

Present
    Jeanne, +1.571.765.aaaa, Alastair, Jan, Alex, AleMiele, Greg, +1.561.582.aabb, Sueann, Jutta, Tim_Boland
Regrets
    Cherie, E.
Chair
    Jutta Treviranus
Scribe
    jeanne

Contents

    * Topics
         1. Finish Jan 24 survey
         2. Definition of programmatically determined (programmatically determinable)
         3. Definition of Definition of recognized
         4. Definition of sequential keyboard navigation
         5. Renaming "Applicability Notes" as "Conformance Conditions"
         6. Proposal re: B.1.1.3
         7. Proposal to strengthen B.2.1.1 (was B.1.1.1)
         8. B.2.4.4 Save for Reuse:
         9. Next publishing
    * Summary of Action Items

<scribe> scribe: jeanne
Finish Jan 24 survey
Definition of programmatically determined (programmatically determinable)

http://www.w3.org/2002/09/wbs/35520/20110113/results#xq11

5 accepts, Jutta requests grammar edits. Alastair had changes for clarity.

<Jan> When information is encoded in a way that allows different software, including assistive technologies, to extract and present the information in different modalities. ATAG 2.0 uses this term in two contexts:

<Jan> Communication between the authoring tool and assistive technology: For non-web-based user interfaces, this means making use of a platform accessibility services, general-purpose APIs, and in some cases document object models. For web-based user interfaces, this means following WCAG 2.0 so that the user agent can pass on the information.

<Jan> Processing content: Is the authoring tool able to extract information from the content (e.g., to extract the language of content from the markup).

<scribe> ACTION: jeanne to create a new survey to look for a new time for meeting. [recorded in http://www.w3.org/2011/02/07-au-minutes.html#action01]

<trackbot> Created ACTION-319 - Create a new survey to look for a new time for meeting. [on Jeanne Spellman - due 2011-02-14].

<Jan> Processing content: Whether the authoring tool able to extract information from the content (e.g., to extract the language of content from the markup).

<Jan> Communication between the authoring tool and assistive technology: For non-web-based user interfaces, this means making use of a platform accessibility services, general-purpose APIs, and in some cases document object models. For web-based user interfaces, this means following WCAG 2.0 so that the user agent can pass on the information.

<Jan> When information is encoded in a way that allows different software, including assistive technologies, to extract and present the information in different modalities. ATAG 2.0 uses this term in two contexts:

<Jan> - Communication between the authoring tool and assistive technology: For non-web-based user interfaces, this means making use of a platform accessibility services, general-purpose APIs, and in some cases document object models. For web-based user interfaces, this means following WCAG 2.0 so that the user agent can pass on the information.

<Jan> - Processing content: Is the authoring tool able to extract information from the content (e.g., to extract the language of content from the markup).

Information that is encoded in a way that allows different software, including assistive technologies, to extract and present the information in different modalities. ATAG 2.0 uses this term in two contexts:

<Jan> Information that is encoded in a way that allows different software, including assistive technologies, to extract and present the information in different modalities. ATAG 2.0 uses this term in two contexts:

<Jan> > - Communication between the authoring tool and assistive technology: For non-web-based user interfaces, this means making use of platform accessibility services, general-purpose APIs, and in some cases document object models. For web-based user interfaces, this means following WCAG 2.0 so that the user agent can pass on the information.

<Jan> - Processing content: Whether the authoring tool able to extract information from the content (e.g., to extract the language of content from the markup).

<Jan> SN: Suggests: Communication between the authoring tool and assistive technology: For non-web-based user interfaces, this means making use of platform accessibility services, APIs, and in some cases document object models. For web-based user interfaces, this means following WCAG 2.0 so that the user agent can pass on the information.

<Jan> Information that is encoded in a way that allows different software, including assistive technologies, to extract and present the information in different modalities. ATAG 2.0 uses this term in two contexts:

<Jan> - Communication between the authoring tool and assistive technology: For non-web-based user interfaces, this means making use of platform accessibility services, APIs, and in some cases document object models. For web-based user interfaces, this means following WCAG 2.0 so that the user agent can pass on the information.

<Jan> - Processing content: Whether the authoring tool able to extract information from the content (e.g., to extract the language of content from the markup).

<Jan> For web-based user interfaces, this means ensuring that the user agent can pass on the information (e.g., through the use of ARIA).

<Jan> - Communication between the authoring tool and assistive technology: For non-web-based user interfaces, this means making use of platform accessibility services, APIs, and in some cases document object models. For web-based user interfaces, this means ensuring that the user agent can pass on the information (e.g., through the use of ARIA).

Alex: WCAG doesn't really address this directly. It may be confusing.

<Jan> Information that is encoded in a way that allows different software, including assistive technologies, to extract and present the information in different modalities. ATAG 2.0 uses this term in two contexts:

<Jan> - Communication between the authoring tool and assistive technology: For non-web-based user interfaces, this means making use of platform accessibility services, APIs, and in some cases document object models. For web-based user interfaces, this means ensuring that the user agent can pass on the information (e.g., through the use of ARIA).

<Jan> - Processing content: Whether the authoring tool able to extract information from the content (e.g., to extract the language of content from the markup).

<Jan> - Processing content: Whether the authoring tool is able to extract information from the content (e.g., to extract the language of content from the markup).

<Jan> Resolution: All accept the wording above for programmatically determinable.
Definition of Definition of recognized

<Jan> http://www.w3.org/2002/09/wbs/35520/20110113/results#xq13

<Jan> Resolution: All accept remove defn of recognized
Definition of sequential keyboard navigation

<Jan> http://www.w3.org/2002/09/wbs/35520/20110113/results#xq14

<Jan> Using a keyboard interface to navigate one-by-one through all of the items in an ordered set (e.g. menu items, form fields, etc.). This is in contrast to direct navigation methods such as keyboard shortcuts and bypass links.

<Jan> Resolution: All accept add "sequential keyboard navigation"

no objections

This finishes the 24 january survey

http://www.w3.org/2002/09/wbs/35520/20110204/results#xq2
Renaming "Applicability Notes" as "Conformance Conditions"

<Jan> http://www.w3.org/2002/09/wbs/35520/20110204/results#xq2

Alex: they are not conditions, they are disclaimers of W3C.

Jeanne: Not all were conditions, so I didn't want to use the term.

<Jan> Alastair: "Conformance Applicability"

<Jan> Jutta: "Conformance Applicability Notes"

<Jan> Resolution: All accept "Conformance Applicability Notes"
Proposal re: B.1.1.3

<Jan> http://www.w3.org/2002/09/wbs/35520/20110204/results#xq1

<Jan> Resolution: All accept Folding " B.1.1.3 Template Auto-Selection (WCAG)" into a note in "B.1.1.2 Content Auto-Generation During Authoring Sessions (WCAG)": " Note 1: Automatic generation includes automatically selecting templates for authors."

<Jan> Proposal to strengthen B.2.1.1 (was B.1.1.1)
Proposal to strengthen B.2.1.1 (was B.1.1.1)

<Jan> http://www.w3.org/2002/09/wbs/35520/20110204/results#xq3

Greg: It is about the ability to do it, rather than the certainty that it should be done.

Jutta: The authoring tool is only capable of editing what the authoring tool can edit.

Alastair: one authoring tool can have a very simple interface, but follows ATAG, while another simply provides an HTML view. Both would be seen as equal under ATAG and that doesn't seem right. But I recognize that this would be difficult to quantify.

<scribe> Postponed for more discussion.

<Jan> ACTION: JR to To organize chat with Greg, Alastair, Alex about this B.2.1.1 [recorded in http://www.w3.org/2011/02/07-au-minutes.html#action02]

<trackbot> Created ACTION-320 - Organize chat with Greg, Alastair, Alex about this B.2.1.1 [on Jan Richards - due 2011-02-14].

<Jan> http://www.w3.org/2002/09/wbs/35520/20110204/results#xq4
B.2.4.4 Save for Reuse:

<Jan> Greg withdraws objection.

<Jan> Resolution: All accept: B.2.4.4 Save for Reuse: When authors enter programmatically associated text alternatives for non-text content, both of the following are true: (Level AAA) (a) the text alternatives are automatically saved and suggested by the authoring tool, if the same non-text content is reused; and (b) the author has the option to edit or delete the saved text alternatives.
Next publishing

Jeanne: What's left?

Definition of authoring tool, bundling of changes, maybe a couple more substantive changes.

jeanne: We also need to make sure our comment responses are ok.

Jan: People need to read the responses and make any notes about the comments - wording, tone, etc.

Jeanne: I think the week after CSUN is a more realistic date for publishing.

Jan: We don't want to go to Last Call again without people who made comments having agreed to the changes.
Summary of Action Items
[NEW] ACTION: jeanne to create a new survey to look for a new time for meeting. [recorded in http://www.w3.org/2011/02/07-au-minutes.html#action01]
[NEW] ACTION: JR to To organize chat with Greg, Alastair, Alex about this B.2.1.1 [recorded in http://www.w3.org/2011/02/07-au-minutes.html#action02]



-- 
(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: Richards, Jan
> Sent: February 4, 2011 4:24 PM
> To: AUWG
> Subject: AUWG Teleconference on 7 February 2011 4:00pm-5pm ET
> 
> There will be an AUWG teleconference on Monday 7 February 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-20110204/
> http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20110204/
> 
> 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. Finish Jan 24 survey
> http://www.w3.org/2002/09/wbs/35520/20110113/results
> 
> 2. Feb 7 Survey
> http://www.w3.org/2002/09/wbs/35520/20110204/
> 
> 3. (With 10 minutes to go) Quick discussion of next steps. i.e. Target
> date for next Public Draft?
> 
> Future meetings:
> ================
> Feb. 14
> Feb. 21: Family Day (Ontario, Canada): NO CALL
> Feb. 28
> Mar. 7
> Mar. 14
> Mar. 21
> Mar. 28
> 
> Cheers,
> Jan
> 
> 
> 
> ATAG 2.0 Guidelines:
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> --
> (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 February 2011 22:13:06 UTC