Techniques for Authoring Tool Accessibility Guidelines 1.0

ATAG Checkpoint 5.1: Ensure that functionality related to accessible authoring practices is naturally integrated into the overall look and feel of the tool. [Priority 2]

• Provide a consistent look and feel, but not to the point that product differentiation and improved accessibility functionality are compromised:
  • Provide a common toolkit to design tool functionality modules (so that third party developers can add accessibility features with the same look and feel). [T????]
  • 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.[T0223]
  • The same fonts, text sizes, colors, symbols, etc. that characterize other program features should also characterize those dealing with accessibility.[T0224]
• There should be seamless integration of the accessibility functions into the workflow model of the base tool:
  • The accessibility features should be designed as integral components of the authoring tool application, not components that need to be separately executed.[T0222]
  • Include considerations for accessibility, such as short text label and long description attributes, on the same dialog as the source attribute, rather than buried behind an "Advanced..." button.[T0225]
  • The default settings of the authoring tool should include all accessible content production features enabled (as opposed to accessibility features for the author). The author may have the option to disable these features later on. [T0226]
  • 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. [T0227]

ATAG Checkpoint 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]

• 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. [T0228]
• Highlight the most accessible authoring solutions or templates when presenting choices for the author. [T0229]

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