ZVON > References > ATAG 1.0
   Previous | Next | Guidelines | Priorities

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 [P1]Ensure that the author can produce accessible content in the markup language(s) supported by the tool.
1.2 [P1]Ensure that the tool preserves all accessibility information during authoring, transformations, and conversions.
1.3 [relative] Ensure that when the tool automatically generates markup it conforms to the W3C's Web Content Accessibility Guidelines 1.0.
1.4 [relative]Ensure that templates provided by the tool conform to the Web Content Accessibility Guidelines 1.0.
[ top ]