Techniques for Authoring Tool Accessibility

Abstract

This document is part of a series of accessibility documents published by the W3C Web Accessibility Initiative (WAI).

Status of this document

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.

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.

Please send general 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.

1 Introduction

2 Guidelines

Guideline 1. Support accessible authoring practices.

If the tool automatically generates markup, many authors will be unaware of the accessibility status of the final content unless they expend extra effort to review it and make appropriate corrections by hand. Since many authors are unfamiliar with accessibility, authoring tools are responsible for automatically generating accessible markup, and where appropriate, for guiding the author in producing accessible content.

Many applications feature the ability to convert documents from other formats (e.g., Rich Text Format) into a markup format specifically intended for the Web such as HTML. Markup changes may also be made to facilitate efficient editing and manipulation. It is essential that these processes do not introduce inaccessible markup or remove accessibility content, particularly when a tool hides the markup changes from the author's view.

Checkpoints:

1.1 Ensure that the author can produce accessible content in the markup language(s) supported by the tool. [Priority 1] (Checkpoint 1.1)

• Provide options for accessibility information to be included whenever an object is added to a document (e.g., a text equivalent for an image). Refer also to checkpoint 3.1.
• Allow direct source editing (but note also the requirements of checkpoint 1.2 and checkpoint 5.1)
• Most image formats, including PNG, SVG, WebCGM, JPEG, and GIF allow the inclusion of text content. Where it is available in the format, this feature should be used by authoring tools.
• Many formats for audio or video allow authors to include equivalent alternatives.
• An audio/video editing suite can use SMIL to synchronize audio, video, descriptive signing and text tracks.
• Reference: Web Content Accessibility Guidelines 1.0 [WCAG10] and Techniques for Web Content Accessibility Guidelines 1.0 [WCAG10-TECHS]
• Reference: The Web Accessibility Initiative has published a number of documents on the accessibility features of different W3C specifications:
  • Accessibility Features of CSS [CSS2-ACCESS]
  • Accessibility Features of SMIL [SMIL-ACCESS]
  • HTML 4.0 Accessibility Improvements [HTML4-ACCESS].
  • Accessibility of Scalable Vector Graphics [SVG-ACCESS]

  In each case the specifications themselves also provide information.

• Sample: Amaya implements all of the accessibility features of HTML. The CSS cascade order, an accessibility feature of CSS2, has not yet been completely implemented in Amaya.

1.2 Ensure that the tool preserves all accessibility information during authoring, transformations, and conversions. [Priority 1] (Checkpoint 1.2)

• When transforming a table to a list or list of lists, ensure that table headings are transformed into headings and that summary or caption information is retained as rendered content. This transformation may not be reversible.
• Even when a document's graphical layout has been rearranged, ensure that the document makes sense when rendered serially. For example, prompt the author to confirm linearized reading order after the graphical layout has changed. Desktop publishing software often has such a feature.
• When importing images with associated descriptions to an HTML document make the descriptions available through appropriate markup. For instance, in HTML use "longdesc" or "alt".
• When converting from a word-processor format to HTML, ensure that headings and list items are transformed into appropriate headings of the appropriate level, and list items in the appropriate type of list (rather than as plain text with font formatting)
• Do not transform text into images - use style sheets for presentation control, or an XML application such as Scalable Vector Graphics [SVG] that keeps the text as text. If this is not possible, ensure that the text that is converted is available as equivalent text for the image.
• Ensure that the tool recognizes and preserves elements that are defined in the relevant specification(s) even if it is unable to render them in a publishing view or preview mode. This is relevant for WYSIWYG page authoring tools, tools that handle image formats which allow the incorporation of equivalent text or data, and tools for multimedia and data-processing.
• When converting linked elements such as footnotes or endnotes either provide them as inline content or maintain two-way linking. In HTML, this should be hypertext links rather than plain-text references.
• Sample: The predefined transformations shipped with Amaya preserve all element content. The transformation language allows the preservation of attribute values, but this is not done by all the supplied transformations.

1.3 Ensure that when the tool automatically generates markup it conforms to the W3C's Web Content Accessibility Guidelines 1.0 [WCAG10]. [Relative Priority] (Checkpoint 1.3)

• Use consistent document structures. For a tool that does site-wide management, provide consistent navigation systems and document structures.
• Include markup that provides equivalent alternatives for media-dependent elements or content.
• Do not use structural markup for presentation effects, or presentation markup for known structures. For example, use list markup of an appropriate type rather than creating multiple line paragraphs and beginning each line with an image of a bullet. Do not use list markup for an indentation effect.
• Do not publish Web content in markup languages that do not allow for equivalent alternative information to be included for media-specific presentations (such as images or video, sound, etc).
• New markup languages are constantly being developed, and in many cases offer improvements to the structure and utility of Web content. In implementing a new or extended markup language, it is important to ensure that a tool does not remove access to information that had been inherent in the base markup language.

  The same can apply to a format that simplifies an existing format. For example, producing a modified HTML DTD that did not include the "alt" attribute for the IMG element, or effectively working to such a DTD by not implementing a means to include the attribute, compromises the accessibility of any included IMG elements.

• Reference: The Web Accessibility Initiative's Protocols and Formats group have a draft set of notes about creating accessible markup languages [XMLGL].
• Sample: Amaya generates markup that conforms to level-A, and allows the author to generate markup that is triple-A through the user interface.

1.4 Ensure that templates provided by the tool conform to the Web Content Accessibility Guidelines 1.0 [WCAG10]. [Relative Priority] (Checkpoint 1.4)

