Example for Checkpoint
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.

Content developers must ensure that pages are accessible with scripts turned off or in browsers that don't support scripts.

• Avoid creating content on the fly locally (client-side). If a user's browser does not handle scripts, no content will be generated or displayed. However, this is different than displaying or hiding already existing content by using a combination of style sheets and scripting; if there is no script, then the content is always shown. This also does not rule out generating pages on the fly on the server-side and delivering them to the client.
  
  
• Avoid creating links that use "javascript" as the URI. If a user is not using scripts, then they won't be able to link since the browser can't create the link content. For example, do NOT do this:
  
  <A href="javascript:">...</A>
  Because this is a dead-end link for a user agent where scripts are not supported or not loaded.