- DRAFT -

Authoring Tool Accessibility Guidelines Working Group Teleconference

16 Sep 2010

See also: IRC log

Attendees

Contents

• Topics
• Summary of Action Items

RSSagent timed out without making minutes. The following are copied from the IRC log and lightly edited.

<Jan> MASTER: http://www.w3.org/WAI/AU/2010/ED-ATAG20-20100914/MASTER-20100914.html

<jeanne> zakim, aaaa is Adobe_meeting

<Zakim> +Adobe_meeting; got it

<jeanne> zakim, Adobe_meeting has Jutta, Jan, Jeanne, Greg, Sueann

<Zakim> +Jutta, Jan, Jeanne, Greg, Sueann; got it

<Jan> Comment table: http://lists.w3.org/Archives/Public/w3c-wai-au/2010JulSep/att-0084/atag20-8Jul10LC-comments-rev4.html

<jeanne> rrsagent, make logs public

<RRSAgent> I have made the request, jeanne

<jeanne> rrsagent, make minutes

<RRSAgent> I have made the request to generate http://www.w3.org/2010/09/16-au-minutes.html jeanne

* Quits: gpisocky (chatzilla@192.150.10.200) (Connection reset by peer)

* Joins: gpisocky (chatzilla@192.150.10.200)

<jeanne> action: jeanne to respond to Oracle (Peter Wallach) to ask what the points of conflict with 508 with ATAG, and that 508 cannot be referenced in an international standard.

* @trackbot noticed an ACTION. Trying to create it.

* RRSAgent records action 1

<@trackbot> Created ACTION-290 - Respond to Oracle (Peter Wallach) to ask what the points of conflict with 508 with ATAG, and that 508 cannot be referenced in an international standard. [on Jeanne Spellman - due 2010-09-23].

<jeanne> Group discussed the Oracle request for reference to 508 in Part A. The group agreed that 508 is a national standard that is not appropriate in an international standard.

<jeanne> SN and GP argued that we have to limit the number of standards being referenced, because vendors will not try to meet all of them. Vendors will meet 508 first, because that is market driven.

<jeanne> topic: WCAG Accessibility supported

<jeanne> group discussed how to make the qualification to WCAG more clear

<jeanne> several alternatives were discussed. Propose to substitute "meet" for "conform"

<jeanne> topic: Triage continues

<jeanne> topic: Email Client as an Authoring Tool

<jeanne> Discussion that tools may also do other things, such as adding content that isn't web content.

<jeanne> In that case, the authoring tools do not apply as it is outside the scope.

<jeanne> action: Jeanne to add Flex and Silverlight to the definition examples of Web Content Technologies.

* @trackbot noticed an ACTION. Trying to create it.

* RRSAgent records action 2

<@trackbot> Created ACTION-291 - Add Flex and Silverlight to the definition examples of Web Content Technologies. [on Jeanne Spellman - due 2010-09-23].

<jeanne> topic: variations from WCAG

<jeanne> If there is an SC that goes beyond WCAG, we must show that it is necesary for Authoring Tool accessibility. If not, we should harmonize with WCAG 2

<jeanne> action: gp to write a proposal for a definition of "additional information"

* @trackbot noticed an ACTION. Trying to create it.

* RRSAgent records action 3

<@trackbot> Created ACTION-292 - Write a proposal for a definition of "additional information" [on Greg Pisocky - due 2010-09-23].

<jeanne> topic: IBM comment 17

<jeanne> SN: How does someone determine the way the accessibility of mashup information? When you exchange information you have to say how accessibility is communicated?

<jeanne> JR: The pieces of the mashup are going to be in some piece of technology where the original author may or may not have done. We say that you only have to be responsible for information you can edit.

<jeanne> TB: It is an issue of how the authoring tool is going to use it.

<jeanne> JR: Example - a PNG file has metadata. A HTML editor can take the PNG and put it in the document and just identify that "blob" to the user.

Summary of Action Items