• Produce accessible representations for site maps generated by the authoring tool.
• Provide equivalent alternatives for all non-text content (images, audio, etc).
• Use consistent navigation mechanisms.
• Ensure that event-handlers for scripts are device-independent.
• Ensure that color schemes provide sufficient contrast for people or technology with poor color separation.
• Ensure that the natural language of the template is identified.
• Provide navigation bars.
• Provide keyboard shortcuts for important links, etc.
• Sample: Amaya has templates, which have not yet been checked for conformance to WCAG 1.0 [WCAG10].
• Some sample templates are available: (Note that these samples are still subject to review, and may require changes. Sample set one includes:
  • Main page template.
  • News and events page template
  • Page about the template site
  • Stylesheet.

Guideline 2. Generate standard markup.

Conformance with standards promotes interoperability and accessibility by making it easier to create specialized user agents that address the needs of users with disabilities. In particular, many assistive technologies used with browsers and multimedia players are only able to provide access to Web documents that use valid markup. Therefore, valid markup is an essential aspect of authoring tool accessibility.

Where applicable use W3C Recommendations, which have been reviewed to ensure accessibility and interoperability. If there are no applicable W3C Recommendations, use a published standard that enables accessibility.

Checkpoints:

2.1 Use the latest versions of W3C Recommendations when they are available and appropriate for a task. [Priority 2] (Checkpoint 2.1)

W3C specifications have undergone review specifically to ensure that they do not compromise accessibility, and where possible, they enhance it.

• When creating documents or markup languages, make full use of W3C Recommendations. For example, when creating mathematical content for the Web use MathML [MATHML] rather than another markup language. Use applicable HTML 4 [HTML4] structures.
• Specifications that become W3C Recommendations after an authoring tool's development cycles permit input are not considered "available" in time.
• Ensure that the tool recognizes and preserves elements that are defined in the relevant specification(s) even if it is unable to render them. This is particularly important for WYSIWYG editing tools.
• Sample: Amaya supports HTML 4 [HTML4], XHTML 1.0 [XHTML10], and most of CSS1 [CSS1]. It provides partial support for MathML [MATHML] and some experimental support for Scalable Vector Graphics [SVG].

2.2 Ensure that the tool automatically generates valid markup. [Priority 1] (Checkpoint 2.2)

This is necessary for user agents to be able to render Web content in a manner appropriate to a particular user's needs.

• Produce valid HTML/XML. Refer to [HTML-XML-VALIDATOR].
• Publish proprietary language specifications or DTDs on the Web, to allow documents to be validated.
• Use namespaces and schemas to make documents that can be automatically transformed to a known markup language.
• Sample: Amaya implements each language according to the published specifications.

2.3 If markup produced by the tool does not conform to W3C specifications, inform the author. [Priority 3] (Checkpoint 2.3)

• Invalid markup can be highlighted through the use of style sheets. Refer also to checkpoint 4.1.
• A tool that provides a Web editing mode and a non-Web editing mode can change modes when invalid markup is introduced. Refer also to checkpoint 4.1.
• Sample: If Amaya imports or generates markup that does not conform to W3C specifications it is highlighted in the structure view. This occurs when Amaya tries to repair invalid markup and cannot successfully do so.

Guideline 3. Support the creation of accessible content.

Well-structured information and equivalent alternative information are cornerstones of accessible design, allowing information to be presented in a way most appropriate for the needs of the user without constraining the creativity of the author. Yet producing equivalent information, such as text alternatives for images and auditory descriptions of video, can be one of the most challenging aspects of Web design, and authoring tool developers should attempt to facilitate and automate the mechanics of this process. For example, prompting authors to include equivalent alternative information such as text equivalents, captions, and auditory descriptions at appropriate times can greatly ease the burden for authors. Where such information can be mechanically determined and offered as a choice for the author (e.g., the function of icons in an automatically-generated navigation bar, or expansion of acronyms from a dictionary), the tool can assist the author. At the same time, the tool can reinforce the need for such information and the author's role in ensuring that it is used appropriately in each instance.

Checkpoints:

3.1 Prompt the author to provide equivalent alternative information (e.g., captions, auditory descriptions, and collated text transcripts for video). [Relative Priority] (Checkpoint 3.1)

Note: Some checkpoints in the Web Content Accessibility Guidelines 1.0 [WCAG10] may not apply.

• When a multimedia object is inserted, prompt the author for relevant alternatives: functional replacement and long description for images, text captions (as text or as a URI), video of signed translations for audio, and audio descriptions for video (as well as alternatives for its audio components).
• Provide an author with the option of specifying alternative information, or electing to insert null alternative information for images, audio, video. Default to an accessibility error such as no TITLE or DESC element for SVG images. Prompt the author to identify the type of image (decorative, a navigation icon, etc.).
• When video is inserted, prompt the author for a still image as part of the alternative information.
• When inserting objects such as spreadsheets or word processor documents, offer the option of providing a Web-formated version. For example, a spreadsheet or a word processor document in a proprietary format could also be published as an HTML document. Tools that dynamically generate Web content may use HTTP content negotiation to facilitate this.
• Satisfying checkpoint 3.5 would provide much of the required functionality. Refer also to checkpoint 4.1. Refer also to checkpoint 6.2..
• Sample: Amaya prompts the author to provide equivalent text for IMG and AREA elements, and CAPTION for the TABLE element.
• Some Techniques are listed below for different languages, according to Web Content Guidelines checkpoints.

WCAG Checkpoint 1.1 Provide a text equivalent for every non-text element [Priority 1]

Refer also to WCAG checkpoint 9.1 and WCAG checkpoint 13.10.

Techniques for WCAG checkpoint 1.1

HTML

• prompt for longdesc and alt for img elements
• prompt for alt for area elements
• prompt for text transcript for audio objects.
• prompt for collated text transcript for movies.

SVG

Prompt for a title and desc for each g group

SMIL

Prompt for alt, longdesc, a text or textstream object for audio, image and video objects

WCAG Checkpoint 1.2 Provide redundant text links for each active region of a server-side image map. [Priority 1]

Refer also to WCAG checkpoint 1.5 and WCAG checkpoint 9.1.

Techniques for WCAG checkpoint 1.2

HTML

• Use the same User interface for server and client side image map creations, including prompting for alternatives for each region. Use alternatives provided to generate redundant text-based links for server-side maps.
• Prompt for text which describes the range and the effect of possible coordinate entries, and generate an alternative, form-based entry system.

WCAG Checkpoint 1.3 Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation. [Priority 1]

Techniques for WCAG checkpoint 1.3

SMIL

• Prompt the author to provide an audio track that includes description, if necessary with an alternative version of the video.

WCAG Checkpoint 1.4 For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation. [Priority 1]

Techniques for WCAG checkpoint 1.4

HTML

• Use a format such as SMIL which allows for the inclusion and synchronization of equivalent tracks

XML

• Use SMIL timing to synchronize equivalents

WCAG Checkpoint 1.5 Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map. [Priority 3]

Refer also to WCAG checkpoint 1.2 and WCAG checkpoint 9.1.

Techniques for WCAG checkpoint 1.5

HTML

Use the alt associated with area elements to build a redundant text navigation bar

WCAG Checkpoint 2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup. [Priority 1]

Techniques for WCAG checkpoint 2.1

WCAG Checkpoint 2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen. [Priority 2 for images, Priority 3 for text].

Techniques for WCAG checkpoint 2.2

HTML, SVG, CSS

Where only one color has been specified (for example a background but not foreground) ask the author to specify (or confirm default) colors for other parts, where possible from a range that has sufficient contrast.

WCAG Checkpoint 3.1 When an appropriate markup language exists, use markup rather than images to convey information. [Priority 2]

Refer also to WCAG guideline 6 and WCAG guideline 11.

Techniques for WCAG checkpoint 3.1

HTML

• Where images are readable through Optical Character Recognition (OCR) as text, use text with CSS styling.

XHTML, XML

• Where images are readable through Optical Character Recognition (OCR) as text use SVG
• Where images are recognizable as mathematical content, use MathML
• Prompt the author to use a markup language for text, mathematics, etc.

WCAG Checkpoint 6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. [Priority 1]

Techniques for WCAG checkpoint 6.2

HTML

• Where scripts change the src attribute of images, prompt the author to include changes in the alt attribute or element content.

SVG, XHTML

• Where SMIL animation is used, prompt the author to ensure that desc and title elements are appropriately updated by the animation

WCAG Checkpoint 6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. [Priority 1]

Techniques for WCAG checkpoint 6.3

HTML

Ask for equivalents for scripts, and applets, for example a movie (and collated text transcripts, audio, etc)

WCAG Checkpoint 6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. [Priority 2]

Techniques for WCAG checkpoint 6.5

WCAG Checkpoint 7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. [Priority 1]

Note. People with photosensitive epilepsy can have seizures triggered by flickering or flashing in the 4 to 59 flashes per second (Hertz) range with a peak sensitivity at 20 flashes per second as well as quick changes from dark to light (like strobe lights).

Techniques for WCAG checkpoint 7.1

HTML (relying on lowsrc attribute - not in W3C recommendation)

Prompt for a non-animated "lowsrc" version of animated images.

WCAG Checkpoint 7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off). [Priority 2]

