WebAIM - Web Accessibility In Mind

E-mail List Archives

RE: NOSCRIPT question

for

From: Steven Faulkner
Date: May 2, 2006 7:30PM


Chris wrote
> And how is that more logical than having the definitions at the end of
> the page and using target links on the words?

I didn't claim that it was more or less logical than any other method,
and I agree that implementing a different method may be more logical.
The example I gave was to demonstrate a possible use of the NOSCRIPT
element.

After testing the functionality of their script with assistive
technology and keyboard I found that it was accessible via a number of
user agents and input devices with javascript enabled.

It is not my role to tell them that their "script planning" is "sad"
unless it impacts upon the accessibility of the content.

with regards

Steven Faulkner
Web Accessibility Consultant
vision australia - information & library service
454 Glenferrie Road
Kooyong Victoria 3144
Phone: (613) 9864 9281
Fax: (613) 9864 9210
Email: <EMAIL REMOVED>
www.accessibleinfo.org.au | www.wat-c.org

Download the Web Accessibility Toolbar
[http://www.visionaustralia.org.au/ais/toolbar/]

Vision Australia was formed through the merger of the Royal Blind
Society
NSW, the Royal Victorian Institute for the Blind, Vision Australia
Foundation and the National Information & Library Service.
ABN: 67 108 391 831 ACN: 108 391 831



> -----Original Message-----
> From: Christian Heilmann [mailto: <EMAIL REMOVED> ]
> Sent: Wednesday, 3 May 2006 9:40 AM
> To: <EMAIL REMOVED> ; WebAIM Discussion List
> Subject: Re: [WebAIM] NOSCRIPT question
>
>
> > I can give you an example of NOSCRIPT use that i
> recommended to a client
> > yesterday.
> >
> > The clients page has a javascript based "glossary"
> function: when a user
> > activates a Javascript link on certain words, content is
> written to the
> > page with the definition of the word. because the content
> is written to
> > the page via javascript it is not available when Javascript
> is disabled
> > or not supported. In this case I recommended that a
> NOSCRIPT element be
> > included containing the word definitions, so that the information is
> > available regardless of javascript support.
>
> And how is that more logical than having the definitions at the end of
> the page and using target links on the words? This would work without
> JavaScript. With JavaScript you can initially hide all the
> definitions, loop through all links and display them f.e. as a tooltip
> when the user clicks or hovers over the links.
>
> No need for NOSCRIPT, it is in 99.9% of the cases a sad excuse for bad
> script planning.
>
> --
>
> Chris Heilmann
> Blog: http://www.wait-till-i.com
> Writing: http://icant.co.uk/
> Binaries: http://www.onlinetools.org/


___________________
<< ella for Spam Control >> has removed Spam messages and set aside Later
for me
You can use it too - and it's FREE! http://www.ellaforspam.com