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

Re: Automatically testing Web content for flicker

From: Phill Jenkins <pjenkins@us.ibm.com>
Date: Fri, 7 Jun 2002 09:35:17 -0400
To: w3c-wai-er-ig@w3.org
Message-ID: <OF64E01810.AC29DA59-ON86256BD1.0049FD06@pok.ibm.com>


>>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.

I meant that it is an issue to have this unnecessary checkpoint in WCAG.
My point, and I think Nick's, was that it should not be in WCAG, and we
should not be trying to find methods to test to add to the WCAG success
criteria because it is not a content responsibility.  Flicker is handled by
the display's __mhz and the browser - so there is no requirement on the
author.

Please understand that photosensitive epilepsy is a real issue, but it
doesn't belong in WCAG.

Regards,
Phill Jenkins
IBM Research Division - Accessibility Center
http://www.ibm.com/able
Received on Friday, 7 June 2002 09:35:57 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 9 June 2005 12:10:41 GMT