RFC 3875 - The Common Gateway Interface (CGI) Version 1.1. [Docs] [txt|pdf] [draft-coar-cgi-v11] [Diff1] [Diff2] [Errata] INFORMATIONAL Errata Exist Network Working Group D. Robinson Request for Comments: 3875 K. Coar Category: Informational The Apache Software Foundation October 2004 Status of this Memo This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. RFC 3875 CGI Version 1.1 October 2004 Table of Contents 1. RFC 3875 CGI Version 1.1 October 2004 5. RFC 3875 CGI Version 1.1 October 2004 1. 1.1. The Common Gateway Interface (CGI) [22] allows an HTTP [1], [4] server and a CGI script to share responsibility for responding to client requests. 1.2. The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY' and 'OPTIONAL' in this document are to be interpreted as described in BCP 14, RFC 2119 [3]. 1.3. Not all of the functions and features of the CGI are defined in the main part of this specification. 1.4. HTML Techniques for Web Content Accessibility Guidelines 1.0. W3C Note 6 November 2000 This version: (plain text, PostScript, PDF, gzip tar file of HTML, zip archive of HTML) Latest version: Previous version: Editors: Wendy Chisholm, W3C; Gregg Vanderheiden, Trace R & D Center University of Wisconsin -- Madison; Ian Jacobs, W3C Copyright ©1999 - 2000 W3C® (MIT, INRIA, Keio), All Rights Reserved.
Abstract This document describes techniques for authoring accessible Hypertext Markup Language (HTML) content (refer to HTML 4.01 [HTML4]). This document is part of a series of documents about techniques for authoring accessible Web content. Note: This document contains a number of examples that illustrate accessible solutions in CSS but also deprecated examples that illustrate what content developers should not do. Status of this document 1 Document structure and metadata Checkpoints in this section: Example. HTML Test Suite for UAAG 1.0 (Draft) On this page: Test 1 | References | About these tests Nearby: More HTML 4.01 Tests | UAAG 1.0 Test Suite UAAG 1.0 Requirement Checkpoint 1.1 Full keyboard access (Priority 1 ) Provision 1 : Ensure that the user can operate, through keyboard input alone, any user agent functionality available through the user interface.
Test 1 : Procedure Using the standard keyboard or an assistive technology that emulates the keyboard, uncheck and check the two checkboxes on this page. Run test Expected results Using the keyboard or an assistive technology that emulates the keyboard, the user checks and unchecks the checkboxes Source code <form action=".. References HTML 4.01 specification for CHECKBOX About this test suite This test is part of a test suite for the User Agent Accessibility Guidelines (UAAG) 1.0 . Test created by: Colin Koteles. Forms in HTML documents. 17.1 Introduction to forms An HTML form is a section of a document containing normal content, markup, special elements called controls (checkboxes, radio buttons, menus, etc.), and labels on those controls.
Users generally "complete" a form by modifying its controls (entering text, selecting menu items, etc.), before submitting the form to an agent for processing (e.g., to a Web server, to a mail server, etc.) Here's a simple form that includes labels, radio buttons, and push buttons (reset the form or submit it): <FORM action=" method="post"><P><LABEL for="firstname">First name: </LABEL><INPUT type="text" id="firstname"><BR><LABEL for="lastname">Last name: </LABEL><INPUT type="text" id="lastname"><BR><LABEL for="email">email: </LABEL><INPUT type="text" id="email"><BR><INPUT type="radio" name="sex" value="Male"> Male<BR><INPUT type="radio" name="sex" value="Female"> Female<BR><INPUT type="submit" value="Send"><INPUT type="reset"></P></FORM> Note.
Controls. Mailto. Tabbed form navigation. 17.1 Introduction to forms An HTML form is a section of a document containing normal content, markup, special elements called controls (checkboxes, radio buttons, menus, etc.), and labels on those controls. Users generally "complete" a form by modifying its controls (entering text, selecting menu items, etc.), before submitting the form to an agent for processing (e.g., to a Web server, to a mail server, etc.)
Here's a simple form that includes labels, radio buttons, and push buttons (reset the form or submit it): <FORM action=" method="post"><P><LABEL for="firstname">First name: </LABEL><INPUT type="text" id="firstname"><BR><LABEL for="lastname">Last name: </LABEL><INPUT type="text" id="lastname"><BR><LABEL for="email">email: </LABEL><INPUT type="text" id="email"><BR><INPUT type="radio" name="sex" value="Male"> Male<BR><INPUT type="radio" name="sex" value="Female"> Female<BR><INPUT type="submit" value="Send"><INPUT type="reset"></P></FORM> Note. Controls. Form data. HTML5: Techniques for providing useful text alternatives. 2. Introduction Text Alternatives Text alternatives are a primary way of making visual information accessible, because they can be rendered through any sensory modality (for example, visual, auditory or tactile) to match the needs of the user.
Providing text alternatives allows the information to be rendered in a variety of ways by a variety of user agents. To determine appropriate text alternatives it is important to think about why an image is being included in a document. Examples of scenarios where users benefit from text alternatives for images They have a very slow connection and are browsing with images disabled.
General Text Alternative Good Practices Provide the same informational content as the image. 2.1 A simple alt text decision tree A simple informative process for deciding if and what an alt text should be: Is this image the only content of a link or form control? 2.2 Conformance 2.1.1 Compliance with other specifications This section is non-normative. 3.
Example 1.1 Example 1.2. 4.9 Tabular data — HTML5. 4.9 Tabular data 4.9.1 The table element Categories: Flow content. Palpable content. Contexts in which this element can be used: Where flow content is expected. Content model: In this order: optionally a caption element, followed by zero or more colgroup elements, followed optionally by a thead element, followed optionally by a tfoot element, followed by either zero or more tbody elements or one or more tr elements, followed optionally by a tfoot element (but there can only be one tfoot element child in total), optionally intermixed with one or more script-supporting elements. Content attributes: Global attributes DOM interface: interface HTMLTableElement : HTMLElement { attribute HTMLTableCaptionElement? The table element represents data with more than one dimension, in the form of a table.
The table element takes part in the table model. Precise rules for determining whether this conformance requirement is met are described in the description of the table model. The border . caption [ = ] . tHead [ = ] Web Developer Installed. HTML 4.01 Specification. Abstract This specification defines the HyperText Markup Language (HTML), the publishing language of the World Wide Web. This specification defines HTML 4.01, which is a subversion of HTML 4. In addition to the text, multimedia, and hyperlink features of the previous versions of HTML (HTML 3.2 [HTML32] and HTML 2.0 [RFC1866]), HTML 4 supports more multimedia options, scripting languages, style sheets, better printing facilities, and documents that are more accessible to users with disabilities.
HTML 4 also takes great strides towards the internationalization of documents, with the goal of making the Web truly World Wide. HTML 4 is an SGML application conforming to International Standard ISO 8879 -- Standard Generalized Markup Language [ISO8879]. Status of this document This section describes the status of this document at the time of its publication. This document has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation.
Index of the HTML 4 Elements. Index of the HTML 4 Attributes. The W3C Markup Validation Service. The W3C CSS Validation Service. XHTML 1.0: The Extensible HyperText Markup Language (Second Edition) A Reformulation of HTML 4 in XML 1.0 W3C Recommendation 26 January 2000, revised 1 August 2002 superseded 27 March 2018 This version: Latest version: Previous version: Authors: See acknowledgments.
Please refer to the errata for this document, which may include some normative corrections. This document is also available in these non-normative formats: Multi-part XHTML file, PostScript version, PDF version, ZIP archive, and Gzip'd TAR archive. Copyright ©2002 W3C® (MIT, INRIA, Keio), All Rights Reserved. Abstract This specification defines the Second Edition of XHTML 1.0, a reformulation of HTML 4 as an XML 1.0 application, and three DTDs corresponding to the ones defined by HTML 4. Status of this document This section describes the status of this document at the time of its publication. This specification is a Superseded Recommendation. This section is informative. 1.1. 1.2. May a. Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification. This specification defines Cascading Style Sheets, level 2 revision 1 (CSS 2.1). CSS 2.1 is a style sheet language that allows authors and users to attach style (e.g., fonts and spacing) to structured documents (e.g., HTML documents and XML applications).
By separating the presentation style of documents from the content of documents, CSS 2.1 simplifies Web authoring and site maintenance. CSS 2.1 builds on CSS2 [CSS2] which builds on CSS1 [CSS1]. It supports media-specific style sheets so that authors may tailor the presentation of their documents to visual browsers, aural devices, printers, braille devices, handheld devices, etc. CSS 2.1 corrects a few errors in CSS2 (the most important being a new definition of the height/width of absolutely positioned elements, more influence for HTML's "style" attribute and a new calculation of the 'clip' property), and adds a few highly requested features which have already been widely implemented.
Media types. 7.1 Introduction to media types One of the most important features of style sheets is that they specify how a document is to be presented on different media: on the screen, on paper, with a speech synthesizer, with a braille device, etc. Certain CSS properties are only designed for certain media (e.g., the 'page-break-before' property only applies to paged media). On occasion, however, style sheets for different media types may share a property, but require different values for that property. For example, the 'font-size' property is useful both for screen and print media. The two media types are different enough to require different values for the common property; a document will typically need a larger font on a computer screen than on paper.
Therefore, it is necessary to express that a style sheet, or a section of a style sheet, applies to certain media types. 7.2 Specifying media-dependent style sheets There are currently two ways to specify media dependencies for style sheets: all print. Visual formatting model. 9.1 Introduction to the visual formatting model This chapter and the next describe the visual formatting model: how user agents process the document tree for visual media. In the visual formatting model, each element in the document tree generates zero or more boxes according to the box model. The layout of these boxes is governed by: box dimensions and type. positioning scheme (normal flow, float, and absolute positioning). relationships between elements in the document tree.external information (e.g., viewport size, intrinsic dimensions of images, etc.).
The properties defined in this chapter and the next apply to both continuous media and paged media. The visual formatting model does not specify all aspects of formatting (e.g., it does not specify a letter-spacing algorithm). 9.1.1 The viewport User agents for continuous media generally offer users a viewport (a window or other viewing area on the screen) through which users consult a document. 9.1.2 Containing blocks containing block . <! An. Positioning - Visual formatting model. 9.1 Introduction to the visual formatting model This chapter and the next describe the visual formatting model: how user agents process the document tree for visual media. In the visual formatting model, each element in the document tree generates zero or more boxes according to the box model. The layout of these boxes is governed by: box dimensions and type. positioning scheme (normal flow, float, and absolute positioning). relationships between elements in the document tree.external information (e.g., viewport size, intrinsic dimensions of images, etc.).
The properties defined in this chapter and the next apply to both continuous media and paged media. However, the meanings of the margin properties vary when applied to paged media (see the page model for details). The visual formatting model does not specify all aspects of formatting (e.g., it does not specify a letter-spacing algorithm). 9.1.1 The viewport User agents for continuous media generally offer users a viewport containing block . Box model. Contents The CSS box model describes the rectangular boxes that are generated for elements in the document tree and laid out according to the visual formatting model. 8.1 Box dimensions Each box has a content area (e.g., text, an image, etc.) and optional surrounding padding border , and margin areas; the size of each area is specified by properties defined below.
The margin, border, and padding can be broken down into top, right, bottom, and left segments (e.g., in the diagram, "LM" for left margin, "RP" for right padding, "TB" for top border, etc.). The perimeter of each of the four areas (content, padding, border, and margin) is called an "edge", so each box has four edges: content edge or inner edge The content edge surrounds the rectangle given by the width and height of the box, which often depend on the element's rendered content. Content box padding edge The padding edge surrounds the box padding. Padding box border edge The border edge surrounds the box's border. Border box margin box and auto. Assigning property values, Cascading, and Inheritance. 6.1 Specified, computed, and actual values Once a user agent has parsed a document and constructed a document tree, it must assign, for every element in the tree, a value to every property that applies to the target media type.
The final value of a property is the result of a four-step calculation: the value is determined through specification (the "specified value"), then resolved into a value that is used for inheritance (the "computed value"), then converted into an absolute value if necessary (the "used value"), and finally transformed according to the limitations of the local environment (the "actual value"). 6.1.1 Specified values User agents must first assign a specified value to each property based on the following mechanisms (in order of precedence): If the cascade results in a value, use it. Otherwise, if the property is inherited and the element is not the root of the document tree, use the computed value of the parent element. Otherwise use the property's initial value. The. Fonts. Typography on the Web - W3C Wiki. W3C Opens Typography on the Web.
WOFF File Format 1.0. Character entity references in HTML 4.