Techniques for WCAG checkpoint 7.2

WCAG Checkpoint 7.3 Until user agents allow users to freeze moving content, avoid movement in pages. [Priority 2]

When a page includes moving content, provide a mechanism within a script or applet to allow users to freeze motion or updates. Using style sheets with scripting to create movement allows users to turn off or override the effect more easily. Refer also to WCAG guideline 8.

Techniques for WCAG checkpoint 7.3

WCAG Checkpoint 8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.]

Refer also to WCAG guideline 6.

Techniques for WCAG checkpoint 8.1

WCAG Checkpoint 9.1 Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape. [Priority 1]

Refer also to WCAG checkpoint 1.1, WCAG checkpoint 1.2, and WCAG checkpoint 1.5.

Techniques for WCAG checkpoint 9.1

HTML

Use the same interface for defining areas of client- and server-side maps, and produce the image as client-side where possible

WCAG Checkpoint 11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. [Priority 2]

Techniques for WCAG checkpoint 11.1

Raster images (PNG, JPEG, GIF)

• Use RDF to incorporate textual equivalents in image encodings

Vector images

• Use SVG, and prompt the author to provide appropriate title and desc elements for each g element.

WCAG Checkpoint 11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.) [Priority 3]

Techniques for WCAG checkpoint 11.3

WCAG Checkpoint 11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page. [Priority 1]

Techniques for WCAG checkpoint 11.4

General

Note that the alternative page is required to be an accessible version, rather than simply a plain text or other partial view of the information

WCAG Checkpoint 13.2 Provide metadata to add semantic information to pages and sites. [Priority 2]

Refer also to WCAG checkpoint 13.5.

Techniques for WCAG checkpoint 13.2

Images

Metadata can be added to most image formats commonly used on the Web, including PNG, JPEG, GIF, and SVG. See the W3C Note "Describing and retrieving photos using RDF and HTTP" [[RDFPIC]].

WCAG Checkpoint 14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page. [Priority 3]

Refer also to WCAG guideline 1.

Techniques for WCAG checkpoint 14.2

HTML

Provide libraries of accessible clip art to illustrate common concepts, or allow the author to build them. See also ATAG 3.5

3.2 Help the author create structured content and separate information from its presentation. [Relative Priority] (Checkpoint 3.2)

Note: Some checkpoints in Web Content Accessibility Guidelines 1.0 [WCAG10] may not apply.

• Recognize collections of uppercase letters as likely abbreviations (in languages that have case) and prompt the author for an expansion, to be provided in markup (e.g., in HTML, with abbr or acronym).
• Prompt the author to identify the structural role of content that has been emphasized through styling.
• In Japanese, Chinese, and other appropriate languages, prompt the author for text that can be used as a ruby for unusual ideographs or ideographic groups. Refer to [RUBY].
• Prompt the author for header information for tabular data.
• Prompt the author (and allow them to specify a default suggestion) for the language of a document.
• Sample: In future releases Amaya is expected to prompt the author for "title" for ABBR, acronym, object, and IMG elements, and label for form controls. The user interface of Amaya was developed to guide authors to produce structured documents. Style in Amaya is created as a stylesheet.
• Some techniques for different languages are listed below, organized by Web Content Accessibility Guidelines checkpoints.

WCAG Checkpoint 1.1 Provide a text equivalent for every non-text element [Priority 1]

Refer also to WCAG checkpoint 9.1 and WCAG checkpoint 13.10.

Techniques for WCAG checkpoint 1.1

WCAG Checkpoint 1.2 Provide redundant text links for each active region of a server-side image map. [Priority 1]

Refer also to WCAG checkpoint 1.5 and WCAG checkpoint 9.1.

Techniques for WCAG checkpoint 1.2

HTML

Ask the author to identify regions in an image map, or to describe how the coordinates will be used so that a form-based input method can be generated.

WCAG Checkpoint 1.3 Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation. [Priority 1]

Synchronize the auditory description with the audio track as per WCAG checkpoint 1.4. Refer to WCAG checkpoint 1.1 for information about textual equivalents for visual information.

Techniques for WCAG checkpoint 1.3

WCAG Checkpoint 1.4 For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation. [Priority 1]

