- From: Peter Parente <pparent@us.ibm.com>
- Date: Wed, 8 Aug 2007 16:50:47 -0400
- To: jimallan@tsbvi.edu
- Cc: WAU-ua <w3c-wai-ua@w3.org>, w3c-wai-ua-request@w3.org
- Message-ID: <OF3EF20EBE.2E66EC3D-ON85257331.007005F8-85257331.00727D24@us.ibm.com>
3.2 Toggle audio, video, animated images, and animated/blinking text (P1) 1. Allow configuration not to render audio, video, or animated images in the viewport or chrome except on explicit user request. 2. Allow configuration to render animated or blinking text in the viewport or chrome as motionless, unblinking text. Sufficient techniques 1. The user agent may satisfy this checkpoint by making video and animated images invisible and audio silent, but this technique is not recommended. 2. The user agent may satisfy this checkpoint by showing still images in place of video and image animations. 3. The user must still have access to all animated/blinking text content, but the user agent may render it in a separate viewport (e.g., for large amounts of streaming text). 4. The user agent may satisfy this checkpoint by always rendering animated or blinking text as motionless, unblinking text. Normative inclusions and exclusions 1. This checkpoint does not apply for content the user agent cannot deterministically recognize as audio, video, animated images, or animated/blinking text. 2. This configuration is required for content rendered without any user interaction (including content rendered on load or as ther result of a script) as well as content rendered as the result of user interaction that is no an explicit user request (e.g., when the user activates a link). 3. This checkpoint must be satisfied for all implemented audio, video, animated image, and animated/blinking text specifications; see the section on conformance profiles. 4. When configured not to render audio, video, or animated images except on explicit user request, the user agent is not required to retrieve them until the user requests them explicitly. 5. Checkpoint 4.3 addresses user control of blinking effects caused by rapid color changes. 6. Conformace profile labels: Visual text, Animation, Video, Audio Notes (merge bullets from existing 3.2, 3.3) ----- We should probably pull the inline definition out of the old 3.3 and put it with the rest of the terms used in the document. blinking text: text whose visual rendering alternates between visible and invisible at any rate of change. Peter Parente pparent@us.ibm.com Tie: 526-2346 IBM: 919-486-2346 Jim Allan <allanj@tsbvi.edu > To Sent by: WAU-ua <w3c-wai-ua@w3.org> w3c-wai-ua-reques cc t@w3.org Subject User Agent Teleconference for 08/01/2007 03:10 August 2 2007 PM Please respond to jimallan@tsbvi.ed u W3C User Agent Teleconference for August 2 2007 ------------------------------------------------------------- Chair: Jim Allan Date: Thursday, August 2 2007 Time: 1:00-2:00 pm Boston Local Time, USA (18:00-19:00 UTC/GMT) Call-in: Zakim bridge at: +1-617-761-6200, code 82941# for UK use 44-117.270-6152 IRC: sever: irc.w3.org, port: 6665, channel: #ua. ------------------------------------------------------------- Regrets, agenda requests, or comments to the list Regrets: Cathy Laws Agenda: 1. Charles Chen author of FireVox participating on call. Discuss AJAX and UA behavior 2. review action items JA to Will forward PP's message to x-tech. JA to Contact Charles Chen to invite him to the call. JR to Will update wiki for 3.1 JR (3.4) rework new proposal, flesh out setting and UA behavior PP to Proposal to combine 3.2 and 3.3 JA to Get thoughts together about 3.4 "All executable content" managing configuration 3. @alt and @title display as tooltip Jim Allan, Webmaster & Statewide Technical Support Specialist Texas School for the Blind and Visually Impaired 1100 W. 45th St., Austin, Texas 78756 voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/ "We shape our tools and thereafter our tools shape us." McLuhan, 1964
Attachments
- image/gif attachment: pic32706.gif
Received on Wednesday, 8 August 2007 20:51:10 UTC