- From: Charles McCathieNevile <charles@w3.org>
- Date: Tue, 15 Dec 1998 18:35:57 -0500 (EST)
- To: Jutta Treviranus <jutta.treviranus@utoronto.ca>
- cc: w3c-wai-au@w3.org
This sounds pretty good to me. I would actually reword number 2 as follows: Where the Authoring Tool provides the functions of a browser (or other user agent), such as by offering a page preview mode or a WYSIWYG editing mode, the tool should also follow? (comply with? conform to?) the _link_W3C User Agent Guidelines_ --Charles McCathieNevile - mailto:charles@w3.org phone:(temporary) +1 (617) 258 8143 http://purl.oclc.org/net/charles W3C Web Accessibility Initiative - http://www.w3.org/WAI 545 Technology sq., Cambridge MA, USA On Tue, 15 Dec 1998, Jutta Treviranus wrote: I have been giving some thought to the reworking of the user interface section of the guidelines. I would like to add to the introduction as follows: Principles to consider in making the authoring tool accessible to authors with disabilities relate to 3 classes of functionality: 1) The authoring tool is a software program with standard user interface elements and as such should follow relevant user interface accessibility guidelines (links to TRACE guidelines, Microsoft, SUN, DACX, Apple, IBM guidelines) 2) The authoring tool frequently encompasses the functionality of a user agent or browser and as such should follow the user agent guidelines. 3) The authoring tool has unique functionality as a Web content editor. Access to this unique functionality will be addressed in these guidelines. Reactions? Jutta
Received on Tuesday, 15 December 1998 18:36:00 UTC