IRC log of au on 2011-01-24

Timestamps are in UTC.

20:56:28 [RRSAgent]
RRSAgent has joined #au
20:56:28 [RRSAgent]
logging to http://www.w3.org/2011/01/24-au-irc
20:56:34 [jeanne]
jeanne has joined #au
20:56:37 [Jan]
Zakim, this will be AUWG
20:56:37 [Zakim]
ok, Jan; I see WAI_AUWG()3:00PM scheduled to start 56 minutes ago
20:56:42 [Jan]
Meeting: WAI AU
20:57:06 [Jan]
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0019.html
20:57:12 [Jan]
Chair: Jutta Treviranus
20:57:15 [Jan]
Sctibe: Jan
20:57:53 [AleMiele]
Hi all
21:00:23 [Jan]
Regrets: Alastair C.
21:00:54 [Jan]
zakim, code?
21:00:54 [Zakim]
the conference code is 2894 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), Jan
21:01:00 [Zakim]
WAI_AUWG()3:00PM has now started
21:01:07 [Zakim]
+??P0
21:01:14 [Jan]
zakim, ??P0 is really Jan
21:01:14 [Zakim]
+Jan; got it
21:01:38 [Zakim]
+[Microsoft]
21:02:07 [Jan]
zakim, [Microsoft] is really Cherie
21:02:07 [Zakim]
+Cherie; got it
21:02:13 [Zakim]
+ +1.571.765.aaaa
21:02:48 [Zakim]
+??P3
21:02:53 [Jan]
zakim, aaaa is really Greg
21:02:53 [Zakim]
+Greg; got it
21:02:57 [Zakim]
+Jeanne
21:03:32 [Jan]
zakim, ??P3 is really AlessandroMiele
21:03:32 [Zakim]
+AlessandroMiele; got it
21:04:06 [Zakim]
+??P5
21:04:06 [gpisocky]
gpisocky has joined #au
21:04:36 [Jan]
zakim, ??P5 is really Jutta
21:04:36 [Zakim]
+Jutta; got it
21:05:04 [Jan]
zakim, who's here?
21:05:04 [Zakim]
On the phone I see Jan, Cherie, Greg, AlessandroMiele, Jeanne, Jutta
21:05:05 [Zakim]
On IRC I see gpisocky, jeanne, RRSAgent, AleMiele, Zakim, Jan, trackbot
21:07:33 [Jan]
http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0019.html
21:08:01 [Jan]
Topic: Survey results
21:08:02 [Jan]
http://www.w3.org/2002/09/wbs/35520/20110113/results
21:08:34 [Jan]
Topic: Proposal to replace A.2.2.2 and A.2.2.3
21:08:50 [Jan]
proposal is here: http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0013.html
21:08:55 [Zakim]
+ +1.561.582.aabb
21:09:27 [Jan]
zakim, aabb is really SueannN
21:09:27 [Zakim]
+SueannN; got it
21:09:52 [Zakim]
+[Microsoft]
21:11:51 [Jan]
zakim, [Microsoft] is really AlexLi
21:11:51 [Zakim]
+AlexLi; got it
21:12:32 [Jan]
http://www.w3.org/2002/09/wbs/35520/20110113/results#xq2
21:13:00 [Jan]
A.2.2.2 Access to Rendered Text Properties: If a text property is both rendered and editable by an editing-view and the property can be communicated by the supported platform accessibility service, then the property can be programmatically determined. (Level A)
21:16:54 [Jan]
is programmatically determibable
21:18:41 [Jan]
drop "by an editing-view "
21:19:03 [Jan]
A.2.2.2 Access to Rendered Text Properties: If a text property is both rendered and editable and the property can be communicated by the supported platform accessibility service, then the property is programmatically determineable. (Level A)
21:19:19 [Jan]
Resolution: No objections to "A.2.2.2 Access to Rendered Text Properties: If a text property is both rendered and editable and the property can be communicated by the supported platform accessibility service, then the property is programmatically determineable. (Level A)"
21:19:42 [Jan]
Topic: B.1.1.2
21:19:44 [Jan]
http://www.w3.org/2002/09/wbs/35520/20110113/results#xq1
21:21:52 [Jan]
Resolution: All accept proposal http://www.w3.org/2002/09/wbs/35520/20110113/results#xq1
21:22:00 [Jan]
Topic: Removing from B.2.3.1:
21:22:08 [Jan]
http://www.w3.org/2002/09/wbs/35520/20110113/results#xq3
21:23:07 [Jan]
B.2.3.1 Alternative Content is Editable (WCAG): Authors are able to modify programmatically associated text alternatives for non-text content. (Level A) @@including types of alternative content that may not typically be displayed on screen by user agents
21:25:51 [Jan]
Action JR: To clarify where we are on tools that are just checkers
21:25:51 [trackbot]
Created ACTION-318 - Clarify where we are on tools that are just checkers [on Jan Richards - due 2011-01-31].
21:27:07 [ssnichol]
ssnichol has joined #au
21:27:30 [Sueann]
Sueann has joined #au
21:27:50 [ssnichol]
ssnichol has left #au
21:28:09 [Jan]
Resolution: All accept proposal http://www.w3.org/2002/09/wbs/35520/20110113/results#xq3
21:28:30 [Jan]
Topic: Defini6tion of alternative content
21:28:32 [Jan]
http://www.w3.org/2002/09/wbs/35520/20110113/results#xq4
21:30:46 [Jan]
Importantly, from the perspective of authoring tools, alternative content may or may not be:
21:30:48 [Jan]
* @@programmatically associated: Alternative content whose location and purpose can be programmatically determined from the original content for which it is serving as an alternative. For example, a paragraph might serve as a text alternative for an image, but it is only programmatically associated if this relationship is properly encoded (e.g. by "aria-labeledby").
21:32:34 [Jan]
Resolution: Accept new defn with Greg's grmmar fix http://www.w3.org/WAI/AU/2011/ED-ATAG20-20110105/#def-Alternative-Content
21:32:51 [Jan]
Topic: Definition of author permission
21:33:01 [Jan]
http://www.w3.org/WAI/AU/2011/ED-ATAG20-20110105/#def-Authoring-Permission
21:33:08 [Jan]
http://www.w3.org/2002/09/wbs/35520/20110113/results#xq5
21:35:43 [Jan]
author permission: Authorization that allows modification of given web content. Some authoring tools are capable of managing authoring permissions in order to prevent unauthorized modifications.
21:36:53 [Jan]
Multiple author roles: Some authoring tools include multiple author roles, each with different views and content editing permissions (e.g. a content management system may separate the roles of designers, content authors, and quality assurers). In these cases, the Part B success criteria apply to the authoring tool as a whole, not to the view provided to any particular author role. Accessible...
21:36:55 [Jan]
...content support features should be made available to any author role where it would be useful.
21:37:52 [Jan]
Resolution: "author permission: Authorization that allows modification of given web content. Some authoring tools are capable of managing authoring permissions in order to prevent unauthorized modifications."
21:38:21 [Jan]
Topic: Definition of Web content
21:38:22 [Jan]
http://www.w3.org/2002/09/wbs/35520/20110113/results#xq7
21:38:40 [Jan]
content (web content)
21:38:41 [Jan]
Information and sensory experience to be communicated to the end user by means of a user agent, including code or markup that defines the content's structure, presentation, and interactions. In ATAG 2.0, the term is primarily used to refer to the output that is produced by the authoring tool. Content produced by authoring tools may include web applications, including those that act as...
21:38:43 [Jan]
...web-based authoring tools. Content may or may not be:
21:38:45 [Jan]
* accesible content (WCAG): Content that meets the WCAG 2.0 success criteria (Level A, AA, or AAA).
21:42:06 [Jan]
http://www.w3.org/TR/2009/WD-ATAG20-20091029/
21:42:13 [Jan]
web content [adapted from WCAG 2.0]
21:42:15 [Jan]
Information and sensory experience to be communicated to the end user by means of a user agent, including code or markup that defines the content's structure, presentation, and interactions. In ATAG 2.0, "web content" is primarily used to refer to the output that is produced by the authoring tool. "Web content" may include web applications, including those that act as web-based authoring...
21:42:16 [Jan]
...tools. Accessible web content is web content that conforms to a particular level of WCAG 2.0 .
21:44:40 [Jan]
Resolution: to accept http://www.w3.org/WAI/AU/2011/ED-ATAG20-20110105/#def-Web-Content with Alessandro's correction"accesible"
21:45:04 [Jan]
Topic: Defn of content rendering
21:45:06 [Jan]
http://www.w3.org/2002/09/wbs/35520/20110113/results#xq8
21:45:38 [Jan]
content rendering
21:45:39 [Jan]
User interface functionality that authoring tools present if they render, play or execute the web content being edited. ATAG 2.0 recognizes several types of content renderings:
21:45:41 [Jan]
* conventional renderings (or "WYSIWYG"): @@When content is rendered in a way that is similar to the default rendering a user agents would create from the same content. While "WYSIWYG", standing for "What-you-see-is-what-you-get" is the common term, it is problematic in terms of accessibility because reinforces the assumption that there is one end user experience; or
21:45:43 [Jan]
* unconventional renderings: When content is rendered differently than it would be in a typical user agent (e.g. rendering an audio file as a graphical wavefront); or
21:45:44 [Jan]
* partial renderings: When some aspects of the content are rendered, played, or executed, but not others (e.g. a frame-by-frame video editor renders the graphical, but not the timing aspects, of a video).
21:46:00 [Jan]
* conventional renderings (or "WYSIWYG"): @@When content is rendered in a way that is similar to the default rendering a user agent would create from the same content. While "WYSIWYG", standing for "What-you-see-is-what-you-get" is the common term, it is problematic in terms of accessibility because reinforces the assumption that there is one end user experience; or
21:49:52 [Jan]
conventional renderings (or "WYSIWYG"): When content is rendered in a way that is similar to the default rendering a user agents would create from the same content. While "WYSIWYG", standing for "What-you-see-is-what-you-get" is the common term, differences between user agents and end user settings mean that in reality there is no single typical end user experience; or
21:50:17 [Zakim]
-SueannN
21:50:32 [Jan]
conventional renderings (or "WYSIWYG"): When content is rendered in a way that is similar to the default rendering a user agent would create from the same content. While "WYSIWYG", standing for "What-you-see-is-what-you-get" is the common term, differences between user agents and end user settings mean that in reality there is no single typical end user experience; or
21:51:19 [Jan]
Resolution: All accept defintion of content rendering with "conventional renderings (or "WYSIWYG"): When content is rendered in a way that is similar to the default rendering a user agent would create from the same content. While "WYSIWYG", standing for "What-you-see-is-what-you-get" is the common term, differences between user agents and end user settings mean that in reality there is no...
21:51:20 [Jan]
...single typical end user experience; or"
21:51:28 [Zakim]
+SueannN
21:52:07 [Jan]
Topic: Defn Content Transformations
21:52:09 [Jan]
http://www.w3.org/2002/09/wbs/35520/20110113/results#xq9
21:52:21 [Jan]
content transformations
21:52:23 [Jan]
Processes that takes as input, content in one web content technology or non-web content technology (e.g. a word processing format) and produces as output, content that has been either:
21:52:25 [Jan]
* @@optimized: e.g. removing whitespace, re-compressing images; or
21:52:26 [Jan]
* restructured: e.g. linearizing tables, splitting a document into pages; or
21:52:28 [Jan]
* re-coded: e.g. HTML to XHTML, a word processing format to HTML.
21:53:47 [Jan]
Processes that take as input, content in one web content technology or non-web content technology (e.g. a word processing format) and produce as output, content that has been either:
21:54:48 [Jan]
Processes that content in one web content technology or non-web content technology (e.g. a word processing format) as input and produce as output, content that has been either:
21:55:14 [Jan]
Processes that content in one web content technology or non-web content technology (e.g. a word processing format) as input and produce content that has been either:
21:56:25 [Jan]
Resolution: All agree to content transformations rewording with change "Processes that content in one web content technology or non-web content technology (e.g. a word processing format) as input and produce content that has been either:"
21:56:42 [Jan]
Topic: Default Option
21:56:43 [Jan]
http://www.w3.org/2002/09/wbs/35520/20110113/results#xq10
21:58:13 [Jan]
Default Option: A setting or value for an option that is assigned automatically by the authoring tool and remains in effect unless canceled or changed by the author.
21:58:40 [Jan]
Resolution: All accept "Default Option: A setting or value for an option that is assigned automatically by the authoring tool and remains in effect unless canceled or changed by the author."
21:59:19 [Zakim]
-AlexLi
21:59:21 [Zakim]
-Cherie
21:59:24 [Zakim]
-SueannN
21:59:26 [Zakim]
-Jan
21:59:32 [Zakim]
-Greg
21:59:34 [Zakim]
-AlessandroMiele
21:59:44 [Jan]
RRSAgent, make minutes
21:59:44 [RRSAgent]
I have made the request to generate http://www.w3.org/2011/01/24-au-minutes.html Jan
21:59:50 [Jan]
RRSAgent, set logs public
21:59:55 [Jan]
Zakim, bye
21:59:55 [Zakim]
leaving. As of this point the attendees were Jan, Cherie, +1.571.765.aaaa, Greg, Jeanne, AlessandroMiele, Jutta, +1.561.582.aabb, SueannN, AlexLi
21:59:55 [Zakim]
Zakim has left #au
22:00:00 [Jan]
RRSAgent, bye
22:00:00 [RRSAgent]
I see 1 open action item saved in http://www.w3.org/2011/01/24-au-actions.rdf :
22:00:00 [RRSAgent]
ACTION: JR to To clarify where we are on tools that are just checkers [1]
22:00:00 [RRSAgent]
recorded in http://www.w3.org/2011/01/24-au-irc#T21-25-51