W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 2007

[Fwd: Proposal to combine 3.2 and 3.3]

From: Jan Richards <jan.richards@utoronto.ca>
Date: Mon, 13 Aug 2007 10:42:08 -0400
Message-ID: <46C06DC0.6030808@utoronto.ca>
To: WAI-UA list <w3c-wai-ua@w3.org>

Hi,

This is a result of my action item to tweak Peter's proposal to be more 
clear about placeholders 
(http://lists.w3.org/Archives/Public/w3c-wai-ua/2007JulSep/0058.html).

In doing so, I decided to split out audio and also distinguish between 
chrome and viewport...since I think it's more likely that the user would 
be explicitly ask to render individual images in the content than in the 
  chrome (e.g. button bar images).

Also in my opinion this checkpoint is crying out to have things 
re-organized into WCAG and ATAG-style success criteria:

3.2 Toggle audio, video, animated images, and animated/blinking text (P1)

*1. Allow configuration not to render stand-alone or multimedia audio in 
the viewport, except on explicit user request, and instead display a 
placeholder*
*2. Allow configuration not to render audio in the chrome.*
*3. Allow configuration to render motionless placeholders for video or
animated images in the viewport except on explicit user request.*
*4. Allow configuration to display motionless placeholders for video or
animated images in the chrome.*
5. 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 displaying an audio 
placeholder that indicates (a) that the audio content has been silenced 
and (b) allows the user to explicitly request that the audio be played.*
2. *The user agent may satisfy this checkpoint by showing a placeholder 
(e.g. a blank or still images) that indicates that (a) video or image 
animations have been blocked and (b) allows the user to explicitly 
request that they be rendered.*
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
be determined programmatically to be 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 *the* result of a
script) as well as content rendered as the result of user interaction
that is *not* 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. Conformance profile labels: Visual text, Animation, Video, Audio

Notes
(merge bullets from existing 3.2, 3.3)

-----

JR: I've modified the definition of *blinking text" to be more in line 
with WCAG 2.0.

blinking text: text whose visual rendering *turns on and off 0.5 times 
per second or more*.


Cheers,
Jan






Peter Parente
pparent@us.ibm.com
Tie: 526-2346
IBM: 919-486-2346
Inactive hide details for Jim Allan <allanj@tsbvi.edu>Jim Allan
<allanj@tsbvi.edu>


                         *Jim Allan <allanj@tsbvi.edu>*
                         Sent by: w3c-wai-ua-request@w3.org

                         08/01/2007 03:10 PM
                         Please respond to
                         jimallan@tsbvi.edu

	

To
	
WAU-ua <w3c-wai-ua@w3.org>

cc
	

Subject
	
User Agent Teleconference for August 2 2007

	



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




-- 
Jan Richards, M.Sc.
User Interface Design Specialist
Adaptive Technology Resource Centre (ATRC)
Faculty of Information Studies
University of Toronto

   Email: jan.richards@utoronto.ca
   Web:   http://jan.atrc.utoronto.ca
   Phone: 416-946-7060
   Fax:   416-971-2896
Received on Monday, 13 August 2007 14:43:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:51:47 GMT