19:49:16 RRSAgent has joined #au 19:49:16 logging to http://www.w3.org/2012/01/16-au-irc 19:49:30 Zakim, this will be AUWG 19:49:31 ok, Jan; I see WAI_AUWG()3:00PM scheduled to start in 11 minutes 19:49:39 Meeting: WAI AU 19:50:04 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2012JanMar/0008.html 19:50:44 Regrets: Alessandro M, Tim B 20:00:26 WAI_AUWG()3:00PM has now started 20:00:33 +[IPcaller] 20:00:48 zakim, [IPcaller] is really Jan 20:00:48 +Jan; got it 20:01:40 +??P7 20:01:55 +[IPcaller] 20:02:06 zakim, [IPcaller] is really Andrew 20:02:06 +Andrew; got it 20:02:18 zakim, ??P7 is really Jutta 20:02:18 +Jutta; got it 20:02:23 Chair: Jutta Treviranus 20:02:47 andrewronksley has joined #au 20:03:00 +[Microsoft] 20:03:39 zakim, [Microsoft] is really Alex 20:03:39 +Alex; got it 20:05:04 +Greg 20:06:05 + +1.561.582.aaaa 20:06:26 zakim, aaaa is really Sueann 20:06:26 +Sueann; got it 20:07:08 http://lists.w3.org/Archives/Public/w3c-wai-au/2012JanMar/0008.html 20:07:56 Scribe: Jan 20:08:30 Topic: 1. Tentative "Conformance Requirements" Section - everyone took an action last week to look at this text. 20:08:40 http://www.w3.org/WAI/AU/2012/ED-IMPLEMENTING-ATAG20-20120113/#conf-req 20:08:51 JT: People have chance to read? 20:08:58 SN: No chance yet? 20:09:23 JT: We will all now read it http://www.w3.org/WAI/AU/2012/ED-IMPLEMENTING-ATAG20-20120113/#conf-req 20:09:24 +[Microsoft] 20:09:47 zakim, [Microsoft] is really Cherie 20:09:47 +Cherie; got it 20:16:45 WCAG2: http://www.w3.org/TR/WCAG/#conformance 20:17:58 GP: Wonders about "Statement of" 20:18:06 JR: No problem to remove it. 20:18:12 JT: Any objections? 20:18:16 None 20:20:06 note 2 in ATAG 2.0 conformance...ie is confusing 20:20:29 an applicable Level A success criterion has not been met 20:20:38 original: Note 2: If the minimum conformance level (Level A) has not been achieved (i.e., at least one applicable Level A success criterion has not been met), it is still beneficial to publish a statement specifying which success criteria were met. 20:21:20 original: Note 2: If the minimum conformance level (Level A) has not been achieved (i.e., not all applicable Level A success criteria have been met), it is still beneficial to publish a statement specifying which success criteria were met. 20:21:32 NEW: Note 2: If the minimum conformance level (Level A) has not been achieved (i.e., not all applicable Level A success criteria have been met), it is still beneficial to publish a statement specifying which success criteria were met. 20:21:51 AL: Under Success Criteria Satisfaction...NA should be first 20:22:36 JR: +1 20:22:42 JT: Objections? 20:22:48 No objections 20:24:54 AL: Do we need to define "authoring process components"? 20:25:21 JR: I think it is implicit but I can try? 20:25:38 JT: Do we use the phrase elsewhere? 20:25:40 JR: No 20:25:50 JT: Other way to phrase 20:26:32 JR: Sub-system? 20:28:03 AL: Maybe JT: tools or components? 20:28:13 Original: his conformance option may be selected when an authoring tool would require additional authoring process components in order to conform as a complete authoring system. This option may be used for components with very limited functionality (e.g. a plug-in) up to nearly complete systems (e.g. a markup editor that only lacks accessibility checking functionality). 20:28:38 JT: This conformance option may be selected when an authoring tool would require additional tools or components in order to conform as a complete authoring system. This option may be used for components with very limited functionality (e.g. a plug-in) up to nearly complete systems (e.g. a markup editor that only lacks accessibility checking functionality). 20:28:43 No objections 20:28:51 NEW: This conformance option may be selected when an authoring tool would require additional tools or components in order to conform as a complete authoring system. This option may be used for components with very limited functionality (e.g. a plug-in) up to nearly complete systems (e.g. a markup editor that only lacks accessibility checking functionality). 20:29:26 JT: We accept all of the new language with today's three modifications/ 20:29:38 No objections 20:30:36 Resolution: Accept new "Conformance Requirements" text with 3 modifications: Rem statement of; NEW: Note 2: If the minimum conformance level (Level A) has not been achieved (i.e., not all applicable Level A success criteria have been met), it is still beneficial to publish a statement specifying which success criteria were met.; NEW: This conformance option may be selected when an authoring... 20:30:37 ...tool would require additional tools or components in order to conform as a complete authoring system. This option may be used for components with very limited functionality (e.g. a plug-in) up to nearly complete systems (e.g. a markup editor that only lacks accessibility checking functionality). 20:30:51 2. Part A Conformance Applicability Note: Platform limitations 20:31:14 http://lists.w3.org/Archives/Public/w3c-wai-au/2012JanMar/0001.html 20:31:22 "Statement of Partial ATAG 2.0 Conformance - Platform Limitation (Level A, AA, or AAA) 20:31:24 This conformance option may be selected when an authoring tool is unable to meet one or more success criteria because of intrinsic limitations of the platform (e.g., lacking a platform accessibility service). The (optional) explanation of conformance claim results should explain what platform features are missing." 20:31:35 JT: Thoughts? 20:32:41 GP: So 2 flavours of partial for different reasons? 20:32:44 JR: Yes 20:33:03 JR: WCAG2 has 2 flavours of partial as well? 20:33:07 JR: WCAG2 has 2 flavours of partial as well. 20:33:23 No objections 20:33:47 Resolution: Accept new partial conformance type http://lists.w3.org/Archives/Public/w3c-wai-au/2012JanMar/0001.html 20:34:01 Topic: 3. Proposals on A.4.2.1 (Explain Accessibility Features) and A.4.2.2 (Explain All Features) 20:34:09 http://lists.w3.org/Archives/Public/w3c-wai-au/2012JanMar/0003.html 20:35:47 A.4.2.1 Explain Accessibility Features: For each authoring tool feature that is used to meet Part A of ATAG 2.0, at least one of the following is true: 20:35:48 (a) Explained in documentation: use of the feature is explained in the authoring tool's documentation; or 20:35:50 (b) Explained in interface: use of the feature is explained in the user interface; or 20:35:51 (c) Platform service: the feature is a service provided by an underlying platform; or 20:35:53 (d) Not used by authors: the feature is not used directly by authors (e.g., passing information to a platform accessibility service) 20:35:55 Note: The accessibility of the documentation is covered by Guideline A.1.1 and Guideline A.1.2. 20:35:57 A.4.2.2 Explain All Features: For each authoring tool feature, at least one of the following is true: 20:36:06 a) Explained in documentation: use of the feature is explained in the authoring tool's documentation; or 20:36:07 (b) Explained in interface: use of the feature is explained in the user interface; or 20:36:09 (c) Platform service: the feature is a service provided by an underlying platform; or 20:36:11 (d) Not used by authors: the feature is not used directly by authors (e.g., passing information to a platform accessibility service) 20:36:12 Note: The accessibility of the documentation is covered by Guideline A.1.1 and Guideline A.1.2. 20:36:21 JT: Thoughts? 20:36:25 +Jeanne 20:37:31 JT: Are previous concerns addressed? 20:38:24 GP: Description vs explanation? 20:38:46 JR: Explain comes from 508 Refresyh 20:39:28 CE: Agree that describe is better than explain 20:40:09 JR: Described is fine with me 20:40:29 JT: Any objection to "described" in the handle and elsewhere 20:40:37 Resolution: Change explain to describe 20:41:05 Resolution: All accept new A421 and A422 with the change (http://lists.w3.org/Archives/Public/w3c-wai-au/2012JanMar/0003.html) 20:41:14 Topic: 4. Proposal to remove A.3.6.5 Assistance with Preferences 20:42:26 http://lists.w3.org/Archives/Public/w3c-wai-au/2011JulSep/0107.html 20:42:49 JT: Any concerns with dropping it? 20:43:01 GP: No -Jan make a good case 20:43:54 JT: Do we have other related? 20:44:06 GP: THis is really a usability thing 20:46:03 JT: Maybe this should be added as a note somewhere? 20:46:47 Action JR: Find a place to slot in making user settings usable in intent, examples 20:46:47 Created ACTION-371 - Find a place to slot in making user settings usable in intent, examples [on Jan Richards - due 2012-01-23]. 20:47:09 Resolution: Remove SC A365 20:47:17 Topic: 5. Glossary: Content Generation 20:47:22 http://lists.w3.org/Archives/Public/w3c-wai-au/2012JanMar/0007.html 20:48:12 content generation (content authoring, content editing): 20:48:14 The act of specifying the actual web content that will be rendered, played or executed by the end user's user agent. While the precise details of how content is created in any given system may vary widely, responsibility for the generation of content can be any combination of the following (): 20:48:16 - author generated content: Web content for which authors are fully responsible. The author may only be responsible down to a particular level (e.g., when asked to type a text label, the author is responsible for the text, but not for how the label is marked up; when typing markup in a source editing-view, the author is not responsible for the fact that UNICODE is used to encode the text ). 20:48:18 - automatically generated content: Web content for which developer-programmed functionality is fully responsible (e.g., what markup to output when an author requests to start a new document, automatically correcting markup errors). 20:48:20 - third-party content generation: Web content for which a third-party author is responsible (e.g., community shared templates). 20:50:49 JT: Everyone take 2 minutes to read... 20:52:44 AL: I don't have a problem with it 20:52:48 JT: Anyone else? 20:53:20 JT: No objections heard 20:53:56 Resolution: Accept new den of content genreation (http://lists.w3.org/Archives/Public/w3c-wai-au/2012JanMar/0007.html) 20:57:37 -Sueann 20:57:38 -Alex 20:57:38 -Jeanne 20:57:39 -Cherie 20:57:41 -Greg 20:57:45 -Andrew 20:57:46 -Jutta 20:57:47 -Jan 20:57:47 WAI_AUWG()3:00PM has ended 20:57:49 Attendees were Jan, Andrew, Jutta, Alex, Greg, +1.561.582.aaaa, Sueann, Cherie, Jeanne 20:57:52 WAI_AUWG()3:00PM has now started 20:57:57 WAI_AUWG()3:00PM has ended 20:57:58 Attendees were 21:00:23 RRSAgent, make minutes 21:00:23 I have made the request to generate http://www.w3.org/2012/01/16-au-minutes.html Jan 21:00:28 RRSAgent, set logs public 21:00:34 Zakim, bye 21:00:35 Zakim has left #au 21:00:40 RRSAgent, bye 21:00:40 I see 1 open action item saved in http://www.w3.org/2012/01/16-au-actions.rdf : 21:00:40 ACTION: JR to Find a place to slot in making user settings usable in intent, examples [1] 21:00:40 recorded in http://www.w3.org/2012/01/16-au-irc#T20-46-47