[] [contents of this page] [full techniques contents] [next chapter: implementation techniques for guideline 6]

W3C

Techniques for Authoring Tool Accessibility Guidelines 1.0

Working Draft 1 August 2001

Section 5: implementation techniques for guideline 5

This version:
http://www.w3.org/WAI/AU/WD-ATAG10-TECHS-20010801/imp5
Latest version:
http://www.w3.org/WAI/AU/ATAG10-TECHS/imp5

editor of this chapter:

Gregory Rosmaita


Brief table of contents


Guideline 5. Integrate accessibility solutions into the overall "look and feel".

ATAG 5.1 Ensure that functionality related to accessible authoring practices is naturally integrated into the overall look and feel of the tool. [Priority 2] (Checkpoint 5.1)
Markup tools technique Multimedia tools technique Content tools technique Programming tools technique The accessibility features should be designed as integral components of the authoring tool application, not plug-ins or other peripheral components that need to be separately obtained, installed, configured or executed.[Required] @@
Markup tools technique Multimedia tools technique Content tools technique Programming tools technique Ensure that author can utilize the tool's accessible authoring features by the same interaction styles used for other features in the program. For example, if the tool makes use of onscreen symbols such as underlines or coloration change rather than dialogs for conveying information, then the same interface techniques should be used to convey accessibility information.[Required] @@
Markup tools technique Multimedia tools technique Content tools technique Programming tools technique The same fonts, text sizes, colors, symbols, etc. that characterize other program features should also characterize those dealing with accessibility.[Required] @@
Markup tools technique Multimedia tools technique Include considerations for accessibility - such as the "alt" and "longdesc" attributes of the HTML IMG element - right below the "src" attribute in a dialogue box, not buried behind an "Advanced..." button.[Required] @@
Markup tools technique Multimedia tools technique Content tools technique Programming tools technique The default installation of the authoring tool should include all accessibility features enabled. The author may have the option to disable these features later on.[Required] @@
Markup tools technique Multimedia tools technique Content tools technique Programming tools technique Allow efficient and fast access to accessibility-related settings with as few steps as possible needed to make any changes that will generate accessible content.(Suggested)
ATAG 5.2 Ensure that accessible 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] (Checkpoint 5.2)
Markup tools technique Multimedia tools technique Content tools technique Programming tools technique If there is more than one option for the author, and one option is more accessible than another, place the more accessible option first and make it the default. For example, when the author has selected text to format, the use of CSS should be emphasized rather than deprecated FONT element.[Required] @@
Markup tools technique Multimedia tools technique Content tools technique Programming tools technique Highlight the most accessible solutions when presenting choices for the author.(Suggested)
Markup tools technique Multimedia tools technique Content tools technique Programming tools technique Provide an editing view that shows equivalent alternatives in the main content view to make it clear that they are necessary, and will make it obvious when they are missing.(Suggested)

[previous section] [top of this page] [full techniques contents] [next