- From: Richards, Jan <jrichards@ocadu.ca>
- Date: Mon, 5 Mar 2012 20:45:05 +0000
- To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
http://www.w3.org/2012/03/05-au-minutes.html Full text: WAI AU 05 Mar 2012 Agenda See also: IRC log Attendees Present Alex, Jan, Jeanne, Jutta, Tim_Boland, Greg, Cherie Regrets Andrew_R., Greg_P. Chair Jutta Treviranus Scribe Jan Contents Topics A.3.2.3 Conditional Proposal B.1.1.1 Conditional Proposal A.1.2.1 2. Last Call publishing planning Summary of Action Items <scribe> Scribe: Jan https://www.w3.org/2002/09/wbs/35520/atag20120229/results A.3.2.3 Conditional Proposal https://www.w3.org/2002/09/wbs/35520/atag20120229/results#xq5 A.3.2.3 Static Pointing Device Targets: If authoring tool user interface components that accept input also move, then authors can pause the movement. (Level A) A.3.2.3 Static Pointing Device Targets: If authoring tool user interface components accept input and move, then authors can pause the movement. (Level A) A.3.2.3 Static Input Components: If authoring tool user interface components accept input and move, then authors can pause the movement. (Level A) Tim: Should be consistent as possible and well defined JT: Any concerns? Resolution: All accept: "A.3.2.3 Static Input Components: If authoring tool user interface components accept input and move, then authors can pause the movement. (Level A) " B.1.1.1 Conditional Proposal http://www.w3.org/WAI/AU/2012/ED-ATAG20-20120229/#sc_b411 B.4.1.1 Features Active by Default: All accessible content support features are turned on by default. If the authoring tool provides the functionality of generating web content automatically after the end of an authoring session, authors can specify that the content be accessible web content (WCAG). A.3.2.3 handles the fact that that is default option B.1.1.1 Content Auto-Generation After Authoring Sessions (WCAG): If the authoring tool provides the functionality of generating web content automatically after the end of an authoring session, authors can specify that the content be accessible web content (WCAG). (just adding handle) Resolution: For A351All accept "If the authoring tool provides an editing-view of text-based content then editing-views enable text search, such that all of the following are true:" B.1.1.1 Content Auto-Generation After Authoring Sessions (WCAG): If the authoring tool provides the functionality of generating web content automatically after the end of an authoring session, authors can specify that the content be accessible web content (WCAG). Resolution: All accept: Resolution: All accept "If the authoring tool provides the functionality of generating web content automatically during an authoring session, then one of the following is true:" A.1.2.1 JT: minor grammatical: If the authoring tool contains non-web-based user interfaces, then the non-web-based authoring tool user interfaces follow user interface accessibility guidelines for the platform. (Level A) <scribe> ACTION: JR to Add note to clarify " I assume this would not cover keyboard commands based on the parent software? e.g. browser based keyboard controls would not need to be customized, only tool-specific controls." [recorded in http://www.w3.org/2012/03/05-au-minutes.html#action01] <trackbot> Created ACTION-373 - Add note to clarify " I assume this would not cover keyboard commands based on the parent software? e.g. browser based keyboard controls would not need to be customized, only tool-specific controls." [on Jan Richards - due 2012-03-12]. Another small one: "A.4.1.2 Settings Change Confirmation: If the authoring tool provides mechanisms for changing the user interface, then those mechanisms can reverse the changes, or the authoring tool requires author confirmation to proceed." Another small one: "B.3.1.3 Help Authors Locate: If the authoring tool provides checks that require authors to decide whether a potential web content accessibility problem is correctly identified (i.e., manual checking and semi-automated checking), then the relevant content is identified to the authors. (Level A) " JT: Seemsd we have closure on these issues... ... Which is wonderful ... Further issues 2. Last Call publishing planning JS: Next step is last call vote... GP: If vote in favour? Not in favour? JS: If not in favour: We keep working JR: Should we make the changes and then have a survey vote? JS: Explains that last call phase is the start of call for implementations ... Only after we have shown real-world implementation can we move ahead to Recommendation 'RRSAgent, make minutes Summary of Action Items [NEW] ACTION: JR to Add note to clarify " I assume this would not cover keyboard commands based on the parent software? e.g. browser based keyboard controls would not need to be customized, only tool-specific controls." [recorded in http://www.w3.org/2012/03/05-au-minutes.html#action01] -- (Mr) Jan Richards, M.Sc. jrichards@ocadu.ca | 416-977-6000 ext. 3957 | fax: 416-977-9844 Inclusive Design Research Centre (IDRC) | http://idrc.ocad.ca/ Faculty of Design | OCAD University > -----Original Message----- > From: Richards, Jan [mailto:jrichards@ocadu.ca] > Sent: March 3, 2012 11:17 PM > To: w3c-wai-au@w3.org > Subject: AUWG Teleconference on 5 March 2012 3:00pm-4:00pm ET > > There will be an AUWG teleconference on Monday 5 March 2012 at 3:00 pm - > 4:00 pm ET: > > Call: (617) 761-6200 ext. 2894# > IRC: server: irc.w3.org, port: 6665, channel: #au > > If people think they will arrive more than 15 minutes late, please send me an > email beforehand. > > The dial-in numbers for Zakim are now ONLY: > =========================================== > +1.617.761.6200 (Boston) > > > Editor Drafts: > ============== > ATAG 2.0 > http://www.w3.org/WAI/AU/2012/ED-ATAG20-20120229/ > Implementing ATAG 2.0 > http://www.w3.org/WAI/AU/2012/ED-IMPLEMENTING-ATAG20-20120229/ > > Agenda > ====== > > 1. Survey of rewordings to add conditional phrasings: > https://www.w3.org/2002/09/wbs/35520/atag20120229/ > > 2. Last Call publishing planning > > > Cheers, > Jan > > > (MR) JAN RICHARDS > PROJECT MANAGER > INCLUSIVE DESIGN RESEARCH CENTRE (IDRC) > > T 416 977 6000 x3957 > F 416 977 9844 > E jrichards@ocadu.ca > > Twitter @OCAD > Facebook www.facebook.com/OCADUniversity > > OCAD UNIVERSITY > 205 Richmond Street West, 2nd Floor, Toronto, Canada M5V 1V3 > www.ocadu.ca idrc.ocadu.ca >
Received on Monday, 5 March 2012 20:45:30 UTC