- From: Anne Pemberton <apembert@erols.com>
- Date: Mon, 20 Aug 2001 16:47:42 -0400
- To: "WAI Guidelines WG" <w3c-wai-gl@w3.org>
- Message-Id: <5.1.0.14.0.20010820163657.00a43650@pop.erols.com>
Folks, Took Chas idea of separating the guidelines into those related to content and those related to coding, and ended up with three groups .... those that are purely content - all decisions would be out of the hands of the coder (unless the content designer and coder were the same person), those that require a action and/or decision by the content designer and action by the coder, and those that (seem to me) to be purely the bailiwick of the coder. They are rough, and there could be legitimate disagreement on category placement, but I think this suggest that separating content and coding wouldn't be easily done .... Content: The decision will be made by the content provider, the coder has no responsibility * 2.6 Avoid causing the screen to flicker. * 3.3 Write as simple as possible yet appropriate for the site's content. * 3.4 Supplement text with non-text content. * 3.5 Annotate complex or unfamiliar information with summaries and definitions. * 4.1 Choose technologies that support the use of these guidelines. * 4.4 Design content so that when presentation effects are turned off or not supported the content is still usable. Mixed: The decision is made by the content provider, the coder has to follow specs. * 1.1 Provide a text equivalent for all non-text content. * 1.2 Synchronize media equivalents with time-dependent presentations. * 1.3 Use markup or a data model to provide the logical structure of content. * 1.4 Identify the primary natural language of text and text equivalents and all changes in natural language. * 2.1 Handle input errors, such as misspellings. * 2.4 Either give the user control over how long they can interact with content that requires a timed response or give them as much time as possible. * 3.1 Use consistent presentation. * 3.2 Emphasize structure through presentation, positioning, and labels Coding: The responsibility to do this rests principally with the coder. * 1.5 Separate content and structure from presentation. * 2.2 Provide consistent and predictable responses to user actions. * 2.3 Give users control of mechanisms that cause extreme changes in context. * 4.2 Use technologies according to specification. * 4.3 Design user interfaces compatible with assistive technology. Please feel free to rip these categories to shreds. Anne Anne Pemberton apembert@erols.com http://www.erols.com/stevepem http://www.geocities.com/apembert45
Received on Monday, 20 August 2001 16:55:45 UTC