Edit comment LC-1199 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-860 Next: LC-1203

Comment LC-1199: Comment Shortname:; Commenter: Al Gilman <Alfred.S.Gilman@IEEE.org>; 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:
The role of User Agents is underdeveloped in this document, and the effectiveness of the document suffers.

There is a whole missing principle of "different strokes for different folks."

It is not enough to say "people have to perceive the presentation of information." The encoding or representation of the information in that rendered view must be recognizable. The success criterion is in terms of cognition, not perception.

Further, there is no "one size fits all" presentation that affords a functional user experience for all people. So the fundamental requirement is one of personalization: that the same information can be presented and accepted in diversified look-and-feel variants to reach all the people.

The User Agent doesn't just render the display and process user input events. It also affords the user view-management funtions such as navigation within the document and presentation property profiling. These are managed between the user and the user agent. Sometimes it is not easy to make the rendering transform plastic enough to enable use by all users, and the server has to offer content choices to achieve the full range of under which the web content and/or service is available.

Proposed Change:

Clearly represent that the guidelines set out in this document apply to the data passing through the network interface, not the signals passing through the user interface.

Explain the requirements here (in this document, not a companion note) starting with User Interface requirement, but transformed by the capabilities and needs of User Agents.; Related issues: (space separated ids); WG Notes: [EDITORZ] Discussed in the 31 August 2006 telecon: Resolution: Accept LC-1199 as amended http://www.w3.org/WAI/GL/2006/08/31-wai-wcag-minutes.html {accept} DONE Change the Role of the User Agents section in the introduction to: Internal WD updated 1 Sept.; Resolution: The 'Components of Web Accessibility' section of the introduction now contains: It is important to note that Web content is just one aspect of accessibility. Just as important as accessible Web content is the availability of accessible browsers (and other user agents) that can adapt and present the content in the best form for the user. Accessible Web technologies and accessible tools for creating Web content are also important. For an overview of the different components of accessibility and how they work together see: * Essential Components of Web Accessibility - Explains how the Web Content Accessibility Guidelines work with the other WAI guidelines and with assistive technologies to provide access to the Web by people with disabilities. * User Agent Accessibility Guidelines (UAAG) Overview - Introduces guidelines on the design of accessible Browsers and other user agents. * Authoring Tool Accessibility Guidelines (ATAG) Overview - Introduces guidelines on the design of authoring and evaluation tools.; (Please make sure the resolution is adapted for public consumption)