- From: Markku Hakkinen <markku.hakkinen@gmail.com>
- Date: Fri, 26 Feb 2010 15:07:50 -0600
- To: UAWG list <w3c-wai-ua@w3.org>
5.3.1 Accessible Format: At least one version of the documentation is either (Level A): (a) "A" accessible: Web content and conforms to WCAG 2.0 Level "A" (although it is not necessary for the documentation to be delivered on-line), or, (b) accessible platform format: not Web content and conforms to a published accessibility benchmark that is identified in the conformance claim (e.g., when platform-specific documentation systems are used). Intent of Success Criterion 5.3.1: User agents will provide documentation in a format that is accessible. If provided as Web content, it must conform to WCAG 2.0 Level "A" and if not provided as Web content, it must be in conformance to a published accessibility benchmark and identified in any conformance claim for the user agent. This benefits all users who utilize assistive technology or accessible formats. Examples of Success Criterion 5.3.1 A user agent installs user documentation in HTML format conforming to WCAG 2.0 Level "A". This documentation is viewed within the user agent and is accessible in accordance with the conformance of the user agent to UAAG 2.0. A user agent provides documentation in HTML format conforming to WCAG 2.0 Level "AA" and is available online. In addition, the user agent provides user documentation in a locally installed digital talking book content format in conformance with a recognized, published format. 5.3.2 Document Accessibility Features: All user agent features that benefit accessibility @@DEFINE - as specified in the conformance claim@@ are documented. (Level A) Intent of Success Criterion 5.3.2: User agent documentation that includes listings and descriptions of features supporting or benefitting accessibility permits users to have access to a description of accessibility and compatibility features. This benefits all users with disabilities who may require assistance in identifying which accessibility features may be present or how to configure those features to work with assistive technology. Examples of Success Criterion 5.3.2: In a section entitled "Browser Features Supporting Accessibility", a vendor provides a detailed description of user agent features which provide accessibility, describing how they function, and listing any supported third party assistive technologies that may be supported or required.
Received on Friday, 26 February 2010 21:08:22 UTC