Techniques for WCAG checkpoint 1.4

WCAG Checkpoint 1.5 Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map. [Priority 3]

Refer also to WCAG checkpoint 1.2 and WCAG checkpoint 9.1.

Techniques for WCAG checkpoint 1.5

HTML

Use the alt associated with area elements to build a redundant text navigation bar

WCAG Checkpoint 2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup. [Priority 1]

Techniques for WCAG checkpoint 2.1

General

Prompt the author to identify a class, or markup element for uses of color.

WCAG Checkpoint 2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen. [Priority 2 for images, Priority 3 for text].

Techniques for WCAG checkpoint 2.2

WCAG Checkpoint 3.1 When an appropriate markup language exists, use markup rather than images to convey information. [Priority 2]

Refer also to WCAG guideline 6 and WCAG guideline 11.

Techniques for WCAG checkpoint 3.1

WCAG Checkpoint 3.3 Use style sheets to control layout and presentation. [Priority 2]

Techniques for WCAG checkpoint 3.3

WCAG Checkpoint 3.5 Use header elements to convey document structure and use them according to specification. [Priority 2]

Techniques for WCAG checkpoint 3.5

Text / hypertext

• Prompt the author to identify headings and subheadings
• Provide an "outline" or "structure" view which allows the author to easily grasp the heading structure, and edit it.

WCAG Checkpoint 3.6 Mark up lists and list items properly. [Priority 2]

Techniques for WCAG checkpoint 3.6

text / hypertext

• Include lists (marked as lists) in a collapsible structure view

WCAG Checkpoint 3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation. [Priority 2]

Techniques for WCAG checkpoint 3.7

HTML

Automatically include (configurable or localized) quotation marks around quotations. This will encourage authors to use the markup, and not to misuse it.

Where material appears within quote marks ask the author if this is a quotation.

WCAG Checkpoint 4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). [Priority 1]

Techniques for WCAG checkpoint 4.1

WCAG Checkpoint 4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs. [Priority 3]

Techniques for WCAG checkpoint 4.2

HTML

Ask the author to provide an expansion for abbr and acronym elements or confirm that a previously supplied one should be used again.

General

Provide a dictionary mechanism that recognizes abbreviations and prompts the author to include appropriate markup.

WCAG Checkpoint 4.3 Identify the primary natural language of a document. [Priority 3]

Techniques for WCAG checkpoint 4.3

General:

Ask the author to identify the language of any document. Provide a mechanism for setting a default.

WCAG Checkpoint 5.1 For data tables, identify row and column headers. [Priority 1]

Techniques for WCAG checkpoint 5.1

WCAG Checkpoint 5.2 For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells. [Priority 1]

For example, in HTML, use THEAD, TFOOT, and TBODY to group rows, COL and COLGROUP to group columns, and the "axis", "scope", and "headers" attributes, to describe more complex relationships among data.

Techniques for WCAG checkpoint 5.2

HTML

Ask the author to group columns, rows, or blocks of cells that are related.

WCAG Checkpoint 5.3 Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version). [Priority 2]

Refer also to WCAG checkpoint 3.3.

Techniques for WCAG checkpoint 5.3

HTML

• Prompt the author to identify tables which are used as layout devices.
• For layout tables, provide a linearized version, and offer it as a link from the table or as a replacement. An example tool which linearizes tables is tablin.

WCAG Checkpoint 5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting. [Priority 2]

Techniques for WCAG checkpoint 5.4

WCAG Checkpoint 5.5 Provide summaries for tables. [Priority 3]

Techniques for WCAG checkpoint 5.5

HTML

• In a table creation wizard, include a summary or caption dialog
• Render the caption, title and summary of a table, or prompt for content.
• Amaya's user interface guides the author to include a caption for tables,in the following way: When the author creates a table, a dialog is generated which asks for number of rows, columns, border width

  The author selects the appropriate information and a table is created. The cursor is placed at the position of the table caption. The status line, which appears at the bottom of the image, shows that the position is in the caption element of the table. (This is a standard part of the Amaya user interface).

WCAG Checkpoint 5.6 Provide abbreviations for header labels. [Priority 3]

Techniques for WCAG checkpoint 5.6

HTML

Prompt for an abbreviated form of each table header (th)

WCAG Checkpoint 6.1 Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document. [Priority 1]

Techniques for WCAG checkpoint 6.1

HTML

Provide a "draft" view which does not use styling.

WCAG Checkpoint 6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. [Priority 1]

Techniques for WCAG checkpoint 6.2

SVG

Prompt for appropriate changes to title and desc elements which are children of the target of an animate.

HTML

See also frames.

WCAG Checkpoint 6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. [Priority 1]

Refer also to WCAG guideline 1.

Techniques for WCAG checkpoint 6.3

HTML

• Prompt for server-side alternatives for scripts and applets
• Prompt for noscript content for each script.
• Prompt for alternative content for applets and programmatic objects (for example object elements which have a code attribute).

WCAG Checkpoint 6.4 For scripts and applets, ensure that event handlers are input device-independent. [Priority 2]

Refer to the definition of device independence.

Techniques for WCAG checkpoint 6.4

Applet development

• Prompt the author to include device-independent means of activation

WCAG Checkpoint 6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. [Priority 2]

Techniques for WCAG checkpoint 6.5

HTML

Ask the author for:

• appropriate links and content to include in a noframes element
• a server-side alternative to applets and script functions

WCAG Checkpoint 7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. [Priority 1]

Techniques for WCAG checkpoint 7.1

WCAG Checkpoint 7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off). [Priority 2]

Techniques for WCAG checkpoint 7.2

WCAG Checkpoint 7.3 Until user agents allow users to freeze moving content, avoid movement in pages. [Priority 2]

Refer also to WCAG guideline 8.

Techniques for WCAG checkpoint 7.3

WCAG Checkpoint 7.5 Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects. [Priority 2]

Techniques for WCAG checkpoint 7.5

WCAG Checkpoint 8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.]

Refer also to WCAG guideline 6.

Techniques for WCAG checkpoint 8.1

WCAG Checkpoint 9.1 Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape. [Priority 1]

Refer also to WCAG checkpoint 1.1, WCAG checkpoint 1.2, and WCAG checkpoint 1.5.

Techniques for WCAG checkpoint 9.1

HTML

