13:01:27 RRSAgent has joined #au 13:01:27 logging to http://www.w3.org/2009/06/15-au-irc 13:01:29 RRSAgent, make logs public 13:01:29 Zakim has joined #au 13:01:31 Zakim, this will be AUWG 13:01:31 ok, trackbot; I see WAI_AUWG(F2F)8:30AM scheduled to start 31 minutes ago 13:01:32 Meeting: Authoring Tool Accessibility Guidelines Working Group Teleconference 13:01:32 Date: 15 June 2009 13:01:49 zakim, code? 13:01:49 the conference code is 2894 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), jeanne 13:02:05 ann, does that give you what you need? 13:02:09 that's great. thanks! 13:02:19 wasn't sure if it was the usual number or something different. 13:02:50 WAI_AUWG(F2F)8:30AM has now started 13:02:57 +AnnM 13:04:01 Master document http://www.w3.org/WAI/AU/2009/ED-ATAG20-20090612/MASTER-20090612 13:04:32 Jan has joined #au 13:04:59 http://www.w3.org/WAI/AU/2009/ED-ATAG20-20090612/MASTER-20090612 13:08:20 + +3aaaa 13:08:55 zakim, who is here 13:08:55 jeanne, you need to end that query with '?' 13:09:01 zakim, who is here? 13:09:01 On the phone I see AnnM, +3aaaa 13:09:02 On IRC I see Jan, Zakim, RRSAgent, jeanne, AnnM, trackbot 13:09:20 zakim, +3aaaa is really Adobe 13:09:20 +Adobe; got it 13:11:17 zakim, Adobe has Jan_Richards, Reed_Shaffner, Sueann_Nichols, Jutta_Treviranus, Jeanne_Spellman 13:11:17 +Jan_Richards, Reed_Shaffner, Sueann_Nichols, Jutta_Treviranus, Jeanne_Spellman; got it 13:11:57 present+ Ann_McMeekin 13:12:13 rrsagent, make logs public 13:12:18 rrsagent, make minutes 13:12:18 I have made the request to generate http://www.w3.org/2009/06/15-au-minutes.html jeanne 13:13:11 zakim, who is here? 13:13:11 On the phone I see AnnM, Adobe 13:13:12 Adobe has Jan_Richards, Reed_Shaffner, Sueann_Nichols, Jutta_Treviranus, Jeanne_Spellman 13:13:14 On IRC I see Jan, Zakim, RRSAgent, jeanne, AnnM, trackbot 13:13:27 present+ Jan_Richards, Reed_Shaffner, Sueann_Nichols, Jutta_Treviranus, Jeanne_Spellman 13:17:23 chair: jutta, jan 13:17:40 meeting: AUWG Face to Face Day 1 13:21:50 rrsagent, make minutes 13:21:50 I have made the request to generate http://www.w3.org/2009/06/15-au-minutes.html jeanne 13:31:57 yes i can 13:32:05 zakim, who is here? 13:32:05 On the phone I see AnnM, Adobe 13:32:06 Adobe has Jan_Richards, Reed_Shaffner, Sueann_Nichols, Jutta_Treviranus, Jeanne_Spellman 13:32:07 On IRC I see Jan, Zakim, RRSAgent, jeanne, AnnM, trackbot 13:32:19 can you hear me? 13:32:44 ah. how strange. definitely not muted at this end (i checked) 13:48:28 Sueann has joined #au 13:49:56 Greg has joined #au 13:50:26 jtrevir has joined #au 13:52:06 topic: Review of public comments 13:52:46 action: JS to update Glossary to move the definition of Authoring Tool User Interface before the def of the Web based and non-Web based definitions 13:52:46 Created ACTION-156 - Update Glossary to move the definition of Authoring Tool User Interface before the def of the Web based and non-Web based definitions [on Jeanne Spellman - due 2009-06-22]. 13:53:04 Conducting review of public working draft http://www.w3.org/WAI/AU/2009/ED-ATAG20-20090612 13:53:16 topic: Guildline A.1.1 13:54:59 Resolution: Remove applicability note A.1.1 based upon public feedback. 13:56:13 Reed has joined #au 13:56:45 Topic Guidelin A.1.2 13:57:45 rrsagent, make minutes 13:57:45 I have made the request to generate http://www.w3.org/2009/06/15-au-minutes.html jeanne 13:57:48 Rationale: Authoring Tools that are Web applications are Web content that should conform to WCAG 2.0. 13:58:00 This will support the accessibility of the authoring tool user interface and will facilitate communication with assistive technologies via user agents. 13:59:32 A.1.2.1 14:01:56 Topic: A.1.2.1 14:03:21 Proposal by JR for A.1.2.1 Non-Web based authoing tool user interfaces follow (and cite in the conformance claim) accessibility standards and/or platform conventions that support accessibility. (Level A) 14:03:33 A.1.2.1 Non-Web-Based Accessible (Level A): Non-Web-based authoring tool user interfaces follow (and cite in the conformance claim) accessibility standards and/or platform conventions that support accessibility. (Level A) 14:04:30 Resolution Remove Applicability note for A.1.2.1 14:06:11 ReedShaffner has joined #au 14:07:46 A.1.1 Rationale 14:09:41 ReedShaff has joined #au 14:10:00 action: JT to reword the rationale for A.1.2 for clarity and grammar 14:10:00 Created ACTION-157 - Reword the rationale for A.1.2 for clarity and grammar [on Jutta Treviranus - due 2009-06-22]. 14:12:47 Guideline A.2.1 [For the authoring tool user interface] Provide access to alternative content in the Web content. 14:12:47 This is about non-text content - why not state that? Provide access to text alternatives for any non-text content in rendered views of Web content. 14:13:18 Topic: A.2.1 14:14:23 Topic: Guideline A.2.1 14:16:13 JT: Make alternative content available to the author. 14:16:49 scribe: Greg 14:17:29 A.2.1 Make alternative content available to the author. 14:19:33 Topic: Guideline A.2.1 rationale 14:21:51 Some authors require access to alternative content in order to interact with the Web content that they are authoring. 14:22:36 A.2.1.1. The definition of alternative content is inadequate to address this guideline. you may in fact have a flexible system which may require full equivalent replacements for the content defined by user preferences such as a table or accessible datagrid equivalent for a complex visualization. The system may in fact generate alterative content that would be more accessible to an individual user. Although WCAG does not address this ATAG certainly could while st 14:23:27 Although WCAG does not address this ATAG certainly could while still supporting WCAG. How the user specifies this equivalent will be based on their need. ... Think Access for All or ISO DRD/PNP 14:33:39 ARonksley has joined #au 14:40:00 action: JS to change "authors" to "author(s)" 14:40:00 Created ACTION-158 - Change "authors" to "author(s)" [on Jeanne Spellman - due 2009-06-22]. 14:40:20 stylistic note to change authors to author(s) throughout the standard 14:40:27 A.2.1.1 Recognized Alternative Content: When recognized alternative content is available@@define??@@ for Web content being edited, the authoring tool makes the alternative content accessible to the author(s). 14:41:57 action: JR to write a proposed defintion of "available" 14:41:57 Created ACTION-159 - Write a proposed defintion of "available" [on Jan Richards - due 2009-06-22]. 14:43:31 send comments to the public list at: public-atag2-comments@w3.org 14:45:09 topic: Guideline A.2.2 Rationale 14:46:21 2.2 wording needs to harmonize with WCAG; i.e. use "programmatically determinable" instead of "available via the platform 15:14:43 We are taking a 15 minute break. Reconvening at xx:30 15:14:58 will be back in 15 minutes. 15:26:27 rrsagent, make minutes 15:26:27 I have made the request to generate http://www.w3.org/2009/06/15-au-minutes.html jeanne 15:32:29 + +2 15:40:05 zakim, +2 is ARonksley 15:40:05 +ARonksley; got it 15:40:26 present+ Andrew_Ronksley 15:46:31 action: JR to propose a definition of programmatically determined. 15:46:31 Created ACTION-160 - Propose a definition of programmatically determined. [on Jan Richards - due 2009-06-22]. 16:01:50 yup 16:02:52 -ARonksley 16:03:10 A.2.2.1 Purpose of Added Presentation: If an editing view modifies the presentation of Web content to provide authors with additional information, then that additional information can be *programmatically determined*. (Level A) 16:03:22 A.2.2.2 Access to Text Presentation (Minimum): If any of the following properties are present in the Web content and are rendered in an editing view (e.g., WYSIWYG view) they can be *programmatically determined*. (Level A): @@wordsmith?@@ 16:03:24 (a) text font, 16:03:25 (b) text style (e.g., italic, bold), 16:03:27 (c) text color, and 16:03:28 (d) text size. 16:03:43 +??P0 16:04:51 zakim, ??P0 is really ARonksley 16:04:51 +ARonksley; got it 16:05:00 zakim, who is here? 16:05:00 On the phone I see AnnM, Adobe, ARonksley 16:05:01 Adobe has Jan_Richards, Reed_Shaffner, Sueann_Nichols, Jutta_Treviranus, Jeanne_Spellman 16:05:03 On IRC I see ARonksley, ReedShaff, jtrevir, Greg, Sueann, Jan, Zakim, RRSAgent, jeanne, AnnM, trackbot 16:05:25 zakim, Adobe also has Tim_Boland 16:05:25 +Tim_Boland; got it 16:05:50 zakim Adobe also has Greg_Pisocky 16:06:05 present+ Tim_Boland, Greg_Pisocky 16:06:12 rrsagent, make minutes 16:06:12 I have made the request to generate http://www.w3.org/2009/06/15-au-minutes.html jeanne 16:07:54 Topic: Guideline A.2.3 16:11:11 Rationale: Some authors need to set display settings for themselves that differ from the presentation that they define for the published Web content. 16:11:35 Here is the link to the updated comments document: http://www.w3.org/WAI/AU/2009/ED-ATAG20-20090612/atag20_pubWD_21may2009_comment_responses.html 16:12:54 The definition of visual and audio display settings states nothing about where they are set. These should reflect "platform" settings and user-defined application settings (Firefox, Safari 4, IE zoom features). 16:14:48 -AnnM 16:15:24 +AnnM 16:19:01 Action: JR to write a definition for Display Preferences. 16:19:01 Created ACTION-161 - Write a definition for Display Preferences. [on Jan Richards - due 2009-06-22]. 16:19:08 A.2.3.1 Independence of Display: Editing views that render content (e.g., WYSIWYG) allow the authors' own display preferences @@JR DEFINE@@ to take precedence in the editing view without affecting the Web content being edited (i.e., no effect on markup, style sheets, etc.). (Level A) 16:23:39 Greg has joined #au 16:26:56 4.1.8 Important Command Functions: Important command functions (e.g. related to navigation, display, content, information management, etc.) are available in a single keystroke. (Level AA) 16:27:10 ... from UAAG 16:51:32 topic: Checkpoint A.3.1.1 Important Commands 17:03:13 -ARonksley 17:04:06 A.3.1.1 Keyboard: All functionality of the authoring tool is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A) 17:04:16 Note 1: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not. 17:04:18 Note 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation. 17:04:27 A.3.1.3 Keyboard Shortcuts: The authoring tool provides keyboard shortcuts. (Level AA) 17:04:29 A.3.1.4 Customize Keyboard Access: The authoring tool allows authors to customize keyboard access. (Level AAA) 17:06:06 -AnnM 17:06:06 Lunch 1 hour will resume at 2:05 eastern 17:10:19 ARonksley has joined #au 17:15:08 +??P0 17:18:07 -??P0 17:55:21 rrsagent, make minutes 17:55:21 I have made the request to generate http://www.w3.org/2009/06/15-au-minutes.html jeanne 17:56:14 ReedShaff has joined #au 17:56:27 ReedShaff has joined #au 18:02:19 resumed at 2:05 18:02:40 topic: Guideline A.3.2 18:03:29 Jeanne looking for an explanation of the "moving targets" in the rationale 18:04:17 scribe: reed 18:04:40 scribenick:ReedShaff 18:05:05 +AnnM 18:05:31 commenting on contradictions in time limits 18:08:15 discussing WCAG wording as is and what to take over 18:08:54 Just grab text from WCAG? 18:08:57 Agreement from group 18:09:13 A.3.2.2 to be replaced with WCAG 2.2.1 18:10:44 Change A3.2 18:10:58 Changed to Provide authors with enough time 18:12:27 JT: Sounds a little off still 18:12:42 JR: It could also apply to use of help system 18:12:42 s 18:13:30 JR: Can someone take on A3.2.2? 18:13:59 action: JS to provide new text for A3.2.2 and moving targets 18:13:59 Created ACTION-162 - Provide new text for A3.2.2 and moving targets [on Jeanne Spellman - due 2009-06-22]. 18:14:06 Action: JS to write proporsal for A.3.2 rationale and Guildline text 18:14:06 Created ACTION-163 - Write proporsal for A.3.2 rationale and Guildline text [on Jeanne Spellman - due 2009-06-22]. 18:14:37 close action 163 18:15:08 Sueann: not sure I get the moving targets piece, what does moving targets have to do with time limits? 18:15:20 I'm not sure how 18:15:20 A.3.2.3 Moving Targets: If a user interface component that accepts mouse input is capable of movement (e.g., animated vector graphic), provide authors with the option to stop the movement. (Level A) 18:15:20 relates to A.3.2 - since moving targets doesn't seem to have anything to do with time limits. Maybe A.3.2 should be more broadly worded. I think the original wording (from the techniques document Enable time-independent interaction. makes more sense. 18:16:39 TB: why capable of movement and not is moving? 18:16:46 ARonksley_ has joined #au 18:16:49 JR: Yeah, like that 18:17:07 JS: can we take out accepts mouse input? 18:17:19 JR: it doesn't always have to be editable 18:17:28 JT: if a user interface component is moving 18:17:33 JR: yeah, alright 18:17:40 JR: should I get rid of eg? 18:17:44 +??P3 18:19:06 JR: If JS can work something in about why stopping a moving target provides enough time, would that make it better? 18:19:12 Sueann: stretch 18:20:26 JS: I now have 4 18:20:33 comments on this section 18:21:28 JS seems to have proposal that will satisfy 18:21:32 People who have difficulty typing, operating the mouse, or processing information can be prevented from using systems with short time limits or requiring a short reaction speed, such as clicking on a moving target. 18:21:54 JS: probably should be short reaction time 18:22:33 JS: fast reaction speed? 18:22:58 Rationale: Some authors who have difficulty typing, operating the mouse, or processing information can be prevented from using systems with short time limits or requiring a fast reaction speed, such as clicking on a moving target. 18:22:59 JR: Can we move on to A3.3 18:23:10 on A 3.3 18:25:03 JR: checking to see what WCAG uses 18:25:11 JS: I will take this as an editorial change 18:26:13 Action: JS to do a global update of "photosensitive epilepsy" to "photosensitive seizure disorder" 18:26:13 Created ACTION-164 - Do a global update of "photosensitive epilepsy" to "photosensitive seizure disorder" [on Jeanne Spellman - due 2009-06-22]. 18:26:58 JR: rationale, we do this because it's difficult for an authoring tool to prevent the multitude of content and predicting what will flash, we try and solve that at the global level 18:27:16 JR: even if we had levels, how would that work on things like videos 18:27:53 JS: maye we could call it option for static view 18:28:58 Moving on 18:32:05 A.3.4.1 The definition of structured element sets is too limiting. It should not just in include organized elements. Headings are considered structural yet in and by themselves they do not imply a collection of oranized elements. ARIA landmarks should be included as well. The definition of structured element should be that of a significant semantic areas of the page which in turn support the structure of the web page. You might even refer to the WAI-ARIA taxono 18:33:53 http://www.w3.org/TR/2009/WD-wai-aria-20090224/#state_prop_taxonomy 18:38:17 JR: send as an action item to someone, no issue with things being a structured element set, just definition 18:39:09 JR: other than that? 18:39:24 JR: oh there was asuggest about moving navigate by heading to level A 18:39:42 Closed on A3.4 for now 18:39:45 Moved to A3.5 18:41:08 Action: SN A3.4.1 come up with a recommendation on how to address adding WAI-ARIA like taxonomy 18:41:08 Created ACTION-165 - A3.4.1 come up with a recommendation on how to address adding WAI-ARIA like taxonomy [on Sueann Nichols - due 2009-06-22]. 18:41:18 atrribute and formatting added in response to comment 18:41:42 comment: seems werid thisn refers to UI when this really talking about searching for content 18:41:47 JR: that's why i say of the content 18:43:40 Sueann: in 3.5 dont understand use of web content here, shouldn't this apply to editing views, this applies that the web content is output of the tool, should this be covered in B 18:45:40 JR: maybe we make a slight tweek to clarify it's within the web content being authored 18:46:05 Leaving A3.5 18:46:09 Moving to A3.6 18:46:18 Rationale: Authors who have difficulty typing or operating the mouse benefit from the ability to navigate to arbitrary points within the Web content being authored. 18:46:38 Any comments on A3.6? 18:52:00 scribe:Sueann 18:52:14 move to a.3.7 18:52:25 topic: A.3.7 18:57:30 If authoring tools are required to be WCAG compliant, why are previews a special case? It would seem that they should be subject to the same set of rules. 18:57:30 - Why is there a reference to UAAG 1.0? Has the ATAG working group looked at UAAG 1.0 and identified guidelines that if employed would be counter WCAG 2.0 and ATAG 2.0 objectives or today's best practices? For example, guideline 4.1 is outdated in UAAG. All user agents today provide full magnification rather than just text which is much more accurate. Should you still be require font size increases. 18:58:03 This is a preview and reflects the current state in the authoring process 18:59:56 4.1 Applicability note - It is acceptable for certain committing actions (e.g., "save", "publish") to to make all previous authoring actions irreversible. (to to) typo 19:02:02 Jan looking to remove applicability note in 4.2 19:04:31 A.4.2.1 and A.4.2.2 - needs editorial work. When I first read it, I didn't get it as all product features are required to meet part A. But then I realized it's trying to say that if your product has implemented functions in support of the requirements in Part A, you have to document those functions 19:10:55 -??P3 19:12:25 15 min break... 19:20:31 Continuing 19:26:36 Jan recommending removing the AAA requirement for tutorials A.4.2.2, additional concern where would we get an implementation. 19:26:54 Rationale: Some authors may not be able to understand or operate the authoring tool user interface without proper documentation. 19:27:16 +??P14 19:29:02 Agenda: review of levels with a focus on AAA to ensure the requirements can be implemented 19:29:15 on to part B 19:29:37 change in 3. Existing Technologies 19:31:25 Jean would like 1. Author Availability editing changes 19:31:44 and 4. Authoring Systems 19:37:14 Existing Technologies: The success criteria in Part B only apply to support for production of Web content using the Web content technologies that are included in the conformance profile. 19:39:26 Jan: remove b.1.1 add clarification in the AGAG 2.0 conformance profile 19:41:58 IBM comment:Guideline B.1.1 19:41:58 This seems to restrictive. An authoring tool may support include support for all kinds of markup. If one markup, like SVG, which does not fully support assistive technologies is chosen the whole rest of the tool fails? Recommend that the author be given the choice of choosing only accessible technologies. In that mode it should be considered to satisfy this guideline - unless there are none. 19:41:58 This section should also allow for the selection of equivalent alternatives that are accessible. Take a Mashup authoring tool. A chart may be inaccessible but a table equivalent may be acceptable. You might even take into account user preferences. 19:42:00 The section refers to accessible Web content but the definition of accessible web content refers to a particular level of WCAG. Why should an ATAG 2.0 compliant tool support WCAG 1.0 when in fact the guidelines for being ATAG 2.0 compliant require that the authoring tool meet WCAG 2.0 requirements? I disagree that this should include all versions of WCAG. 19:47:11 Need to add a note to handle the case when a technology that can not be made accessible is used an alternative solution can be used to provide an accessible alternative. 19:48:47 getting rid of b.1.1 and fixing the conformance claim 19:53:09 add a bullet item under conformance claim 5 to include web technologies used to provide an alternative conforming version 20:00:57 -AnnM 20:09:08 Jean raised the question should this be a moved out of the claim, and be a guideline in b.2.1 20:27:00 -??P14 20:28:52 +??P0 20:30:12 -??P0 20:30:42 new guideline to support the idea that alternative content, alternative technology be used, and made available by the tool 20:31:05 for the creation of an alterntive to the content that is not accessible. 20:31:27 not sure where this will go -Jean suggested b.2.1 20:33:16 +??P0 20:39:22 new guideline "if a web content technology included in the conformance profile cannot be used to create accessible Web content, then a "conforming alternative version" in another web content technology must also be make available prior to publication. 20:39:30 this still needs work 20:42:27 issues: there are lots of different "tools" that make up parts of an entire web content solution. 20:42:57 Jean : original comment was to address mashups, not part of the conformance claim. 20:46:35 first issue is the task that is being performed, in the case of an animation there the author would not use html. the image or "paint" program won't be accessible. 20:49:36 Jan: can we change the definition of web content technologies to include a conforming alternative for technologies that are not accessible. 20:54:11 Sueann: We need a definition of "Accessible Web Content Technologies" that is the sum of the parts of the Web Content TEchnologis. 20:55:26 Jean suggested we table this and several of us take this and proposals 20:55:52 next step: come up with an agenda for Tue. 20:57:07 agenda: brainstorm people and organizations to invite to review 20:57:26 review levels - AAA 20:58:04 complete the review of feedback in Section B 20:59:36 triage comments - what needs to be worked f2f vs. assigned for action 21:00:07 techniques? 21:02:00 zakim, who is here? 21:02:00 On the phone I see Adobe, ??P0 21:02:01 Adobe has Jan_Richards, Reed_Shaffner, Sueann_Nichols, Jutta_Treviranus, Jeanne_Spellman, Tim_Boland 21:02:02 would be very helpful to have a tool that has mapped to the atag success criteria to see what the conformance is 21:02:04 On IRC I see ARonksley, jtrevir, Sueann, Jan, Zakim, RRSAgent, jeanne, trackbot 21:02:25 zakim, Adobe also has Greg_Pisocky 21:02:25 +Greg_Pisocky; got it 21:02:35 rrsagent, make minutes 21:02:35 I have made the request to generate http://www.w3.org/2009/06/15-au-minutes.html jeanne 21:07:54 -Adobe 21:08:05 -??P0 21:08:06 WAI_AUWG(F2F)8:30AM has ended 21:08:07 Attendees were AnnM, Jan_Richards, Reed_Shaffner, Sueann_Nichols, Jutta_Treviranus, Jeanne_Spellman, ARonksley, Tim_Boland, Greg_Pisocky 21:09:36 rrsagent, make minutes 21:09:36 I have made the request to generate http://www.w3.org/2009/06/15-au-minutes.html jeanne 21:11:39 rrsagent, bye 21:11:39 I see 10 open action items saved in http://www.w3.org/2009/06/15-au-actions.rdf : 21:11:39 ACTION: JS to update Glossary to move the definition of Authoring Tool User Interface before the def of the Web based and non-Web based definitions [1] 21:11:39 recorded in http://www.w3.org/2009/06/15-au-irc#T13-52-46 21:11:39 ACTION: JT to reword the rationale for A.1.2 for clarity and grammar [2] 21:11:39 recorded in http://www.w3.org/2009/06/15-au-irc#T14-10-00 21:11:39 ACTION: JS to change "authors" to "author(s)" [3] 21:11:39 recorded in http://www.w3.org/2009/06/15-au-irc#T14-40-00 21:11:39 ACTION: JR to write a proposed defintion of "available" [4] 21:11:39 recorded in http://www.w3.org/2009/06/15-au-irc#T14-41-57 21:11:39 ACTION: JR to propose a definition of programmatically determined. [5] 21:11:39 recorded in http://www.w3.org/2009/06/15-au-irc#T15-46-31 21:11:39 ACTION: JR to write a definition for Display Preferences. [6] 21:11:39 recorded in http://www.w3.org/2009/06/15-au-irc#T16-19-01 21:11:39 ACTION: JS to provide new text for A3.2.2 and moving targets [7] 21:11:39 recorded in http://www.w3.org/2009/06/15-au-irc#T18-13-59 21:11:39 ACTION: JS to write proporsal for A.3.2 rationale and Guildline text [8] 21:11:39 recorded in http://www.w3.org/2009/06/15-au-irc#T18-14-06 21:11:39 ACTION: JS to do a global update of "photosensitive epilepsy" to "photosensitive seizure disorder" [9] 21:11:39 recorded in http://www.w3.org/2009/06/15-au-irc#T18-26-13 21:11:39 ACTION: SN A3.4.1 come up with a recommendation on how to address adding WAI-ARIA like taxonomy [10] 21:11:39 recorded in http://www.w3.org/2009/06/15-au-irc#T18-41-08