W3C home > Mailing lists > Public > w3c-wai-er-ig@w3.org > June 2002

Re: Automatically testing Web content for flicker

From: Wendy A Chisholm <wendy@w3.org>
Date: Thu, 06 Jun 2002 20:24:04 -0400
Message-Id: <>
To: "Phill Jenkins" <pjenkins@us.ibm.com>, w3c-wai-er-ig@w3.org

> >IMO that belongs more in UAAG: a person with epilepsy would be well-
> >advised to use a browser that doesn't expose him/her to the risk,
> >regardless of webcontent.
> >
> >> [2] http://www.epilepsy.org.uk/info/photofrm.html
>Well said.  It's a browser/display issue, not a content issue.  The web
>site [2] says the problem goes away at 100mhz, so with the right display,
>and the animations turned off by the browser - is the problem solved or
>Again we need an expert here, not us wan-a-bees.

I've been in communication with Dr. Harding (one of the people who helped 
write that article as well as a textbook [0] on the subject).  I blind 
cc'ed him on the message to see if he could help.

>BTW, is this now a WCAG issue?

it's always been a WCAG issue.  It's a WCAG 1.0 checkpoint [1] and thus was 
incorporated into WCAG 2.0 [2].  I sent the question to this list since 
WCAG is trying to figure out methods to test to add to our success criteria.


[0] Harding, G. F. A. & Jeavons, P. M. Photosensitive Epilepsy. MacKeith 
Press, London, 1994 (available from Cambridge University Press).
[1] http://www.w3.org/TR/WCAG10/#tech-avoid-flicker
[2] http://www.w3.org/WAI/GL/WCAG20/#avoid-flicker

wendy a chisholm
world wide web consortium
web accessibility initiative
seattle, wa usa
Received on Thursday, 6 June 2002 20:17:49 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:01:33 UTC