where regions are not easily defined, ask the author to provide information that can be used to generate a form-based input method and explains how the coordinates input will be used. For example, on a map the input might be used to lookup latitude and longitude of a point and then give information about that point.

WCAG Checkpoint 9.2 Ensure that any element that has its own interface can be operated in a device-independent manner. [Priority 2]

Refer also to WCAG guideline 8.

Techniques for WCAG checkpoint 9.2

WCAG Checkpoint 9.3 For scripts, specify logical event handlers rather than device-dependent event handlers. [Priority 2]

Techniques for WCAG checkpoint 9.3

WCAG Checkpoint 9.4 Create a logical tab order through links, form controls, and objects. [Priority 3]

Techniques for WCAG checkpoint 9.4

HTML

Where there are only a few links that change in each page of a collection, ask the author if they should receive focus first. If so, then give them a tabindex, leaving the rest to after the tabindexed links have been focussed.

WCAG Checkpoint 9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. [Priority 3]

Techniques for WCAG checkpoint 9.5

HTML

Ask authors to specify an accesskey for links that appear common to a number of pages

WCAG Checkpoint 10.1 Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user. [Priority 2]

Techniques for WCAG checkpoint 10.1

HTML

Where a link or active element will spawn a new window, prompt the author for title text to make this clear.

WCAG Checkpoint 10.2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned. [Priority 2]

Refer also to WCAG checkpoint 12.4.

Techniques for WCAG checkpoint 10.2

WCAG Checkpoint 10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. [Priority 3]

Techniques for WCAG checkpoint 10.4

HTML

Prompt the author for default place-holder text. Offer the value of the name attribute as a default.

WCAG Checkpoint 10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. [Priority 3]

Techniques for WCAG checkpoint 10.5

WCAG Checkpoint 11.2 Avoid deprecated features of W3C technologies. [Priority 2]

Techniques for WCAG checkpoint 11.2

WCAG Checkpoint 11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.) [Priority 3]

Note. Use content negotiation where possible.

Techniques for WCAG checkpoint 11.3

WCAG Checkpoint 11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page. [Priority 1]

Techniques for WCAG checkpoint 11.4

WCAG Checkpoint 12.1 Title each frame to facilitate frame identification and navigation. [Priority 1]

Techniques for WCAG checkpoint 12.1

HTML

• Prompt the author for a short, human-readable title for each frame. Default text presented in the prompt could use the title defined for the document referenced in the src

WCAG Checkpoint 12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. [Priority 2]

Techniques for WCAG checkpoint 12.2

HTML

• Prompt the author for a longdesc for each frame in a frameset.
• Prompt the author to add a noframes section to the frameset. Encourage the author to include sufficient links to navigate the site, and relevant information. For example, where a frameset defines a navigation frame and a welcome page, include the content of each of these frames in the noframes.

WCAG Checkpoint 12.3 Divide large blocks of information into more manageable groups where natural and appropriate. [Priority 2]

Refer also to WCAG guideline 3.

Techniques for WCAG checkpoint 12.3

HTML

Where there are more than 10 choices in a list (select, checkbox or radio boxes) ask the author to identify subgroups

WCAG Checkpoint 12.4 Associate labels explicitly with their controls. [Priority 2]

Techniques for WCAG checkpoint 12.4

HTML

Ask authors to mark explicitly the labels for form inputs (input and textarea elements)

WCAG Checkpoint 13.1 Clearly identify the target of each link. [Priority 2]

Techniques for WCAG checkpoint 13.1

General

Prompt the author to provide text which can be used as a title for a link.

WCAG Checkpoint 13.2 Provide metadata to add semantic information to pages and sites. [Priority 2]

Refer also to WCAG checkpoint 13.5.

Techniques for WCAG checkpoint 13.2

General

Ask authors for information about a page or site. If its function is known (see also WCAG checkpoint 13.9) add this information as metadata.

WCAG Checkpoint 13.3 Provide information about the general layout of a site (e.g., a site map or table of contents). [Priority 2]

Techniques for WCAG checkpoint 13.3

General

Prompt the author to provide a link or content describing the structure of the site, and its accessibility features.

WCAG Checkpoint 13.4 Use navigation mechanisms in a consistent manner. [Priority 2]

Techniques for WCAG checkpoint 13.4

WCAG Checkpoint 13.5 Provide navigation bars to highlight and give access to the navigation mechanism. [Priority 3]

Techniques for WCAG checkpoint 13.5

WCAG Checkpoint 13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. [Priority 3]

Techniques for WCAG checkpoint 13.6

HTML

Ask authors if lists of links are a group and should be a map.

WCAG Checkpoint 13.9 Provide information about document collections (i.e., documents comprising multiple pages.). [Priority 3]

Techniques for WCAG checkpoint 13.9

General

• Pattern-matching - ask authors to specify the role of pages linked from a navigation bar.
• Where common names are used (search, home, map) as links, ask the author to confirm these functions for use in linking.

WCAG Checkpoint 13.10 Provide a means to skip over multi-line ASCII art. [Priority 3]

Refer to WCAG checkpoint 1.1 and the example of ascii art in the glossary.

Techniques for WCAG checkpoint 13.10

HTML

Where a PRE element is used with substantial punctuation and non-words, ask for text alternative.

WCAG Checkpoint 14.1 Use the clearest and simplest language appropriate for a site's content. [Priority 1]

Techniques for WCAG checkpoint 14.1

General

• Provide readability ratings for text.
• Provide a thesaurus function
• Provide a grammar-checking function

WCAG Checkpoint 14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page. [Priority 3]

Refer also to WCAG guideline 1.

Techniques for WCAG checkpoint 14.2

3.3 Ensure that prepackaged content conforms to the Web Content Accessibility Guidelines 1.0 [WCAG10]. [Relative Priority] (Checkpoint 3.3)

For example, include captions, an auditory description, and a collated text transcript with prepackaged movies. Refer also to checkpoint 3.4.

• Use formats that allow for accessible annotation to be included in the files, such as SMIL, PNG, and SVG.
• Provide long descriptions, and associated text files with appropriate text equivalent in clip-art collections.
• Provide video description files with prepackaged video.
• Provide text caption files for prepackaged audio, or video with auditory track(s).
• Including pre-written descriptions for all multimedia files (e.g., clip-art) packaged with the tool will save authors time and effort, cause a significant number of professionally written descriptions to circulate on the Web, provide authors with convenient models to emulate when they write their own descriptions, and show authors the importance of description writing.
• Refer also to checkpoint 3.5.
• Sample: Amaya does not provide any clip art or other prepackaged content.

