Ensure that all content is accessible 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.
<script language="JavaScript">
<!-- function popwin(){window.open('http://www.somethinginnewwindow.htm','',
'width=400,height=200, scrollbars=1');} // --> </script>
<noscript> This pages used JavaScript to display a pop-up window that points a user to
<a href="perhapsanexecutable.exe">Whatever the script or applet was going to do</a> and here is
some more definition of what to expect.</noscript>
Many users do not use equipment that is capable of running scripts, applets or other programmatic objects. For example, they may have old or non-mainstream hardware and software that does not support the scripting languages or supports only earlier versions. They may be working in an environment where scripts and applets are blocked by a firewall for security reasons. They may have a physical impairment that means they are unable to use a mouse and cannot therefore interact with scripts that require mouse input. Or they may be using a form of assistive technology, such as a screen reader, which cannot access the contents of the script, applet or object. Other users may have turned off support for script handling for reasons of speed or security.
Writing directly accessible applets - WAI recommended technique.
Guidelines on accessibility features provided in Java - Sun guidelines
View WAI checkpoint 9.2 - Ensure that any element that has its own interface can be operated in a device-independent manner.
View WAI checkpoint 9.3 - For scripts, specify logical event handlers rather than device-dependent event handlers.
View WAI checkpoint 8.1 - Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies.