1. Overview This recommended practice provides guidance for designing and implementing well-engineered Web pages for use in managed Web sites. The goal of this recommended practice is to improve the productivity of managed Web operations in terms of: a) locating relevant information, b) facilitating ease of use, c) reducing legal liabilities, and d) providing for efficient development and maintenance practices. This recommended practice will focus on vendor- and product-independent considerations. This recommended practice provides guidance for persons designing and developing Web pages, and managers responsible for establishing guidelines for Web site development.
1.1 Scope This document defines recommended practices for World Wide Web page engineering for Intranet and Extranet environments, based on World Wide Web Consortium (W3C®) and related industry guidelines. This recommended practice does not address stylistic considerations or human-factors considerations in Web page design beyond limitations that reflect good engineering practice. Annex B contains topics which are not sufficiently mature or where there are not specific recommendations for inclusion in the current issue of this recommended practice.
1.2 Purpose This recommended practice is intended to provide guidance to Web page developers in Intranet (organizational internal), and Extranet (amongst a limited domain of organizational participants) Web environments on recommended practices for Web page engineering. The objective is to improve the productivity of Intranet/Extranet Web operations in terms of locating relevant information, and efficient development and maintenance practices. The 2002 revision of this recommended practice addresses items identified in Annex A of IEEE Std 2001- 1999 [B14]1 which can be well-defined and to respond to emerging technology and changes in practice that have resulted in new material or changes to approved recommendations. Conformance to this recommended practice in developing and publishing a Web site provides a basis for a well-engineered Web site.
1.3 Conformance This recommended practice defines two forms of conformance: “IEEE Std 2001-2002-conforming Web page” and “IEEE Std 2001-2002-conforming Web page generation tool.” Throughout this recommended practice, the use of the verb shall indicates a requirement of the standard; the use of the verb should indicates a recommendation; and the use of the verb may indicates an option or variation that is permitted by the recommended practice. Although users of this recommended practice are strongly encouraged to consider the recommendations made within, the implementation of recommendations is not a requirement of Web page conformance.
1.3.1 IEEE Std 2001-2002-conforming Web page A conforming Web page implements all the requirements of this recommended practice. A Web page that conforms to this recommended practice may indicate this by the use of the following tag: NOTE—The HTML Reference Designator (HREF value will change with each version of this recommended practice. Tools should use the HREF value to determine the version of the standard being used. The image file may be downloaded and referenced using relative Uniform Resource Identifiers (URIs), but the target HTML file must be referenced by an absolute URI. Consistent with 4.1.10 of this recommended practice, a meta statement indicating conformance to this recommended practice may be included. This statement is: ”
1.3.2 IEEE Std 2001-2002-conforming Web page generation tool A product for generating well-engineered Web pages dynamically, or as an authoring tool, conforms to IEEE Std 2001-2002 if it satisfies all of the following conditions: a) It generates pages that conform to the XHTML DTD recommendation of the W3C, or it documents which DTDs it supports. b) It generates pages which comply with the DTD selection of the user. c) For versions HTML 3.2 and higher, or XML; it supports Cascading Style Sheets (CSS) 1.0 or higher, or it supports XSL and, in either case, it documents the use of this function and identifies which recommendations are supported. d) It generates pages that conform to all of the requirements, recommendations, and options of this recommended practice. Tools may allow for creation of non-conforming pages as a user option (in which case the IEEE 2001 tag cannot be included on the page.) e) It supports the Web Consortium’s Authoring Tool Accessibility Guidelines (see 2.8)