3.4 Do not automatically generate equivalent alternatives. Do not reuse previously authored alternatives without author confirmation, except when the function is known with certainty. [Priority 1] (Checkpoint 3.4)

For example, prompt the author for a text equivalent of an image. If the author has already provided a text equivalent for the same image used in another document, offer to reuse that text and prompt the author for confirmation. If the tool automatically generates a "Search" icon, it would be appropriate to automatically reuse the previously authored text equivalent for that icon. Refer also to checkpoint 3.3 and checkpoint 3.5.

Note: Human-authored equivalent alternatives may be available for an object (for example, through checkpoint 3.5 and/or checkpoint 3.3). It is appropriate for the tool to offer these to the author as defaults.

• Items used throughout a Website, such as graphical navigation bars, should have standard alternative information. However the author should be prompted to edit or approve this the first time it is used in a site, and when the destination of the links is changed by the author.
• If the author has not specified alternative text for an IMG, or specified that none is required, default to having no "alt" attribute, so that an accessibility problem will be noted. Refer also to checkpoint 4.1.
• Where an object has already been used in a document, the tool should offer the alternative content that was supplied for the first or most recent use as a default.

3.5 Provide functionality for managing, editing, and reusing alternative equivalents for multimedia objects. [Priority 3] (Checkpoint 3.5)

Note: These alternative equivalents may be packaged with the tool, written by the author, retrieved from the Web, etc.

• Maintain a database registry that associates object identity information with alternative information. Whenever an object is used and an equivalent alternative is provided, ask the author whether they want to add the object (or identifying information) and the alternative information to the database. In the case of a text equivalent, the alternate information may be stored in the document source. For more substantial information (such as video captions or audio descriptions), the information may be stored externally and linked from the document source. Allow different alternative information to be associated with a single object.
• Reference: >Allow authors to make keyword searches of a description database (to simplify the task of finding relevant images, sound files, etc.). A paper describing a method to create searchable databases for video and audio files is available (refer to [SEARCHABLE]).
• Suggest pre-written descriptions as default text whenever one of the associated files is inserted into the author's document.
• The use of the Resource Description Framework (RDF) [RDF10], or formats like SVG can enable a tool to maintain and use libraries of information within the tool and on the Web.
• This checkpoint is priority 3, meaning that in itself, it does not have a critical effect on an authoring tool's likelihood of producing accessible mark-up. However, certain implementations of this Alternative Information Management Mechanism (AIMM) [APROMPT] have the potential to simultaneously satisfy several higher priority checkpoints and dramatically improve the usability of an access aware authoring tool. In particular:
  1. The AIMM [APROMPT] should maintain a list of associations between object file names and authored responses to prompts for alternative information (per checkpoint 3.1). The alternative information may take the form of short strings (i.e., "alt"-text) or pointers to descriptive files (i.e., "longdesc", transcripts, etc.). Multiple associations for the same object for different languages or contexts should also be handled.
  2. The AIMM [APROMPT] would offer the associated alternative information as a default whenever the appropriate associated object is selected for insertion. If no previous association is found, the field should be left empty (i.e., no purely rule-generated alternative information should be used). Note: The term "default" implies that the alternative information is offered for the author's approval. The term does not imply that the default alternative information is automatically placed without the author's approval. Such automatic placement may only occur when in situations where the function of the object is known with certainty, per checkpoint 3.4. Such a situation might arise in the case of a "navigation bar builder" that places a navigation bar at the bottom of every page on a site. In this case, it would be appropriate to use the same "alt"-text automatically for every instance of a particular image (with the same target) on every page.
  3. The alternative information mechanism should be closely integrated with the pre-written alternative information provided for all packaged multimedia files, per checkpoint 3.3. This would allow the alternative information to be automatically retrieved whenever the author selected one of the packaged objects for insertion. An important benefit of the system would be the ease of adding a keyword search capability that would allow efficient location of multimedia based on its alternative information.

Guideline 4. Provide ways of checking and correcting inaccessible content.

Many authoring tools allow authors to create documents with little or no knowledge about the underlying markup. To ensure accessibility, authoring tools must be designed so that they can (where possible, automatically) identify inaccessible markup, and enable its correction even when the markup itself is hidden from the author.

Authoring tool support for the creation of accessible Web content should account for different authoring styles. Authors who can configure the tool's accessibility features to support their regular work patterns are more likely to accept accessible authoring practices (refer to guideline 5). For example, some authors may prefer to be alerted to accessibility problems when they occur, whereas others may prefer to perform a check at the end of an editing session. This is analogous to programming environments that allow users to decide whether to check for correct code during editing or at compilation.

Note: Validation of markup is an essential aspect of checking the accessibility of content.

Checkpoints:

4.1 Check for and inform the author of accessibility problems. [Relative Priority] (Checkpoint 4.1)

Note: Accessibility problems should be detected automatically where possible. Where this is not possible, the tool may need to prompt the author to make decisions or to manually check for certain types of problems.

