RE: Propose deleting failure for 3.2.5

You can do it in script, but script can be disabled in every user agent I know of.  Some of those other technologies could probably do it, but I question whether that would constitute a *common* failure.  Seems like a fairly rare failure to me.  I think that the techniques we have around how to use meta refresh and how to set up opt-in content refreshing cover it.  Perhaps it would make sense to add an HTML/script technique for opt-out content refresh, instead of this failure?


________________________________
From: Gregg Vanderheiden [mailto:gv@trace.wisc.edu]
Sent: Tuesday, February 28, 2006 10:06 PM
To: Cynthia Shelly; w3c-wai-gl@w3.org
Subject: RE: Propose deleting failure for 3.2.5


Couldn't you do it in script?  Or Flash?  Or Director?   Applets?


Gregg

 -- ------------------------------
Gregg C Vanderheiden Ph.D.
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center
University of Wisconsin-Madison
The Player for my DSS sound file is at http://tinyurl.com/dho6b <http://tinyurl.com/cmfd9>


________________________________
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Cynthia Shelly
Sent: Tuesday, February 28, 2006 7:05 PM
To: w3c-wai-gl@w3.org
Subject: Propose deleting failure for 3.2.5

At least for HTML, the only ways I know of to "create a complete change of main content through an automatic refresh" are to use meta-refresh or script.  Both can be disabled in browsers.  Are there other technologies that have these issues?  If so, we could create a general technique about it.  If not, then I don't think this is a common failure for HTML, and I propose that we delete it.

http://trace.wisc.edu/wcag_wiki/index.php?title=Failure_due_to_complete_change_of_main_content_through_an_automatic_update_that_the_user_cannot_disable