Re: LVTF question

yes

Gregg C Vanderheiden
greggvan@umd.edu



> On Feb 14, 2017, at 9:51 AM, Jonathan Avila <jon.avila@ssbbartgroup.com> wrote:
> 
> Ø  Otherwise we would have to have an SC that says you cannot have a white background on your web page.
>  
> Creating content in a way the author does not prevent the user from adjusting the colors through the user agent seems like an item that is compatible with the LVTF needs.
> 
> Jonathan
>   <>
> From: Gregg C Vanderheiden [mailto:greggvan@umd.edu] 
> Sent: Tuesday, February 14, 2017 9:40 AM
> To: lisa.seeman
> Cc: GLWAI Guidelines WG org
> Subject: Re: LVTF question
>  
> Brightness is not a function of the software.  that is a function of the hardware.  
>  
> If they are sensitive to any bright light — they can turn the brightness down on their phone/computer — there can be no bright light.  
>  
> Otherwise we would have to have an SC that says you cannot have a white background on your web page.
>  
>  
> As for flashing  we do have SC on both strong flashing that is very large at all — and one for blinking of any size.   
>  
> If you do want to have something more about blinking content you will have to have numbers.   I don’t think a blinking period is a problem, or a very small icon.   — so “any size”  is not really viable.
>  
> Do you have any data on how many people and what size a blinking area is a real problem?    
>  
>  
> Gregg C Vanderheiden
> greggvan@umd.edu <mailto:greggvan@umd.edu>
>  
>  
>  
> On Feb 13, 2017, at 2:39 PM, lisa.seeman <lisa.seeman@zoho.com <mailto:lisa.seeman@zoho.com>> wrote:
>  
> Hi Folks
>  
> I was wondering if we have a SC for severe photophobia -people who get pain from intense light (any size) and flashing (any size)
>  
> There should be a semantics to mark any section of elements with flashing moving or blinking and these of these so that they can be blocked and make sure that low contrast can not be overridden 
>  
> Do we have a SC that support this 
>  
>  
>  
> All the best
> 
> Lisa Seeman
> 
>  <>LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter <https://twitter.com/SeemanLisa>

Received on Tuesday, 14 February 2017 14:56:48 UTC