• Reference: The WAI Evaluation and Repair group [WAI-ER] is developing a document that discusses detailed techniques for testing content according to the Web Content Accessibility Guidelines. A draft of that document is available [AUTO-TOOL].
• Where the tools cannot test for accessibility errors, provide the author with the necessary information, wizards, etc. to check for themselves. Refer also to checkpoint 5.1.
• Include alerts for WCAG 1.0 [WCAG10] Priority 1 checkpoints in the default configuration.
• Provide an editing view that shows equivalent alternatives in the main content view to make it clear that they are necessary. This will make it obvious when they are missing.
• Provide a preview mode that uses alternative content. Although this can give authors a clear understanding of some problems very easily, it should be made clear that there are many ways in which a page may be presented (aurally, text-only, text with pictures separately, on a small screen, on a large screen, etc.). A view that renders the document as it might appear without technologies such as style sheets and images enabled, or the ability to turn those features off and on in the editing view, will also give an author some idea of whether a document's logical order has been correctly preserved, whether alternative text is appropriate, etc.
• Highlight problems detected when documents are opened, when an editing or insertion action is completed, or while an author is editing. Using CSS classes to indicate accessibility problems will enable the author to easily configure the presentation of errors.
• Where there is a change in the writing script used, prompt the author to identify whether there has been a change in language
• Alert authors to accessibility problems when saving.
• Accessibility problems can be highlighted using strategies similar to spell checking within a word processor. Accessibility alerts within the document can be linked to context sensitive help. Refer also to checkpoint 4.2..
• Allow authors to choose different alert levels based on the priority of authoring accessibility recommendations.
• If interruptive warnings are used, provide a means for the author to quickly set the warning to non-obtrusive to avoid frustration.
• Reference: There are online tools whose output can be integrated with the user interface. Other tools are available for incorporation in existing software, either as licensed products or in some cases as "open source" solutions. The WAI Evaluation and Repair group maintains information about available tools [WAI-ER].
• Reference: Refer also to the WAI accessibility references listed in techniques for Refer also to checkpoint 1.1..
• Reference: The Web Accessibility Initiative's Protocols and Formats group have a draft set of notes about creating accessible markup languages [XMLGL].
• Sample: Amaya currently checks for validity, but the only warning of invalid markup appears in the structure view. The Amaya developers are investigating automating an accessibility check and author notification. Where Amaya detects an error, it identifies and highlights the incorrect code in the structure view, allowing the author to delete it.

4.2 Assist authors in correcting accessibility problems. [Relative Priority] (Checkpoint 4.2)

At a minimum, provide context-sensitive help with the accessibility checking required by checkpoint 4.1

• Reference: The WAI Evaluation and Repair group [WAI-ER] is developing a document that discusses detailed techniques for repairing accessibility errors in content according to the Web Content Accessibility Guidelines. A draft of that document is available [AUTO-TOOL].
• Assist authors in ways that are consistent with the look and feel of the authoring tool.
• Provide context sensitive-help for accessibility errors. Refer also to guideline 6.
• Where there are site-wide errors, to make correction more efficient, allow the author to make site-wide changes or corrections. For example, this may be appropriate for a common error in markup, but may not be appropriate in providing a text equivalent that is appropriate for one use of an image but completely inappropriate for the other uses of the image on the same site (or even the same page).
• Allow authors to control both the nature and timing of the correction process.
• Provide a mechanism for authors to navigate sequentially among uncorrected accessibility errors Refer also to checkpoint 7.4..
• Possible implementation strategy: Where there are errors in a document Amaya could alert the author and warn that the document must be changed, and present the structure view highlighting areas where it has changed the markup, allowing the author to abort the editing session or save the changed version under a new name.

4.3 Allow the author to preserve markup not recognized by the tool. [Priority 2] (Checkpoint 4.3)

Note: The author may have included or imported markup that enhances accessibility but is not recognized by the tool.

• Provide a summary of all automated structural changes that may affect accessibility.
• Provide options for the author to confirm or override removal of markup on a change-by-change basis or as a batch process.
• If changes to the markup are necessary for the tool to further process the document (for example, a tool that requires valid markup when a document is opened), inform the author.
• Do not change the DTD without notifying the author.

4.4 Provide the author with a summary of the document's accessibility status. [Priority 3] (Checkpoint 4.4)

• Provide a list of all accessibility errors found in a Web page.
• Provide a summary of accessibility problems remaining by type and/or by number.

4.5 Allow the author to transform presentation markup that is misused to convey structure into structural markup, and to transform presentation markup used for style into style sheets. [Priority 3] (Checkpoint 4.5)

• Some examples of transformations include: HTML table-based layout into CSS, HTML BR to the P element, HTML (deprecated) FONT into heuristically or author-determined structure, Word processor styles to Web styles, HTML deprecated presentational markup into CSS, XHTML span into ruby, MathML presentational markup to semantic markup.
• Allow the author to define transformations for imported documents that have presentation, rather than structural, markup.
• Allow the author to create style rules based on the formatting properties of an element, and then apply the rule to other elements in the document, to assist conversion of documents to the use of style sheets
• Include pre-written transformations to rationalize multiple tables, and to transform (deprecated) presentation HTML into style sheets.
• Remember that accessibility information, including attributes or properties of the elements being transformed, must be preserved - see checkpoint 1.2
• Sample: Amaya provides a language for specifying structure transformations, and a large number of predefined transformations are included.

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

When a new feature is added to an existing software tool without proper integration, the result is often an obvious discontinuity. Differing color schemes, fonts, interaction styles, and even software stability can be factors affecting author acceptance of the new feature. In addition, the relative prominence of different ways to accomplish the same task can influence which one the author chooses. Therefore, it is important that creating accessible content be a natural process when using an authoring tool.

Checkpoints:

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)

• 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.
• The same fonts, text sizes, colors, symbols, etc. that characterize other program features should also characterize those dealing with accessibility.
• 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.
• 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.
• 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
• 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.
• A help page that describes how to make an HTML image map should include adding alternative information for each AREA element in the MAP as part of the process. Any examples of code should give either block content with text links, or AREA elements that all have relevant "alt" attribute values.
• When an author creates an HTML frameset, suggest the links from the navigation bar (and perhaps the content of the "first page") as the content for the NOFRAMES element.
• Sample: In Amaya some accessibility features are part of relevant dialogs. Others, such as longdesc and title attributes must be separately generated by the author. The development team will integrate these into the relevant dialogues in future releases.

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)

• When the author has selected text to format, the use of CSS should be emphasized rather than the (deprecated) HTML FONT element.
• Highlight the most accessible solutions when presenting choices for the author.
• Providing an editing view that shows equivalent alternatives in the main content view will make it clear that they are necessary, and will make it obvious when they are missing.
• 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 requesting equivalent alternatives for an image with the HTML OBJECT element, offer an unchecked option for a null value (i.e., there is no content, implying the image has no real function) with the cursor positioned in the entry field for alternative text (and, if available, provide the appropriate value from the "Alternative Information Management Mechanism"; refer to checkpoint 3.5) rather than offering the filename as a default suggestion, or selecting the null "alt" value as a default.
• Sample: Amaya's user interface guides the author to produce structured content, with presentation elements separated into style sheets. Providing an equivalent alternative is mandatory at the time of inserting some elements.

Guideline 6. Promote accessibility in help and documentation.

Web authors may not be familiar with accessibility issues that arise when creating Web content. Therefore, help and documentation must include explanations of accessibility problems, and should demonstrate solutions with examples.

