Movatterモバイル変換

For further information about Working Group decisions, please consult theminutes ofAUWGMeetings.

This document has been produced by theAuthoring Tool Accessibility GuidelinesWorking Group (AUWG)as part of theWeb Accessibility Initiative(WAI). The goals of theWorking Group are discussed in theAUWG charter. The AUWG is part of theWAI 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 documentsincluding Working Drafts and Notes can be found athttp://www.w3.org/TR/.

Introduction

How this document is organized

This document has been divided into a multi-part hypertext document tokeep individual pages to a manageable size. There are publishing conventionsused to identify various features and parts of the document. Some of thesewill be used to provide multiple views of the techniques - for exampleimplementation techniques for a particular kind of tool, or references forparticular techniques. Other conventions are used to ensure that thisdocument is compatible with ATAG version 1.0 or will be compatible with ATAGwombat with a minimum of difficulty or change.

Applicability oftechniques

Note on applicability of techniques: The followingtechniques are applicable to all kinds of authoring tools, including thosethat are insertable components of other authoring tools. For example, if anauthoring tool for designing on-line courses (courseware) has a prefabricatedchat facility that the instructor can drag on to their page, this componentmust comply with all the techniques for accessible output (guidelines 1-6)and accessible user interface (guideline 7).

Authoring tool categories

Note: Many checkpoints may not apply to a given category of authoring tool (e.g., markup tools, but not multimedia tools). Each section contains a link to a version with icons representing relevant tool categories for each checkpoint. These versions can be viewed by selecting the "turn on icons" link found at the top of each section.

Implementation techniques byguideline and checkpoint

1. Support accessible authoring practices:
   • Techniques for checkpoint 1.1: Ensure that the author can produceaccessible content in themarkup language(s) supported by the tool.[Priority 1]
   • Techniques for checkpoint 1.2: Ensure that the tool preserves allaccessibility information during authoring,transformations, andconversions.[Priority 1]
   • Techniques for checkpoint 1.3: Ensure that when the tool automatically generates markup it conforms to theW3C's Web Content Accessibility Guidelines 1.0[WCAG10].[Relative Priority]
   • Techniques for checkpoint 1.4:Ensure that templates provided by the tool conform to the Web Content Accessibility Guidelines 1.0[WCAG10].[Relative Priority]
2. Generate standard markup:
   • Techniques for checkpoint 2.1: Use the latest versions ofW3C Recommendations when they are available and appropriate for a task.[Priority 2].
   • Techniques for checkpoint 2.2: Ensure that the tool automatically generates valid markup.[Priority 1]
   • Techniques for checkpoint 2.3: If markup produced by the tool does not conform to W3C specifications,inform the author.[Priority 3
3. Support the creation of accessible content:
   • Techniques for checkpoint 3.1:Prompt the author to provideequivalent alternative information (e.g.,captions,auditory descriptions, andcollated text transcripts for video).[Relative Priority]
   • Techniques for checkpoint 3.2: Help the author create structured content and separate information from its presentation.[Relative Priority]
   • Techniques for checkpoint 3.3: Ensure that prepackaged content conforms to the Web Content Accessibility Guidelines 1.0[WCAG10].[Relative Priority]
   • Techniques for checkpoint 3.4: Do not automatically generateequivalent alternatives. Do not reuse previously authored alternatives without author confirmation, except when the function is known with certainty.[Priority 1]
   • Techniques for checkpoint 3.5: Provide functionality for managing, editing, and reusingalternative equivalents for multimedia objects.[Priority 3]
4. Provide ways of checking and correcting inaccessible content:
   • Techniques for checkpoint 4.1:Check for andinform the author ofaccessibility problems.[Relative Priority]
   • Techniques for checkpoint 4.2: Assist authors in correctingaccessibility problems.[Relative Priority]
   • Techniques for checkpoint 4.3: Allow the author to preserve markup not recognized by the tool.[Priority 2]
   • Techniques for checkpoint 4.4: Provide the author with a summary of the document's accessibility status.[Priority 3]
   • Techniques for checkpoint 4.5: Allow the author to transformpresentation markup that is misused to convey structure intostructural markup, and to transform presentation markup used for style into style sheets.[Priority 3]
5. Integrate accessibility solutions into the overall "look and feel":
   • Techniques for checkpoint 5.1:Ensure that functionality related toaccessible authoring practices is naturally integrated into the overall look and feel of the tool.[Priority 2]
   • Techniques for checkpoint 5.2:Ensure thataccessible authoring practices supporting Web Content Accessibility Guidelines 1.0[WCAG10] Priority 1 checkpoints are among the most obvious and easily initiated by the author.[Priority 2]
6. Promote accessibility in help and documentation:
   • Techniques for checkpoint 6.1: Document all features that promote the production of accessible content.[Priority 1]
   • Techniques for checkpoint 6.2: Ensure that creating accessible content is a naturally integrated part of the documentation, including examples.[Priority 2]
   • Techniques for checkpoint 6.3: In a dedicated section, document all features of the tool that promote the production of accessible content.[Priority 3]
7. Ensure that the authoring tool is accessible to authors with disabilities:
   • Techniques for checkpoint 7.1: Use all applicable operating system and accessibility standards and conventions [Priority 1 for standards and conventions that are essential to accessibility; Priority 2 for those that are important to accessibility; Priority 3 for those that are beneficial to accessibility].
   • Techniques for checkpoint 7.2: Allow the author to change the presentation withinediting views without affecting the document markup.[Priority 1]
   • Techniques for checkpoint 7.3: Allow the author to edit allproperties of eachelement and object in an accessible fashion.[Priority 1]
   • Techniques for checkpoint 7.4: Ensure that theediting view allows navigation via the structure of the document in an accessible fashion.[Priority 1]
   • Techniques for checkpoint 7.5: Enable editing of the structure of the document in an accessible fashion.[Priority 2]
   • Techniques for checkpoint 7.6: Allow the author to search withinediting views.[Priority 2]