[thelist] Incorporating a NOSCRIPT declaration where the script is in the header

Christian Heilmann codepo8 at gmail.com
Wed Jan 25 15:35:43 CST 2006


> "Rule: 6.3.4 - When SCRIPT Elements are used, the NOSCRIPT element  is
> required in the document.
> Warning - SCRIPT Element(s) are found in  document and the NOSCRIPT
> element is not."

Interesting how the vendor of that automated test tool read the specs:

6.3 Ensure that pages are usable when scripts, applets, or other
programmatic objects are turned off or not supported. If this is not
possible, provide equivalent information on an alternative accessible
page. [Priority 1]
For example, ensure that links that trigger scripts work when scripts
are turned off or not supported (e.g., do not use "javascript:" as the
link target). If it is not possible to make the page usable without
scripts, provide a text equivalent with the NOSCRIPT element, or use a
server-side script instead of a client-side script, or provide an
alternative accessible page as per checkpoint 11.4. Refer also to
guideline 1.
Techniques for checkpoint 6.3

508 is totally in la la land, especially as those guidelines say
"javascript:" is valid as assistive technology can read it:
http://www.access-board.gov/sec508/guide/1194.22.htm#(l)


--
Chris Heilmann
Blog: http://www.wait-till-i.com
Writing: http://icant.co.uk/
Binaries: http://www.onlinetools.org/



More information about the thelist mailing list