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

Re: GIFs

From: Josh Hughes <josh@deaghean.com>
Date: Fri, 28 Mar 2003 16:01:07 -0500
To: "'w3c-wai-ig@w3.org'" <w3c-wai-ig@w3.org>
Message-ID: <20030328160107874097.GyazMail.josh@deaghean.com>

RAMP's pretty kludgy for such an expensive piece of software, but it 
does do a decent job remediating flicker rate.

I think there's a lot of programming necessary to catch all the 
potential things that could cause a page to flicker. It's better as a 
user check; I think most people could tell whether or not their page 
could cause someone to have an epileptic seizure.


> This is slightly different, but closely related: Deque
> <http://www.deque.com/> creates a product called RAMP that detects
> unacceptable flicker rates and fixes them.
> From <http://www.deque.com/products/rampsection508.htm>:
> "Section 508 Paragraph (j) Pages shall be designed to avoid causing the
> screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
> "Automatically detects flickering rates with unacceptable frequency
> Auto Remediation of animated gifs, marquee elements, and other blinking
> elements." 
> I just happened to go to a product demonstration recently, but haven't had a
> chance to test it out for myself; they did use the product to change a gif
> during the demonstration and it seemed to work well.
> --Liz Roberts 
Received on Friday, 28 March 2003 16:01:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:14 UTC