- From: Jan Richards <jan.richards@utoronto.ca>
- Date: Mon, 02 May 2005 16:43:12 -0400
- To: "List (WAI-AUWG)" <w3c-wai-au@w3.org>
Minutes of Teleconference (2 May 2005) (also see: http://jan.atrc.utoronto.ca/public/auwg/guidelines.html where work assignment as indicated in-line) Present: Jan Richards JR Matt May MM Tim Boland TB Greg Pisocky GP JR: It would also be good to send a signal to the W3C community that we have pulled back from RC and another working draft. Publishing moratorium for a Working Draft is June 1, 2005 JR: Guideline 1 items were added. Now are changes that initiated like numbering. Conformance had to be moved above the guidelines. New conformance scheme that was proposed last week has now been added. A lot of the changes are editorial changes, or removing the ISO 16071 references. JR: Getting down to the guidelines.... GP: I think we need to put a boundary around browser access functionality JR: Good point. This remains an open issue. Could we leave it at that. If anyone wants to make proposals on any of this stuff , feel free. JR: Next, Author Profile functionality. Allow people to choose between configurations. JR: Ensure that documentation is accessible. GP: I will take that. JR: THere is a similar checkpoint in the UAAG JR: Next is preview function accessible JR: I will take that one distinguish between the interface around the preview window but not necessarily what is inside the preview window JR: Now into Guideline A1 JR: A.1.1. A.1.1 Provide text alternatives for all non-text content in the user interface @@ensure preview rendered view out clause is in the defn of user interface TB: I can take a look at that JR: A.1.2 Provide synchronized alternatives for multimedia. TB: I can do that too. JR: Just putting you down for the rationale for those. JR: A.1.3 Ensure that the visual presentation is configurable. [@@add success criteria on foreground/background distinguishability] JT-to propose - user interface JR: Barry will be proposing success criteria for A.1.7 JR: A.1.3 Ensure that the visual presentation is configurable. [@@add success criteria on foreground/background distinguishability] JT-to propose - user interface GP I will do A.2.2 Rationale A.2.2 Make all functionality operable via a keyboard or a keyboard interface. [Priority 1] JR A.2.3 Allow authors to control time limits on their reading or interaction. [Priority ?] TB A.2.4 I can do that JR A.2.5 is an existing one, I will look it up and just use that. JR: A.2.6 Allow the author to search content and markup within the editing views. I'll drop that in JR I can do A.2.7 Undo JR: A.2.8 Separate selection from activation Volunteers? I can do it JR: On to A.3.1 A.3.1 Observe operating environment conventions for the authoring tool user interface, documentation, input configurations, and installation. [Priority ?] Anyone take a shot GP: Rationale and Success criteria, I will give it a shot. JR: A.3.2 Organize content consistently from "page to page" and make interactive components behave in predictable ways.@@"Maintain consistency within the authoring tool user interface."@@ [Priority ?] I will do this. JR: Jutta will propose something about individual conventions. TB: I can do A.3.4 JR: Last one is pretty quick A.4.1 Support interoperability with assistive technologies. [Priority 1]. THis would come straight from WCAG, I can do this one. -- Jan Richards, M.Sc. User Interface Design Specialist Adaptive Technology Resource Centre (ATRC), University of Toronto Email: jan.richards@utoronto.ca Web: http://jan.atrc.utoronto.ca Phone: 416-946-7060 Fax: 416-971-2896
Received on Monday, 2 May 2005 20:44:24 UTC