This is an easy question for someone out there. I want my site to be accessible to lots of people with disabilities. I like to use Javascript in my sites - what to I put in the HTML to replace the Javascript of buttons, etc.? I'm new at this so speak slow...<!--content--><noscript> is used in the event when a browser is configured to not execute any script that might be in the script tags,in this situation noscript is provided with some plain message.<br />
<br />
For more infor on this..please follow this link.<br />
<!-- m --><a class="postlink" href="http://www.w3.org/TR/html401/interact/scripts.html#h-18.3.1">http://www.w3.org/TR/html401/interact/s ... l#h-18.3.1</a><!-- m --><!--content-->It would be better to build a page that works for you without JavaScript with a bit of redirect script so that someone with js enabled will be directed to a js page. <br />
<br />
The <noscript> tag basically makes the particular part of your page that is enclosed in the tag visible only when js is disabled, so that you can inform the user that your page requires js.<!--content-->I tend to disagree with the approach that Mr. Davis has suggested. And I do so for several reasons. <br />
<br />
◊ Most users will have JavaScript enabled and wont even be aware of the script free version. If you site is of any worth then people will begin linking to it - and they'll be linking to the JavaScript dependent version because that's the only one that they know about. <br />
<br />
◊ It's a real nuisance to keep two versions of the same site up to date. And you'll need a graphics version with JavaScript, a graphics version without JavaScript, a text-only version with JavaScript and a text-only version without JavaScript. <br />
<br />
◊ It's a lot of intellectual fun to make one page that works for all. You just have to be creative. If you are using those cascading, DHTML menus then just make certain that the root links are real and that they lead to index pages that the enJavaScripted will never see. Or you can make one big index page and put a link to that inside the NOSCRIPT element. Go ahead an have your form submit 'onchange' but put a submit button in the NOSCRIPT element. In engineering this is known as making the system fail safe. You want valves to automatically close when the power fails so that you don't flood some stream. And wouldn't it be great if somebody could figure out how to make an elevator, in the event of power loss, to descend slowly to the next floor where the doors open by themselves. The trick in making your page fail safe is to start with one that works for all. Once you have that then you can start adding scripts and images - bells, whistles and fuzzy dice. And make sure that your page is in HTML 4.01 Strict (<!-- m --><a class="postlink" href="http://www.w3.org/TR/html4/">http://www.w3.org/TR/html4/</a><!-- m -->), XHTML 1.0 Strict or XHTML 1.1 andbe certain to follow the Web Content Accessibility Guidelines 1.0 (<!-- m --><a class="postlink" href="http://www.w3.org/TR/WCAG10/">http://www.w3.org/TR/WCAG10/</a><!-- m -->).<!--content-->
<br />
For more infor on this..please follow this link.<br />
<!-- m --><a class="postlink" href="http://www.w3.org/TR/html401/interact/scripts.html#h-18.3.1">http://www.w3.org/TR/html401/interact/s ... l#h-18.3.1</a><!-- m --><!--content-->It would be better to build a page that works for you without JavaScript with a bit of redirect script so that someone with js enabled will be directed to a js page. <br />
<br />
The <noscript> tag basically makes the particular part of your page that is enclosed in the tag visible only when js is disabled, so that you can inform the user that your page requires js.<!--content-->I tend to disagree with the approach that Mr. Davis has suggested. And I do so for several reasons. <br />
<br />
◊ Most users will have JavaScript enabled and wont even be aware of the script free version. If you site is of any worth then people will begin linking to it - and they'll be linking to the JavaScript dependent version because that's the only one that they know about. <br />
<br />
◊ It's a real nuisance to keep two versions of the same site up to date. And you'll need a graphics version with JavaScript, a graphics version without JavaScript, a text-only version with JavaScript and a text-only version without JavaScript. <br />
<br />
◊ It's a lot of intellectual fun to make one page that works for all. You just have to be creative. If you are using those cascading, DHTML menus then just make certain that the root links are real and that they lead to index pages that the enJavaScripted will never see. Or you can make one big index page and put a link to that inside the NOSCRIPT element. Go ahead an have your form submit 'onchange' but put a submit button in the NOSCRIPT element. In engineering this is known as making the system fail safe. You want valves to automatically close when the power fails so that you don't flood some stream. And wouldn't it be great if somebody could figure out how to make an elevator, in the event of power loss, to descend slowly to the next floor where the doors open by themselves. The trick in making your page fail safe is to start with one that works for all. Once you have that then you can start adding scripts and images - bells, whistles and fuzzy dice. And make sure that your page is in HTML 4.01 Strict (<!-- m --><a class="postlink" href="http://www.w3.org/TR/html4/">http://www.w3.org/TR/html4/</a><!-- m -->), XHTML 1.0 Strict or XHTML 1.1 andbe certain to follow the Web Content Accessibility Guidelines 1.0 (<!-- m --><a class="postlink" href="http://www.w3.org/TR/WCAG10/">http://www.w3.org/TR/WCAG10/</a><!-- m -->).<!--content-->