Checkpoints:

6.1 Document all features that promote the production of accessible content. [Priority 1] (Checkpoint 6.1)

• Ensure that accessibility solutions are present in all help text descriptions of markup practices (e.g., HTML IMG elements should appear with an "alt" attribute and a "longdesc" attribute wherever appropriate).
• Ensure that electronic documentation complies with the Web Content Accessibility Guidelines 1.0 [WCAG10]
• Link from help text to any automated correction utilities.
• Provide examples of accessible design practices in online tutorials.
• Include help documentation for all accessible authoring practices supported by the tool.
• Link those mechanisms used to identify accessibility problems (e.g., icons, outlining or other emphasis within the user interface) to help files.
• Sample: Amaya help pages for images and image maps [AMAYA-HELP-IMG] include providing text alternatives as part of the process. There is a help page on configuring Amaya, that documents how to change the default keyboard bindings.

6.2 Ensure that creating accessible content is a naturally integrated part of the documentation, including examples. [Priority 2] (Checkpoint 6.2)

• In help text, when explaining the accessibility issues related to non-deprecated elements, emphasize appropriate solutions rather than explicitly discouraging the use of the element.
• Explain the importance of utilizing accessibility features generally and for specific instances.
• Take a broad view of accessibility-related practices; for example, do not refer to text equivalents as being "for blind authors" but rather as "for authors who are not viewing images".
• Avoid labelling accessibility features of the tool with a "handicapped" icon, as this can give the impression that accessible design practices only benefit disabled authors.
• In help text, emphasize accessibility features that benefit multiple groups. In particular the principles of supporting flexible display and control choices have obvious advantages for the emergence of hands free, eyes-free, voice-activated browsing devices such as Web phone, the large number of slow Web connections, and Web users who prefer text-only browsing to avoid "image clutter".
• Provide examples of all accessibility solutions in help text, including those of lower priority in WCAG 1.0 [WCAG10].
• Implement context-sensitive help for all special accessibility terms as well as tasks related to accessibility.
• Document the tool's conformance to ATAG 1.0 [ATAG10].
• Include current versions of, or links to relevant specifications in the documentation (e.g. HTML 4 [HTML4], CSS [CSS2].) This is particularly relevant for markup languages that are easily hand edited, such as most XML languages [XML].
• Include a tutorial specifically on checking for and correcting Web accessibility problems.
• Link to or provide URIs for more information on accessible Web authoring, such as WCAG 1.0 [WCAG10], and other accessibility-related resources.
• Ensure that documentation examples conform to WCAG 1.0 [WCAG10], at least to the level that the tool conforms to ATAG 1.0 [ATAG10].
• Clearly label any examples that display practices that reduce accessibility.
• Sample: Accessible authoring features are added to the documentation as they are incorporated into Amaya, as part of the normal documentation of the relevant feature.

6.3 In a dedicated section, document all features of the tool that promote the production of accessible content. [Priority 3] (Checkpoint 6.3)

• Sample: Amaya documentation has a basic accessibility section, which is an option in Amaya's help menu.

Guideline 7. Ensure that the authoring tool is accessible to authors with disabilities.

The authoring tool is a software program with standard user interface elements and as such must be designed according to relevant user interface accessibility guidelines. When custom interface components are created, it is essential that they be accessible through the standard access mechanisms for the relevant platform so that assistive technologies can be used with them.

Some additional user interface design considerations apply specifically to Web authoring tools. For instance, authoring tools must ensure that the author can edit (in an editing view) using one set of stylistic preferences and publish using different styles. Authors with low vision may need large text when editing but want to publish with a smaller default text size. The style preferences of the editing view must not affect the markup of the published document.

Authoring tools must also ensure that the author can navigate a document efficiently while editing, regardless of disability. Authors who use screen readers, refreshable braille displays, or screen magnifiers can make limited use (if at all) of graphical artifacts that communicate the structure of the document and act as signposts when traversing it. Authors who cannot use a mouse (e.g., people with physical disabilities or who are blind) must use the slow and tiring process of moving one step at a time through the document to access the desired content, unless more efficient navigation methods are available. Authoring tools should therefore provide an editing view that conveys a sense of the overall structure and allows structured navigation.

Note: Documentation, help files, and installation are part of the software and need to be available in an accessible form.

Checkpoints:

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). (Checkpoint 7.1)

The techniques for this checkpoint include references to checklists and guidelines for a number of platforms and to general guidelines for accessible applications.

• Not all of the guidelines and checklists for application accessibility are prioritized according to their impact on accessibility. For instance, the priorities in "The Microsoft Windows Guidelines for Accessible Software Design" [MS-SOFTWARE] are partially determined by a logo requirement program. Therefore developers may need to compare the documents they are using to other guidelines. WCAG 1.0 [WCAG10] and UAAG 1.0 [UAAG10] both have priority systems that are directly compatible with the priorities in [ATAG10].
• User Interfaces are sometimes built as Web content, and, as such, should follow the Web Content Accessibility Guidelines 1.0 [WCAG10]. Refer also to guideline 1.
• Guidelines for specific platforms include
  1. Reference: "IBM Guidelines for Writing Accessible Applications Using 100% Pure Java" [JAVA-ACCESS] R. Schwerdtfeger, IBM Special Needs Systems.
  2. Reference: "An ICE Rendezvous Mechanism for X Window System Clients" [ICE-RAP], W. Walker. A description of how to use the ICE and RAP protocols for X Window clients.
  3. Reference: "Information for Developers About Microsoft Active Accessibility" [MSAA] Microsoft Corporation.
  4. Reference: "The Inter-Client communication conventions manual" [ICCCM]. A protocol for communication between clients in the X Window system.
  5. Reference: "Lotus Notes accessibility guidelines" [NOTES-ACCESS] IBM Special Needs Systems.
  6. Reference: "Java accessibility guidelines and checklist" [JAVA-CHECKLIST] IBM Special Needs Systems.
  7. Reference: "The Java Tutorial. Trail: Creating a GUI with JFC/Swing" [JAVA-TUT]. An online tutorial that describes how to use the Swing Java Foundation Class to build an accessible User Interface.
  8. Reference: "Macintosh Human Interface Guidelines" [APPLE-HI] Apple Computer Inc.
  9. Reference: "The Microsoft Windows Guidelines for Accessible Software Design"