Scripting languages are widely used, and supported by most recent browsers. Scripts can operate on the server side using, for example, the common gateway interface (CGI) or on the client side through scripts embedded in the page or applets. However, not all browsers support client-side scripts and users may turn off both Java and client side scripting. This may be a matter of corporate security policy, or to reduce the distraction of intrusive dynamic elements.
The W3C WAI stipulates that any Web page using client-side scripts must provide the same functionality on the page without the scripts in order to be considered accessible. Dynamic page creation should be focused on server side scripting/programming. This facilitates end-user accessibility, the range of target devices, and security.
Java is currently a key language of the Internet. This is also the case for Intranets, since considerable corporate application functionality can be provided through the use of applets client-side communicating with servlets server-side, and capable of yielding generally superior performance and security to CGI scripts. The recent advent of application service providers in the Internet is likely to accelerate the use of Java.
Java foundation classes (JFC) with the swing architecture and the accessibility classes offer interface flexibility and accommodation to users with disabilities that are not possible using DHTML and style sheets. Current browser offerings do not yet support all of the JFC. For some applications, HTML may be secondary to the Java portions of a Web page, acting only as a carrier for multiple applets that do the actual work and presentation of the page.
The W3C WAI stipulates that, to be accessible, a page containing an applet must be capable of operating without the applet. This may also be required to serve clients where Java is disabled for policy or security reasons. Server side applications and detection of client preferences can be used to meet this objective.