19:55:25 RRSAgent has joined #au 19:55:25 logging to http://www.w3.org/2009/03/09-au-irc 19:55:33 * Zakim, this will be AUWG 19:55:41 Zakim, this will be AUWG 19:55:41 ok, JR; I see WAI_AUWG()3:00PM scheduled to start 55 minutes ago 19:55:46 Meeting: WAI AU 19:56:40 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2009JanMar/0056.html 19:57:17 Regrets: Andrew R., Tim B., Roberto S. 19:59:53 zakim, code? 19:59:53 the conference code is 2894 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), jeanne 20:00:10 WAI_AUWG()3:00PM has now started 20:00:16 + +1.617.324.aaaa 20:01:00 zakim, aaaa is really jeanne 20:01:01 +jeanne; got it 20:01:02 +??P3 20:01:24 zakim, ??P3 is really JR 20:01:24 +JR; got it 20:03:32 +Greg_Pisocky 20:10:13 + +1.561.582.aabb 20:10:55 zakim, +1.561.582.aabb is really SueAnn 20:10:55 +SueAnn; got it 20:11:17 zakim, +1.617.324.aaaa is really jeanne 20:11:17 sorry, JR, I do not recognize a party named '+1.617.324.aaaa' 20:11:31 zakim, who's here? 20:11:31 On the phone I see jeanne, JR, Greg_Pisocky, SueAnn 20:11:32 On IRC I see RRSAgent, Zakim, JR, jeanne, trackbot 20:11:45 Chair: Jan Richards 20:12:56 Greg has joined #au 20:13:12 Scribe: Greg 20:13:25 Topic: F2F Planning 20:13:32 TPAC face to face planning 20:13:46 http://lists.w3.org/Archives/Public/w3c-wai-au/2009JanMar/0060.html 20:14:07 Sueann has joined #au 20:15:20 Does AWUG intend to participate in the meeting in Santa Clara, California USA 20:15:22 November 2 - 6 2009 20:20:06 Final decision to be made next Monday. Jean will put it on a survey 20:20:17 action: JS to put question on attending TPAC on next week's survey 20:20:17 Created ACTION-125 - Put question on attending TPAC on next week's survey [on Jeanne Spellman - due 2009-03-16]. 20:20:19 Topic: ARIA review 20:20:51 http://lists.w3.org/Archives/Public/w3c-wai-au/2009JanMar/0049.html 20:21:26 ARIA Review - ARIA has a last call, ATAG should take a look just to satisfy itself. The new deadline is April 17, 2009 20:21:27 New deadline April 17 20:22:25 Reviews to the group by April 6, 2009 looking at ARIA through the lens of ATAG. 20:23:23 Complete the glossary review 20:23:29 Topic: Finish (hopefully) the glossary review 20:23:40 http://lists.w3.org/Archives/Public/w3c-wai-au/2009JanMar/att-0055/ATAG2_Glossary_Review__Rev11_.doc 20:23:41 +??P8 20:24:04 zakim, ??P8 is really JuttaT 20:24:04 +JuttaT; got it 20:24:10 http://www.w3.org/2002/09/wbs/35520/20090227/results 20:25:36 Topic: assistive technology 20:26:17 assistive technology [adapted from WCAG 2.0] 20:26:19 Software (or hardware), separate from the authoring tool, that provides functionality to meet the requirements of users with disabilities. Some authoring tools may also provide direct accessibility features. 20:26:20 Examples of assistive technologies include, but are not limited to, the following: 20:26:54 • 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 to improve the visual readability of rendered text and images; 20:26:55 • screen readers, which are used by people who are blind to read textual information through synthesized speech or braille; 20:26:57 • text-to-speech software, which is used by some people with cognitive, language, and learning disabilities to convert text into synthetic speech; 20:26:58 • speech recognition software, which may be used by people who have some physical disabilities; 20:27:00 • 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); 20:27:01 • alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activations. 20:27:35 direct accessibility features 20:27:36 Features of an authoring tool that provide functionality to meet the requirements of users with disabilities (e.g., keyboard navigation, zoom functions, text-to-speech). Additional or specialized functionality may still be provided by external assistive technology. 20:28:04 action: JS to update glossary with the new wording of the first paragraph of Assistive Technology 20:28:04 Created ACTION-126 - Update glossary with the new wording of the first paragraph of Assistive Technology [on Jeanne Spellman - due 2009-03-16]. 20:28:31 +1 20:28:45 All: No problem wqith either defn 20:28:57 action: JS to update glossary with new definition of direct accessibility features 20:28:57 Created ACTION-127 - Update glossary with new definition of direct accessibility features [on Jeanne Spellman - due 2009-03-16]. 20:29:49 Topic: equivalent alternative vs. altenative content 20:29:58 Content that is used in place of other content that a person may not be able to access. An equivalent alternative fulfills essentially the same function or purpose as the original content. Examples include text alternatives for non-text content, captions for audio, audio descriptions for video, sign language for audio, media alternatives for time-based media. See WCAG for more information 20:32:18 All: Agree on "Alternative Content" 20:32:54 http://lists.w3.org/Archives/Public/w3c-wai-au/2009JanMar/0062.html 20:33:11 Action: JS to update glossary with the term "alternative content" deleting "equivalent". Inside the definition as well. 20:33:11 Created ACTION-128 - Update glossary with the term \"alternative content\" deleting \"equivalent\". Inside the definition as well. [on Jeanne Spellman - due 2009-03-16]. 20:33:32 Topic: Prominence 20:33:36 http://lists.w3.org/Archives/Public/w3c-wai-au/2009JanMar/0062.html 20:35:02 prominence 20:35:04 A heuristic measure of how likely users are to notice items (controls or 20:35:06 groups of controls) in a user interface that they are operating. 20:35:07 Prominence is affected by numerous factors, including: the number of 20:35:09 navigation steps required, the reading order position, visual properties 20:35:10 (e.g., size, spacing, colour), and even the modality of use (e.g., mouse 20:35:12 vs. keyboard use). For purposes of conformance to ATAG 2.0, item A is 20:35:13 considered to be *at least as prominent* as item B if: 20:35:15 * (a) both items occur in the same item container (e.g., menu for menu 20:35:16 items, list for list items, dialog box for text boxes) 20:35:18 * (b) item A is highlighted if item B is highlighted. 20:35:19 * (c) item A occurs higher in the reading order or immediately follows 20:35:21 item B. 20:37:11 JS: I noticed our examples talk about text 20:37:32 JS: Like to see text, controls, groups of controls 20:40:04 (2a) Rewording B.1.1.2, B.1.1.4, B.1.1.6 for clarity: 20:40:06 B.1.1.2 Author Choice of Technologies (Level A): If the authoring tool 20:40:07 provides authors with Web content technology options, THEN ANY 20:40:09 *ACCESSIBLE technology* (WCAG Level A) options THAT ARE SUITABLE FOR THE 20:40:11 TASK ARE *AT LEAST AS PROMINENT* AS ANY OTHER TECHNOLOGY OPTIONS. (Level A) 20:40:40 (2b) Add this sentence to the end of the definition of "Technology": 20:40:42 An *accessible technology* is a technology that may be used in a way 20:40:43 that is "accessibility supported" (For more information on 20:40:45 "accessibility supported", see WCAG 2.0). 20:46:59 (3) Rewording B.2.1.1, B.2.1.2, B.2.1.3: 20:47:01 B.2.1.1 Guide Accessible (Level A): If authors are prompted for any 20:47:02 information as content is being added or updated (e.g., by an image 20:47:04 modification dialog), then: 20:47:06 (a) PROMPTS ARE INCLUDED for any accessibility information required for 20:47:07 that content to meet WCAG Level A (Level A) 20:47:09 (b) THE ACCESSIBILITY PROMPTS ARE *AT LEAST AS PROMINENT*. 20:57:39 Action JR: Modify proposal for Rewording B.2.1.1, B.2.1.2, B.2.1.3 to not use "At least as prominent" but to use some workflow typoe language instead 20:57:39 Created ACTION-129 - Modify proposal for Rewording B.2.1.1, B.2.1.2, B.2.1.3 to not use \"At least as prominent\" but to use some workflow typoe language instead [on Jan Richards - due 2009-03-16]. 20:57:54 (4) Rewording B.2.5.3: 20:57:56 B.2.5.3 Template Selection Mechanism: If authors are provided with a 20:57:58 template selection mechanism, then (Level A): 20:57:59 (a) the selection mechanism indicates the accessibility status of 20:58:01 templates (if known), AND 20:58:02 (b) any accessible template options ARE *AT LEAST AS PROMINENT* AS other 20:58:04 TEMPLATE options. 20:58:53 (5) Rewording B.2.5.7: 20:58:55 B.2.5.7 Pre-Authored Content Selection Mechanism: If authors are 20:58:57 provided with a selection mechanism for pre-authored content other than 20:58:58 templates (e.g., clip art gallery, widget repository, design themes), 20:59:00 then (Level AA): 20:59:01 (a) the selection mechanism indicates the accessibility status of the 20:59:03 pre-authored content (if known), AND 20:59:04 (b) any accessible options ARE *AT LEAST AS PROMINENT* AS other 20:59:06 PRE-AUTHORED CONTENT options. 20:59:17 (7) Rewording B.3.1.1: 20:59:19 B.3.1.1 Accessible Options Prominent : If authors are provided with 20:59:21 multiple options for an authoring task, options that will result in 20:59:22 content conforming to *WCAG* Level A ARE *AT LEAST AS PROMINENT* AS 20:59:24 OPTIONS THAT WILL NOT. (Level A) 20:59:44 (8) Minor edit to B.3.3.4: 20:59:46 B.3.3.4 At Least as Prominent: Accessible content support features are 20:59:48 *at least as prominent* [DEL] as comparable features related to other 20:59:49 types of Web content problems (e.g., invalid markup, syntax errors, 20:59:51 spelling and grammar errors). (Level AA) 21:00:26 (6) Rewording the rationale of B.3.1: 21:00:28 Guideline B.3.1 Rationale: When authors are learning a new authoring 21:00:30 tool, they may find and learn to use the first authoring action they 21:00:31 encounter that achieves their intended outcome. Since they may be 21:00:33 unaware of the issue of accessibility, it preferable that accessible 21:00:35 content be an additional unintended outcome, rather than inaccessible 21:00:37 content. 21:03:27 -JuttaT 21:03:28 -Greg_Pisocky 21:03:28 -SueAnn 21:03:56 -JR 21:03:57 -jeanne 21:03:57 WAI_AUWG()3:00PM has ended 21:03:59 Attendees were +1.617.324.aaaa, jeanne, JR, Greg_Pisocky, SueAnn, JuttaT 21:06:50 NEXT CALL Mar 23 21:07:00 RRSAgent, make minutes 21:07:00 I have made the request to generate http://www.w3.org/2009/03/09-au-minutes.html JR 21:07:07 RRSAgent, set logs public 21:07:14 Zakim, bye 21:07:14 Zakim has left #au 21:07:24 RRSAgent, bye 21:07:24 I see 5 open action items saved in http://www.w3.org/2009/03/09-au-actions.rdf : 21:07:24 ACTION: JS to put question on attending TPAC on next week's survey [1] 21:07:24 recorded in http://www.w3.org/2009/03/09-au-irc#T20-20-17 21:07:24 ACTION: JS to update glossary with the new wording of the first paragraph of Assistive Technology [2] 21:07:24 recorded in http://www.w3.org/2009/03/09-au-irc#T20-28-04 21:07:24 ACTION: JS to update glossary with new definition of direct accessibility features [3] 21:07:24 recorded in http://www.w3.org/2009/03/09-au-irc#T20-28-57 21:07:24 ACTION: JS to update glossary with the term "alternative content" deleting "equivalent". Inside the definition as well. [4] 21:07:24 recorded in http://www.w3.org/2009/03/09-au-irc#T20-33-11 21:07:24 ACTION: JR to Modify proposal for Rewording B.2.1.1, B.2.1.2, B.2.1.3 to not use "At least as prominent" but to use some workflow typoe language instead [5] 21:07:24 recorded in http://www.w3.org/2009/03/09-au-irc#T20-57-39