W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2001

RE: Any examples of <NOSCRIPT>?

From: Jim Thatcher <thatch@attglobal.net>
Date: Tue, 20 Feb 2001 19:24:55 -0600
To: Kynn Bartlett <kynn@reef.com>, "W3c-Wai-Ig@W3. Org" <w3c-wai-ig@w3.org>
Message-id: <NDBBKJDAKKEJDCICIODLKEILCNAA.thatch@attglobal.net>
Great Kynn,

You asked whether or not this is an "ideal usage" of the NOSCRIPT element.
My question was whether there were real life "effective" uses.

I really didn't expect any, and good for you for finding a "real life" use
of NOSCRIPT. This one at http://www.section508.gov, of all places, is
certainly real life and it is effective. What it does is provide text at the
top of the page that in effect says "we use JavaScript for XYZ and since you
don't support JavaScript you are out of lunch as regards XYZ."

I really think that is kind of an ingenious idea. "We're using JavaScript
and you don't get the benefit of it, so TOUGH!"

I guess I would say the instance is certainly not ideal. The prescription
for NOSCRIPT is that authors will provide alternate content when scripting
is not available. This example does not do that because I read "alternate"
do be in some sense equivalent.

Do you agree?

Jim
jim@jimthatcher.com
Accessibility Consulting
http://jimthatcher.com
512-306-0931

-----Original Message-----
From: Kynn Bartlett [mailto:kynn@reef.com]
Sent: Tuesday, February 20, 2001 5:19 PM
To: jim@jimthatcher.com; W3c-Wai-Ig@W3. Org
Subject: Re: Any examples of <NOSCRIPT>?


At 12:01 PM 2/20/2001, Jim Thatcher wrote:
>Does anyone know of a real life effective use of the NOSCRIPT element?

The government's Section 508 web site -- http://www.section508.gov/
-- uses a <noscript> element.  This might be an interesting point of
discussion as to whether or not this is ideal usage.

Here's the content of the <noscript>:

<noscript>
         <font face="Arial" size="-1"> You are receiving this message since
your browser does not support Java
         Script or you have Java Scripts disabled in your browser.  The
following
         disclaimer paragraphs are provided below as the alternative for
display of information that would
         normally be seen on your monitor when you click on a link to a
federal site
         or if you clicked on a link to a non-federal site. <ul>
                 <li>All external links to federal sites include an exit
Java Script pop-up
                         disclaimer that includes the following language.
"You are now leaving the
                         Section 508 website.  Thank you for visiting our
site.  We welcome your
                         comments on how we can make our site more useful."
                 <li>All external links to non-federal sites include an
exit pop-up disclaimer
                         that includes the following language: "You are now
leaving the Section 508
                         website.  Thank you for visiting our
                         site.  We welcome your comments on how we can make
this site more useful.
                         You are now leaving this site to link to another
location that is not
                         maintained by the Federal Government.  The Federal
Government takes no
                         responsibility for and exercises no control over
non-government sites, the
                         view that may be represented, or the accuracy,
privacy policies, copyright
                         or trademark compliance, or the legality of any
material contained on those
                         sites."
         </ul>
         <p>Any questions about exit disclaimers should be referred to the
Webmaster at section.508@gsa.gov</p></font>
</noscript>

What do you think?

--Kynn


--
Kynn Bartlett <kynn@reef.com>
Technical Developer Liaison
Customer Management/Edapta
Reef North America
Tel +1 949-567-7006
________________________________________
ACCESSIBILITY IS DYNAMIC. TAKE CONTROL.
________________________________________
http://www.reef.com
Received on Tuesday, 20 February 2001 20:31:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:53 GMT