IRC log of au on 2009-01-05

Timestamps are in UTC.

20:51:11 [RRSAgent]
RRSAgent has joined #au
20:51:12 [RRSAgent]
logging to http://www.w3.org/2009/01/05-au-irc
20:51:25 [JR]
Zakim, this will be AUWG
20:51:25 [Zakim]
ok, JR; I see WAI_AUWG()3:00PM scheduled to start 51 minutes ago
20:51:32 [JR]
Meeting: WAI AU
20:51:40 [JR]
Chair: Jutta Treviranus
20:52:17 [JR]
Agenda:http://lists.w3.org/Archives/Public/w3c-wai-au/2009JanMar/0001.html
20:52:32 [JR]
Regrets: Anne M.
20:54:09 [jeanne]
jeanne has joined #au
20:55:38 [AndrewR]
AndrewR has joined #au
20:57:39 [Greg]
Greg has joined #au
20:59:24 [jeanne]
zakim, code?
20:59:24 [Zakim]
the conference code is 2894 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), jeanne
20:59:33 [Zakim]
WAI_AUWG()3:00PM has now started
20:59:40 [Zakim]
+??P3
20:59:44 [Zakim]
+Jeanne
20:59:52 [JR]
zakim, ??P3 is really JR
20:59:52 [Zakim]
+JR; got it
21:00:54 [Zakim]
+Greg_Pisocky
21:01:53 [Zakim]
+ +2
21:02:04 [Zakim]
+??P14
21:02:22 [JR]
zakim, +2 is really AndrewR
21:02:22 [Zakim]
+AndrewR; got it
21:02:42 [JR]
zakim, +??P12 is really Jutta
21:02:42 [Zakim]
sorry, JR, I do not recognize a party named '+??P12'
21:02:44 [jeanne]
zakim, who is here
21:02:44 [Zakim]
jeanne, you need to end that query with '?'
21:02:50 [jeanne]
zakim who is here?
21:03:06 [JR]
zakim, ??P12 is really Jutta
21:03:06 [Zakim]
+Jutta; got it
21:03:10 [jeanne]
zakim, who is here?
21:03:10 [Zakim]
On the phone I see JR, Jeanne, Greg_Pisocky, AndrewR, ??P14
21:03:11 [Zakim]
On IRC I see Greg, AndrewR, jeanne, RRSAgent, Zakim, JR, trackbot
21:03:13 [JR]
zakim, who's here?
21:03:13 [Zakim]
On the phone I see JR, Jeanne, Greg_Pisocky, AndrewR, ??P14
21:03:15 [Zakim]
On IRC I see Greg, AndrewR, jeanne, RRSAgent, Zakim, JR, trackbot
21:03:43 [jeanne]
zakim, ??P14 is really Jutta
21:03:43 [Zakim]
+Jutta; got it
21:03:54 [jeanne]
zakim, who is here?
21:03:54 [Zakim]
On the phone I see JR, Jeanne, Greg_Pisocky, AndrewR, Jutta
21:03:55 [Zakim]
On IRC I see Greg, AndrewR, jeanne, RRSAgent, Zakim, JR, trackbot
21:04:39 [jeanne]
present: JR, Jeanne, Greg, Andrew, Jutta
21:04:54 [jeanne]
regrets: Ann
21:08:39 [Zakim]
+ +1.603.578.aabb
21:08:44 [JR]
http://lists.w3.org/Archives/Public/w3c-wai-au/2008OctDec/0083.html
21:09:01 [JR]
zakim, +1.603.578.aabb is really Dana
21:09:01 [Zakim]
+Dana; got it
21:09:24 [JR]
Actual link to attachment: http://lists.w3.org/Archives/Public/w3c-wai-au/2008OctDec/att-0083/ATAG_Glossary_Review.doc
21:11:26 [JR]
Topic: Glossary review
21:12:03 [AndrewR]
JR: first term abbreviation. adding "adapted from" WCAG 2.0 in the brackets
21:12:42 [AndrewR]
JR: agreed at F2F in Redmond to not follow WCAG 2.0s style exactly
21:13:15 [JR]
http://www.w3.org/TR/WCAG20/#glossary
21:13:18 [Zakim]
-AndrewR
21:14:12 [jeanne]
http://www.w3.org/WAI/AU/2008/WD-ATAG20-20081202/#glossary
21:14:32 [Zakim]
+??P6
21:14:49 [AndrewR_]
AndrewR_ has joined #au
21:15:01 [jeanne]
zakim, ??P6 is really Andrew
21:15:01 [Zakim]
+Andrew; got it
21:18:19 [AndrewR]
JS: "enhance" seems to be indicate an "improvement". "engineer" may be a better word
21:20:54 [AndrewR]
JS: "provide" would be suitable
21:21:09 [JR]
A programmatic interface that is specifically engineered to provide communication between mainstream applications and assistive technologies (e.g., UIA, MSAA and IAccessible2 for Windows applications, AXAPI for MacOSX applications, Gnome Accessibility Toolkit API for Gnome applications, Java Access for Java applications, etc.). On some platforms it may be conventional to enhance communication furt
21:21:11 [JR]
her by implementing a document object.
21:22:02 [jeanne]
action: JS to update the document with new text for Platform Accessibility Architecture
21:22:02 [trackbot]
Created ACTION-68 - Update the document with new text for Platform Accessibility Architecture [on Jeanne Spellman - due 2009-01-12].
21:23:50 [AndrewR]
JR: could remove "severity" from the sentence
21:24:26 [JR]
accessibility problem
21:24:28 [JR]
ATAG 2.0 refers to two types of accessibility problems:
21:24:30 [JR]
1.authoring tool user interface accessibility problem: An aspect of an authoring tool user interface that does not meet one of the success criteria in Part A.
21:24:32 [JR]
2.Web content accessibility problem: An aspect of Web content that does not meet a WCAG success criteriaon.
21:25:54 [JR]
1.authoring tool user interface accessibility problem: An aspect of an authoring tool user interface that does not meet a success criterion in Part A.
21:26:37 [JR]
accessibility problem
21:26:39 [JR]
ATAG 2.0 refers to two types of accessibility problems:
21:26:40 [JR]
1.authoring tool user interface accessibility problem: An aspect of an authoring tool user interface that does not meet a success criterion in Part A.
21:26:42 [JR]
2.Web content accessibility problem: An aspect of Web content that does not meet a WCAG success criterion.
21:26:53 [jeanne]
action: JS to update the document with new text for "accessibility problem"
21:26:53 [trackbot]
Created ACTION-69 - Update the document with new text for \"accessibility problem\" [on Jeanne Spellman - due 2009-01-12].
21:27:04 [JR]
accessibility information
21:27:05 [JR]
Any information that is necessary for undertaking an accessible authoring practice (e.g., text descriptions of images, role and state information, relationships within complex tables).
21:28:12 [jeanne]
+1
21:28:49 [Zakim]
+Tim_Boland
21:30:05 [jeanne]
present+ Tim
21:32:22 [JR]
Action: JR - take another try at: "accessibility information" ... make it more direct
21:32:22 [trackbot]
Created ACTION-70 - - take another try at: \"accessibility information\" ... make it more direct [on Jan Richards - due 2009-01-12].
21:32:44 [JR]
accessible content support features
21:32:46 [JR]
Any features of an authoring tool that directly support authors in increasing the accessibility of the content being edited (i.e., in meeting any of the success criteria in Principle B.2).
21:34:52 [JR]
assistive technology [adapted from WCAG 2.0]
21:34:53 [JR]
Software and/or hardware that provides functionality to meet the requirements of users with disabilities that goes beyond direct accessibility features offered by mainstream applications. Assistive technology functionality includes alternative presentations (e.g., as synthesized speech or magnified content), alternative input methods (e.g., voice), additional navigation or orientation...
21:34:55 [JR]
...mechanisms, and content transformations (e.g., to make tables more accessible). Examples of assistive technologies that are important in the context of this document include the following:
21:35:10 [jeanne]
action: JS to update the document with new text for accessible content support features
21:35:12 [trackbot]
Created ACTION-71 - Update the document with new text for accessible content support features [on Jeanne Spellman - due 2009-01-12].
21:35:38 [JR]
•screen magnifiers, and other visual reading assistants, which are used by people with visual, perceptual and physical print disabilities to change text font, size, spacing, color, synchronization with speech, etc. in order improve the visual readability of rendered text and images;
21:35:39 [JR]
•screen readers, which are used by people who are blind to read textual information through synthesized speech or braille;
21:35:41 [JR]
•text-to-speech software, which is used by some people with cognitive, language, and learning disabilities to convert text into synthetic speech;
21:35:42 [JR]
•speech recognition software, which may be used by people who have some physical disabilities;
21:35:44 [JR]
•alternative keyboards, which are used by people with certain physical disabilities to simulate the keyboard (including alternate keyboards that use head pointers, single switches, sip/puff and other special input devices);
21:35:45 [JR]
•alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activations.
21:38:26 [JR]
http://lists.w3.org/Archives/Public/w3c-wai-au/2008OctDec/att-0083/ATAG_Glossary_Review.doc
21:38:57 [Tim]
Tim has joined #au
21:40:49 [JR]
assistive technology [adapted from WCAG 2.0]
21:40:51 [JR]
Software and/or hardware that provides functionality to meet the requirements of users with disabilities that goes beyond direct accessibility features offered by mainstream applications. Assistive technology functionality includes alternative presentations (e.g., as synthesized speech or magnified content), alternative input methods (e.g., voice), additional navigation or orientation...
21:40:52 [JR]
...mechanisms, and content transformations (e.g., to make tables more accessible). Examples of assistive technologies that are important in the context of this document includes but are not limited to the following:
21:43:00 [Zakim]
-Dana
21:45:01 [JR]
assistive technology [adapted from WCAG 2.0]
21:45:02 [JR]
Software and/or hardware that provides functionality to meet the requirements of users with disabilities that goes beyond direct accessibility features offered by mainstream applications. Assistive technology functionality includes alternative presentations (e.g., as synthesized speech or magnified content), alternative input methods (e.g., voice), additional navigation or orientation...
21:45:04 [JR]
...mechanisms, and content transformations (e.g., to make tables more accessible). Note: Examples of assistive technologies that are important in the context of this document includes but are not limited to the following:
21:45:05 [JR]
•screen magnifiers, and other visual reading assistants, which are used by people with visual, perceptual and physical print disabilities to change text font, size, spacing, color, synchronization with speech, etc. in order improve the visual readability of rendered text and images;
21:45:07 [JR]
•screen readers, which are used by people who are blind to read textual information through synthesized speech or braille;
21:45:08 [JR]
•text-to-speech software, which is used by some people with cognitive, language, and learning disabilities to convert text into synthetic speech;
21:45:11 [JR]
•speech recognition software, which may be used by people who have some physical disabilities;
21:45:14 [JR]
•alternative keyboards, which are used by people with certain physical disabilities to simulate the keyboard (including alternate keyboards that use head pointers, single switches, sip/puff and other special input devices);
21:45:17 [JR]
•alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activations.
21:46:26 [JR]
Note: Examples of assistive technologies include, but are not limited to, the following:
21:51:26 [jeanne]
+1
21:52:05 [JR]
audio [adapted from WCAG 2.0]
21:52:07 [JR]
The technology of sound reproduction. Audio can be created synthetically (including speech synthesis), recorded from real world sounds, or both.
21:52:24 [jeanne]
action: JS to update the document with new text for assistive technologies
21:52:25 [trackbot]
Created ACTION-72 - Update the document with new text for assistive technologies [on Jeanne Spellman - due 2009-01-12].
21:53:22 [JR]
authoring action
21:53:24 [JR]
Any action that authors can take using the authoring tool user interface that results in editing content (e.g., typing text, deleting, inserting an element, applying a template). Most authoring tool user interfaces also enable actions that do not edit content (e.g., setting preferences, viewing documentation).
21:53:41 [jeanne]
action: JS to update the document to add to the introduction of the Glossary section to add the text "definitions are normative, examples are informative."
21:53:41 [trackbot]
Created ACTION-73 - Update the document to add to the introduction of the Glossary section to add the text \"definitions are normative, examples are informative.\" [on Jeanne Spellman - due 2009-01-12].
21:55:00 [JR]
Any action that authors can take using the authoring tool user interface that results in creating or editing content (e.g., typing text, deleting, inserting an element, applying a template). Most authoring tool user interfaces also enable actions that do not edit content (e.g., setting preferences, viewing documentation).
21:55:53 [jeanne]
+1 to new definition. More brief, more clear.
21:56:19 [JR]
authoring outcome
21:56:21 [JR]
The content modifications that result from authoring actions. The scope of authoring outcomes range from narrow (e.g., inserting a link) to wide (e.g., adding a site-wide navigation system). Authoring outcomes are cumulative (e.g., text is entered, then styled, then made into a link, then given title).
21:56:39 [jeanne]
action: JS to update the document with new text for audio
21:56:40 [trackbot]
Created ACTION-74 - Update the document with new text for audio [on Jeanne Spellman - due 2009-01-12].
21:56:50 [jeanne]
action: JS to update the document with new text for authoring action
21:56:50 [trackbot]
Created ACTION-75 - Update the document with new text for authoring action [on Jeanne Spellman - due 2009-01-12].
21:58:22 [JR]
The content modifications that result from authoring actions (e.g., inserting a link, adding a site-wide navigation system). Authoring outcomes are cumulative (e.g., text is entered, then styled, then made into a link, then given a title).
21:59:34 [JR]
The content or content modifications that result from authoring actions (e.g., inserting a link, adding a site-wide navigation system). Authoring outcomes are cumulative (e.g., text is entered, then styled, then made into a link, then given a title).
22:02:35 [JR]
The content or content modifications that result from authoring actions. Authoring outcomes are cumulative (e.g., text is entered, then styled, then made into a link, then given a title).
22:03:38 [jeanne]
JS to update the document with new text for authoring actions
22:04:04 [Zakim]
-Tim_Boland
22:04:06 [Zakim]
-Greg_Pisocky
22:04:26 [Zakim]
-JR
22:04:30 [Zakim]
-Jeanne
22:04:51 [jeanne]
rrsagent, make logs public
22:04:52 [Zakim]
-Jutta
22:04:57 [jeanne]
rrsagent, make minutes
22:04:57 [RRSAgent]
I have made the request to generate http://www.w3.org/2009/01/05-au-minutes.html jeanne
22:07:21 [Zakim]
-Andrew
22:07:22 [Zakim]
WAI_AUWG()3:00PM has ended
22:07:24 [Zakim]
Attendees were Jeanne, JR, Greg_Pisocky, AndrewR, Jutta, Dana, Andrew, Tim_Boland
22:13:37 [AndrewR]
AndrewR has left #au
22:24:32 [jeanne]
rrsagent, bye
22:24:32 [RRSAgent]
I see 8 open action items saved in http://www.w3.org/2009/01/05-au-actions.rdf :
22:24:32 [RRSAgent]
ACTION: JS to update the document with new text for Platform Accessibility Architecture [1]
22:24:32 [RRSAgent]
recorded in http://www.w3.org/2009/01/05-au-irc#T21-22-02
22:24:32 [RRSAgent]
ACTION: JS to update the document with new text for "accessibility problem" [2]
22:24:32 [RRSAgent]
recorded in http://www.w3.org/2009/01/05-au-irc#T21-26-53
22:24:32 [RRSAgent]
ACTION: JR - take another try at: "accessibility information" ... make it more direct [3]
22:24:32 [RRSAgent]
recorded in http://www.w3.org/2009/01/05-au-irc#T21-32-22
22:24:32 [RRSAgent]
ACTION: JS to update the document with new text for accessible content support features [4]
22:24:32 [RRSAgent]
recorded in http://www.w3.org/2009/01/05-au-irc#T21-35-10
22:24:32 [RRSAgent]
ACTION: JS to update the document with new text for assistive technologies [5]
22:24:32 [RRSAgent]
recorded in http://www.w3.org/2009/01/05-au-irc#T21-52-24
22:24:32 [RRSAgent]
ACTION: JS to update the document to add to the introduction of the Glossary section to add the text "definitions are normative, examples are informative." [6]
22:24:32 [RRSAgent]
recorded in http://www.w3.org/2009/01/05-au-irc#T21-53-41
22:24:32 [RRSAgent]
ACTION: JS to update the document with new text for audio [7]
22:24:32 [RRSAgent]
recorded in http://www.w3.org/2009/01/05-au-irc#T21-56-39
22:24:32 [RRSAgent]
ACTION: JS to update the document with new text for authoring action [8]
22:24:32 [RRSAgent]
recorded in http://www.w3.org/2009/01/05-au-irc#T21-56-50