E-mail List Archives

RE: HowTo provide the user the ability to turn refresh off?

for

From: O'Rourke, John
Date: Dec 20, 2002 1:19PM


Joel and all,

I interpret the refresh verses non-refresh capabilities in the following
manner. It's not a violation necessarily in Section 508 to include web
content refresh characteristics in web design. It is more of a
violation to prevent user agents from the ability to alter the rate of
page refresh settings. Microsoft's DOM provides the ability to slow
down or turn off refresh and I'll have to take a closer look at the JAWS
updated scripts and the Window-Eyes set files to examine how this was
accomplished. User agents now have the ability to provide selective
controls and toggles not found in earlier releases particularly in
assistive technology.

John O'Rourke


-----Original Message-----
From: Joel Ward [mailto: <EMAIL REMOVED> ]
Sent: Friday, December 20, 2002 2:44 PM
To: <EMAIL REMOVED>
Subject: Re: HowTo provide the user the ability to turn refresh off?


> The option allowing refresh is:
> <meta http_equiv="REFRESH" contents="300">

By-the-way, is this considered a violation of the 508 or W3C rules?
I've seen discussions arguing both sides.

I consider it a violation, as it can be impossible for certain people to
read (or listen to) the page quick enough (therefore they are unable to
receive all of the content).


----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/


----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/