Edit comment LC-720 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-1066 Next: LC-946

Comment LC-720: Comment Shortname:; Commenter: Robert C. Baker <Robert.C.Baker@ssa.gov> on behalf of Social Security Administration; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
Part of Item:
Comment Type: TE
Comment (including rationale for proposed change):

(See LC 681 for complete submission)

The guidelines do not address the following:

Â§Guidelines for creating HTML documentation and Help must be stated and Help using navigational techniques must also be documented for accessibility.

Proposed Change:; Related issues: LC-681
(space separated ids); WG Notes: [TEAMB] SENT FOR CLARIFICATION * Do not understand this one. If the documentation is on the Web, it is covered by the guidelines. For the last part are you just saying that there must be a help file on each page that says how to navigate that page? Can you explain more and give us an example of what you think should be on each web page? CLARIFICATION RECEIVED SSA has found that vendors supplying documentation for products do not have a clear understanding of what is required for accessible electronic documentation. Often documentation is supplied in PDF format and is determined to be not accessible. Vendors will then just convert to HTML and think they are done with it. It is likely that the WCAG guidelines do cover documentation and Help facilities but it is felt that a separate section dedicated to Help and documentation would help to clarify this situation. Documentation and Help can be presented in many formats. These include straight text, a Microsoft or RoboHelp type Help facility with frames such as Content, Index and Search, an interactive documentation capability where there is a table of contents and the user is able to move around a document and finally links to context sensitive Help on the same HTML page. The issues that are involved include: Equivalent alt text for images Ability to move automatically to a content frame when a link is selected from a different frame Elimination of A-Z links for index as it requires significant keyboarding to be replaced by drop downs Selection of objects moving directly to the object of the selection and therefore a change in focal point Ability to move back to original focus when a Help link is selected HTML capability to select context sensitive help for a field through keystrokes Discussed in the 24 August 2006 telecon: Resolution: accept 720 as amended http://www.w3.org/WAI/GL/2006/08/24-wai-wcag-minutes.htm {not-accept}; Resolution: We agree that Help and documentation that is available *on the web* is web content and hence that it should conform to these Guidelines. Note that although the same issues appear for documentation and Help files for desktop applications, these guidelines do not address that content. However, we feel that attempting to single out specific examples of Web content is likely to lead people to believe that only the listed examples are covered.; (Please make sure the resolution is adapted for public consumption)