[ contents of this page ] [ full contents ] [ next: implementation techniques for guideline 1 ]
Copyright ©1999 - 2002 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C.
This document is published as an informative appendix to the Authoring Tool Accessibility Guidelines. The document represents an attempt to make it clearer how to use the techniques for different types of tools.
For further information about Working Group decisions, please consult the minutes of AUWG Meetings.
This document has been produced by the Authoring Tool Accessibility Guidelines Working Group (AUWG) as part of the Web Accessibility Initiative (WAI). The goals of the Working Group are discussed in the AUWG charter. The AUWG is part of the WAI Technical Activity.
Please send comments about this document to the public mailing list: w3c-wai-au@w3.org (public archives).
A list of current W3C Recommendations and other technical documents including Working Drafts and Notes can be found at http://www.w3.org/TR.
This document has been divided into a multi-part hypertext document to keep individual pages to a manageable size. There are publishing conventions used to identify various features and parts of the document. Some of these will be used to provide multiple views of the techniques - for example implementation techniques for a particular kind of tool, or references for particular techniques. Other conventions are used to ensure that this document is compatible with ATAG version 1.0 or will be compatible with ATAG wombat with a minimum of difficulty or change.
Note on applicability of techniques: The following techniques are applicable to all kinds of authoring tools, including those that are insertable components of other authoring tools. For example, if an authoring tool for designing on-line courses (courseware) has a prefabricated chat facility that the instructor can drag onto their page, this component must comply with all the techniques for accessible output (guidelines 1-6) and accessible user interface (guideline 7).
Note: For the purposes of these techniques, authoring tools may fall into one or more of the following categories. For example, an HTML authoring tool that allows the user to create JavaScript will fall under two categories, Markup Editing Tools and Programming Tools. A SMIL editor that includes a text-only view of the markup and a preview mode would be considered both a Markup Editing Tool and a Multimedia Creation Tool.
This draft is accompanied by a version without icons.