- dynamic content
-
From Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 1.0 (2004-01-15) | Glossary for this source
Content that is generated in response to a request. This may
be
used for content that depends on changing environmental factors
such as time (e.g., stock quotes) or place (e.g., nearby gas
stations)
- element content
-
From Extensible Markup Language (XML) 1.1 (2004-02-04) | Glossary for this source
An element type has element content when elements of that type MUST contain only child elements (no character data), optionally separated by white space (characters matching the nonterminal S).
- element content
-
From Extensible Markup Language (XML) 1.0 (2000-10-06) | Glossary for this source
An element type has element content when elements of that type must contain only child elements (no character data), optionally separated by white space (characters matching the nonterminal S).
- equivalent (for content)
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source
The term "equivalent" is used in this document as it is used in the Web Content Accessibility Guidelines 1.0 [WCAG10]: Content is "equivalent" to other content when both fulfill essentially the same function or purpose upon presentation to the user. In the context of this document, the equivalent must fulfill essentially the same function for the person with a disability (at least insofar as is feasible, given the nature of the disability and the state of technology), as the primary content does for the person without any disability.Equivalents include text equivalents (e.g., text equivalents for images, text transcripts for audio tracks, or collated text transcripts for a movie) and non-text equivalents (e.g., a prerecorded audio description of a visual track of a movie, or a sign language video rendition of a written text).Each markup language defines its own mechanisms for specifying conditional content, and these mechanisms may be used by authors to provide text equivalents. For instance, in HTML 4 [HTML4] or SMIL 1.0 [SMIL], authors may use the alt attribute to specify a text equivalent for some elements. In HTML 4, authors may provide equivalents and other conditional content in attribute values (e.g., the summary attribute for the TABLE element), in element content (e.g., OBJECT for external content it specifies, NOFRAMES for frame equivalents, and NOSCRIPT for script equivalents), and in prose. Please consult the Web Content Accessibility Guidelines 1.0 [WCAG10] and its associated Techniques document [WCAG10-TECHS] for more information about equivalents.
- executable content
-
From Voice Extensible Markup Language (VoiceXML) Version 2.0 (2004-03-16) | Glossary for this source
Procedural logic that occurs in <block>,
<filled>, and
event handlers
.
- focus, content focus, user interface focus,user
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source
In this document, the term "content focus" (required by checkpoint 9.1) refers to a user agent mechanism that has all of the following properties: It designates zero or one element in content that is either enabled or disabled. In general, the focus should only designate enabled elements, but it may also designate disabled elements.It has state, i.e., it may be "set" on an enabled element, programmatically or through the user interface. Some content specifications (e.g., HTML, CSS) allow authors to associate behavior with focus set and unset events.Once it has been set, it may be used to trigger other behaviors associated with the enabled element (e.g., the user may activate a link or change the state of a form control). These behaviors may be triggered programmatically or through the user interface (e.g., through keyboard events).User interface mechanisms may resemble content focus, but do not satisfy all of the properties. For example, designers of word processing software often implement a "caret" that indicates the current location of text input or editing. The caret may have state and may respond to input device events, but it does not enable users to activate the behaviors associated with enabled elements.The user interface focus shares the properties of the content focus except that, rather than designating pieces of content, it designates zero or one control of the user agent user interface that has associated behaviors (e.g., a radio button, text box, or menu).On the screen, the user agent may highlight the content focus in a variety of ways, including through colors, fonts, graphics, and magnification. The user agent may also highlight the content focus when rendered as synthesized speech, for example through changes in speech prosody. The dimensions of the rendered content focus may exceed those of the viewport.In this document, each viewport is expected to have at most one content focus and at most one user interface focus. This document includes requirements for content focus only, for user interface focus only, and for both. When a requirement refers to both, the term "focus" is used.When several viewports coexist, at most one viewport's content focus or user interface focus responds to input events; this is called the current focus.
- mixed content
-
From Extensible Markup Language (XML) 1.1 (2004-02-04) | Glossary for this source
An element type has mixed content when elements of that type MAY contain character data, optionally interspersed with child elements.
- mixed content
-
From Extensible Markup Language (XML) 1.0 (2000-10-06) | Glossary for this source
An element type has mixed content when elements of that type may contain character data, optionally interspersed with child elements.
- negotiate content
-
From Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 1.0 (2004-01-15) | Glossary for this source
Message content that has been selected by content
negotiation.
- non-variant content
-
From Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 1.0 (2004-01-15) | Glossary for this source
When the form/format of the content being sent does not
depend
on receiver's capabilities and/or preferences
- operator, content element
-
From Mathematical Markup Language (MathML) Version 2.0 (2001-02-21) | Glossary for this source
A mathematical object that is applied to arguments using the apply element.
- reference in content
-
From Extensible Markup Language (XML) 1.1 (2004-02-04) | Glossary for this source
as a reference anywhere after the start-tag and before the end-tag of an element; corresponds to the nonterminal content.
- reference in content
-
From Extensible Markup Language (XML) 1.0 (2000-10-06) | Glossary for this source
as a reference anywhere after the start-tag and before the end-tag of an element; corresponds to the nonterminal content.
- rendered content
-
From Glossary of Cascading Style Sheets, level 2 CSS2 Specification (1998-05-12) | Glossary for this source
The content of an element after the rendering that applies to it according to the relevant style sheets has been applied. The rendered content of a replaced element comes from outside the source document. Rendered content may also be alternate text for an element (e.g., the value of the HTML "alt" attribute), and may include items inserted implicitly or explicitly by the style sheet, such as bullets, numbering, etc.
- rendered content, rendered text
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source
Rendered content is the part of content that the user agent makes available to the user's senses of sight and hearing (and only those senses for the purposes of this document). Any content that causes an effect that may be perceived through these senses constitutes rendered content. This includes text characters, images, style sheets, scripts, and anything else in content that, once processed, may be perceived through sight and hearing.The term "rendered text" refers to text content that is rendered in a way that communicates information about the characters themselves, whether visually or as synthesized speech.In the context of this document, invisible content is content that is not rendered but that may influence the graphical rendering (e.g., layout) of other content. Similarly, silent content is content that is not rendered but that may influence the audio rendering of other content. Neither invisible nor silent content is considered rendered content.
- repair content, repair text
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source
In this document, the term "repair content" refers to content generated by the user agent in order to correct an error condition. "Repair text" refers to the text portion of repair content. Some error conditions that may lead to the generation of repair content include: Erroneous or incomplete content (e.g., ill-formed markup, invalid markup, or missing conditional content that is required by format specification);Missing resources for handling or rendering content (e.g., the user agent lacks a font family to display some characters, or the user agent does not implement a particular scripting language).This document does not require user agents to include repair content in the document object. Repair content inserted in the document object should conform to the Web Content Accessibility Guidelines 1.0 [WCAG10]. For more information about repair techniques for Web content and software, refer to "Techniques for Authoring Tool Accessibility Guidelines 1.0" [ATAG10-TECHS].
- separation of form from content
-
From Glossary of "Weaving the Web" (1999-07-23) | Glossary for this source
The principle that one should represent separately the essence
of a document and the style with which it is presented. An element
in my decision to use SGML and an important element in the drive
for accessibility on the Web.
- size and color of non-text content
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source
This document includes some checkpoints to ensure that the user is able to control the size and color of visually rendered text content (checkpoints 4.1 and 4.3). This document does not in general address control of the size and color of visually rendered non-text content (e.g., images).Note: A user agent may implement resizing functionalities as part of conformance to other specifications (e.g., Scalable Vector Graphics [SVG]).
- tables of contents
-
From Web Content Accessibility Guidelines 1.0 (1999-05-05) | Glossary for this source
A table of contents generally lists (and links to) the most important sections of a document.
- text content, non-text content,non-text
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source
As used in this document a "text element" adds text characters to either content or the user interface. Both in the Web Content Accessibility Guidelines 1.0 [WCAG10] and in this document, text elements are presumed to produce text that can be understood when rendered visually, as synthesized speech, or as Braille. Such text elements benefit at least these three groups of users: visually-displayed text benefits users who are deaf and adept in reading visually-displayed text;synthesized speech benefits users who are blind and adept in use of synthesized speech;braille benefits users who are blind, and possibly deaf-blind, and adept at reading braille.A text element may consist of both text and non-text data. For instance, a text element may contain markup for style (e.g., font size or color), structure (e.g., heading levels), and other semantics. The essential function of the text element should be retained even if style information happens to be lost in rendering.A user agent may have to process a text element in order to have access to the text characters. For instance, a text element may consist of markup, it may be encrypted or compressed, or it may include embedded text in a binary format (e.g., JPEG)."Text content" is content that is composed of one or more text elements. A "text equivalent" (whether in content or the user interface) is an equivalent composed of one or more text elements. Authors generally provide text equivalents for content by using the conditional content mechanisms of a specification.A "non-text element" is an element (in content or the user interface) that does not have the qualities of a text element. "Non-text content" is composed of one or more non-text elements. A "non-text equivalent" (whether in content or the user interface) is an equivalent composed of one or more non-text elements.