Techniques for Authoring Tool Accessibility Guidelines 1.0

Checkpoints:

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

T0231 Ensure that the help system of the tool can answer the questions: "What features does this tool have to encourage the production of accessible content?" and "How are these used?".[Required] @@

T0232 Link from help text to any automated correction utilities.(Suggested)

T0233 Link those mechanisms to identify accessibility problems (i.e., icons, outlining or other emphasis within the user interface) to help files.(Suggested)

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

T0234 Always include accessibility-related practices in every example for which one would be required, regardless of whether the example is meant to emphasize this or not (e.g., HTML IMG elements should appear with an alt attribute and a longdesc attribute wherever appropriate).[Required] @@

T0235 Provide examples of all accessibility solutions in help text, including those of lower priority in WCAG 1.0 [WCAG10].[Required] @@

Writing Accessibility Rationale (Suggested):

• T0236 Ensure that documentation examples conform to WCAG 1.0 [WCAG10], at least to the level that the tool conforms to ATAG 1.0 [ATAG10].
• T0237 Explain the importance of utilizing accessibility features generally and for specific instances.
• T0238 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".
• T0239 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".

Explaining Accessibility (Suggested):

• T0240 When explaining the accessibility issues related to non-deprecated elements, emphasize appropriate solutions rather than explicitly discouraging the use of the element.
• T0241 Avoid labeling accessibility features of the tool with a "handicapped" icon, as this can give the impression that accessible design practices only benefit disabled authors.

Context Sensitive Help (Suggested):

• T0242 For tools that include context sensitive help, implement context-sensitive help for accessibility terms as well as tasks related to accessibility.

Outside Reference (Suggested):

• T0245 Link to or provide URIs for more information on accessible Web authoring, such as WCAG 1.0 [WCAG10], and other accessibility-related resources.
• T0244 Document the tool's conformance to ATAG 1.0 [ATAG10].
• T0243 Include current versions of, or links to relevant language specifications in the documentation. This is particularly relevant for languages that are easily hand edited, such as most XML languages [XML].

Tutorials (Suggested):

• T0246 Include a tutorial specifically on checking for and correcting Web accessibility problems.

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

T0247 Ensure that the help system of the tool includes the documentation required by ATAG 6.1 in a dedicated section.[Required] @@

T0248 The dedicated section could be prefaced by an introduction that explains the importance of accessibility for a wide range of users, from those with disabilities to those with alternative viewers.(Suggested)

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