W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2006

Clearing Issues for 1.4

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Wed, 25 Jan 2006 01:34:46 -0600
To: <w3c-wai-gl@w3.org>
Message-ID: <00aa01c62181$d13c8520$ee8cfea9@NC6000BAK>
 


1614    turn off background audio without silencing foreground audio

If this is meant to imply that the user should be
able to turn off background audio without silencing foreground audio, then
the criterion needs to be reworded to reflect that. As it reads today, all
multimedia would comply as long as the user can turn off their speakers or
mute all audio at the operating system level.                [Comment on
"1.4 L2 SC3: A mechanism is available to turn off background audio that
plays automatically."]

 

Proposed

 

Change it to 

1.4.2          A mechanism is available to turn off background audio that
plays automatically without turning off system volume.

And Close 

 


1615    audio that plays automatically

The current wording only applies this criterion to background audio that
plays automatically, but if it doesn't play automatically--only in response
to some user action--then one could argue that the user can effectively turn
it off by declining to start it. Therefore I suggest removing the phrase
"that plays automatically" as unnecessary.                [Comment on "1.4
L2 SC3: A mechanism is available to turn off background audio that plays
automatically."]

 

Suggest 

Close with

We do not want to prevent audio that the user invokes.  Just audio that
plays automatically.  

 


1616   A mechanism is available to turn off display of background patterns

adding a success criterion to the effect
that "A mechanism is available to turn off display of background patterns
and images that are displayed behind text and/or graphics and to control the
color of the solid background behind such text and graphics." I would make
this L2. (Or is this a UA issue?)                [Comment on "1.4 L2 SC3: A
mechanism is available to turn off background audio that plays
automatically."]

 

Suggest

 We had considered this but it would be too restrict graphic formats that
could be used.  We decided to go have two levels of contrast instead. 

 


1618  turn off playing of the background sounds

I would add a third option, "..., or the user can
turn off playing of the background sounds."                [Comment on "1.4
L3 SC2: Audio content does not contain background sounds or the background
sounds are at least 20 decibels lower than the foreground audio content,
with the exception of occasional sound effects."]

 

Suggest

That we do this.   Change success criterion to:

 

1.4.4 Audio content does not contain background sounds, the background sound
can be turned off or the background sounds are at least 20 decibels lower
than the foreground audio content, with the exception of occasional sound
effects.

 


1707   L1 SC seems a little weak


 

Says old L1 was weak. Should have ""...ensure that foreground 
and background colours can be overridden by the reader,"

"

Suggest          

That we close this with.  

 

This is not currently in the capabilities of user agents and would not be
possible with standard HTML pages.  

We will include this as optional technique under guideline. 

 


1835                      GL 1.4 should require legible contents when using
high contrast settings

Most users who rely on very high contrast simply activate a relevant setting
in their user agent, or more 
commonly in the underlying Operating System.
 
There should be a requirement that content is legible under such
circumstances.

 

Suggest

Close with comment

This would appear to require authors to know what operating system features
would be for users (on different operating systems).  We do not know how to
write techniques for something like this. 

 


1842   color: raise priority of SC 1.3.4, 1.4.1 and 1.4.3

 
Success Criterion 1.3.4 should either be a stand-alone Level 1 Criterion, or
incorporated 
into Success Criterion 1.3.2.
 
Success Criterion for 1.4.1 should be Level 1, and 
for 1.4.3 it should be Level 2.

 

Suggest

We should poll these suggestions

 

-  Move 1.3.4 Any information
<http://www.w3.org/WAI/GL/WCAG20/appendixA.html#colorinfodef>  that is
conveyed by color is visually evident when color is not available  to L1
YES/NO

- Move 1.4.1 Text or diagrams, and their background, have a luminosity
contrast ratio
<http://www.w3.org/WAI/GL/WCAG20/appendixA.html#luminosity-contrastdef>  of
at least 5:1.  to L1   YES / NO

- Move 1.4.3 Text or diagrams, and their background, have a luminosity
contrast ratio
<http://www.w3.org/WAI/GL/WCAG20/appendixA.html#luminosity-contrastdef>  of
at least 10:1  to L2   YES/NO

 

 


  892   Readable fonts

JIS has a guideline that describes choosing default readable fonts.
Suggestion
that we consider something similar.  @@reference to their language.

 

Suggest

Would be good to have a technique for JIS to link to.  Will advisory
technique work?  Don't know how to do a testable 'readable font' guidline. 

Close with

 We don't think we can create a testable success criterion for this.
Readable fonts is not testable.  

 We are adding as advisory technique under 1.4 in Understanding WCAG 2.0.

     "Using readable fonts." 

 

 
Received on Wednesday, 25 January 2006 07:34:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:42 GMT