- From: David Poehlman <david.poehlman@handsontechnologeyes.com>
- Date: Thu, 27 Jul 2006 14:45:46 -0400
- To: Jim Allan <jimallan@tsbvi.edu>
- Cc: w3c-wai-ua@w3.org
On Jul 27, 2006, at 2:04 PM, Jim Allan wrote: my comments inline Jim > Peter Parente wrote: >> >> 4.4 Slow Multimedia >> >> I found this note interesting in light of our discussion two weeks >> ago >> about 3.1 (Toggle background images) and DHTML libraries that use CSS >> tricks (e.g. background) to draw widgets. >> >> *Note:* The style exception of this checkpoint is based on the >> assumption that authors have satisfied the requirements of the "Web >> Content Accessibility Guidelines 1.0" /_[WCAG10]_/ >> <http://www.w3.org/TR/UAAG10-TECHS/references.html#ref-WCAG10> not to >> convey information through style alone (e.g., through color alone or >> style sheets alone). >> >> I see how it fits in the 4.4 section. Does it also suggest any >> changes >> in 3.1? > > JR: I'm not sure what you mean. The problem with background images is > that they are behind other content, creating potential contrast > problems. JA: Not sure about 3.1, need more information. I think 4.4 may tie into 3.2. Animation can be created with Multimedia, and this may require that in addition to ability not to render the content (3.2), that if the multimedia animation, etc. is rendered then the user should be able to control the speed. there is a note in 3.2 referring to Guideline 4 for add ional requirements "Note: See guideline 4 for additional requirements related to the control of rendered audio, video, and animated images. When these content types are not rendered, they are considered conditional content. See checkpoint 2.3 for information about providing access to conditional content." 4.4 has a normative exclusion 1. The user agent is not required to satisfy this checkpoint for audio and animations whose recognized role is to create a purely stylistic effect. Purely stylistic effects include background sounds, decorative animated images, and effects caused by style sheets. this seems strange to me. the purpose of the audio, animation, etc. should not matter. The user should be able to stop it (3.2) or slow it down (4.4). How is the UA to know what is stylistic and what is real content? PP wrote: >> Backtracking a bit to 3.2 (Toggle audio, video, animated images), I >> noticed a new use of animated images the other day that should >> probably >> be user configurable (i.e. on/off). Visit http:// >> www.ethicalhacker.net/ >> in Firefox and watch the site icon that shows up on both the page tab >> and the URL bar. It's a looping (and distracting) animated GIF. > It's not >> part of the content of any page per se, but it is delivered to > and shown >> by the browser when the user visits any page on the site. Should the >> techniques for 3.2 make it explicit that a UA must allow a user to >> turn >> on/off animated content that is not rendered within the main content, >> but still delivered as content and shown elsewhere in the user agent >> chrome? JR wrote: > I can see two ways of handling that: > 1. call it chrome and require ability to toggle animation in chrome. > 2. call the area content since it is controlled by content and have > this > checkpoint apply. JA: I like #2
Received on Thursday, 27 July 2006 18:45:58 UTC