RE: Propose deleting failure for 3.2.5

For meta refresh, while it can be disabled globally in IE, I don't know
how to disable it for a particular site (aside from going in, disabling
it globally, then turning it back on again later). I prefer to have it
on because sometimes it's helpful, but son some sites it becomes a
problem and I need a control to turn it off for that site. And I can't
find an option to disable it in Firefox, so unless I find or write an
extension I don't think it's possible.

 

For script refresh, I don't know how to disable that in any browser
except by turning off script support altogether, which is using a
sledgehammer to nail a thumbtack.

 

I'm caging these comments in "I don't know how" language because it's
possible the majority of browsers do in fact provide the feature to
disable automatic refresh in a useful way. But, unless someone can
describe how this is done in the vast majority of browsers in use today
((IE, Firefox, Safari, and Opera) on (Windows, Mac, and Linux) as a
minimum), I think it remains an issue, at least for some user agents,
and we should keep the failure technique.

 

Michael

 

________________________________

From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On
Behalf Of Cynthia Shelly
Sent: Tuesday, February 28, 2006 8: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