- support, implement, conform
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
In this document, the terms "support," "implement," and "conform" all refer to what a developer has designed a user agent to do, but they represent different degrees of specificity. A user agent "supports" general classes of objects, such as "images" or "Japanese." A user agent "implements" a specification (e.g., the PNG and SVG image format specifications or a particular scripting language), or an API (e.g., the DOM API) when it has been programmed to follow all or part of a specification. A user agent "conforms to" a specification when it implements the specification and satisfies its conformance criteria.
- synchronize
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
In this document, "to synchronize" refers to the act of time-coordinating two or more presentation components (e.g., a visual track with captions, or several tracks in a multimedia presentation). For Web content developers, the requirement to synchronize means to provide the data that will permit sensible time-coordinated rendering by a user agent. For example, Web content developers can ensure that the segments of caption text are neither too long nor too short, and that they map to segments of the visual track that are appropriate in length. For user agent developers, the requirement to synchronize means to present the content in a sensible time-coordinated fashion under a wide range of circumstances including technology constraints (e.g., small text-only displays), user limitations (slow reading speeds, large font sizes, high need for review or repeat functions), and content that is sub-optimal in terms of accessibility.
- text
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
In this document, the term "text" used by itself refers to a sequence of characters from a markup language's document character set. Refer to the "Character Model for the World Wide Web " [CHARMOD] for more information about text and characters. Note: This document makes use of other terms that include the word "text" that have highly specialized meanings: collated text transcript, non-text content, text content, non-text element, text element, text equivalent, and text transcript.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.In this document, a "text decoration" is any stylistic effect that the user agent may apply to visually rendered text that does not affect the layout of the document (i.e., does not require reformatting when applied or removed). Text decoration mechanisms include underline, overline, and strike-through.A text transcript is a text equivalent of audio information (e.g., an audio-only presentation or the audio track of a movie or other animation). It provides text for both spoken words and non-spoken sounds such as sound effects. Text transcripts make audio information accessible to people who have hearing disabilities and to people who cannot play the audio. Text transcripts are usually created by hand but may be generated on the fly (e.g., by voice-to-text converters). See also the definitions of captions and collated text transcripts.
- text content, non-text content,non-text
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
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.
- text decoration
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
In this document, a "text decoration" is any stylistic effect that the user agent may apply to visually rendered text that does not affect the layout of the document (i.e., does not require reformatting when applied or removed). Text decoration mechanisms include underline, overline, and strike-through.
- text transcript
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
A text transcript is a text equivalent of audio information (e.g., an audio-only presentation or the audio track of a movie or other animation). It provides text for both spoken words and non-spoken sounds such as sound effects. Text transcripts make audio information accessible to people who have hearing disabilities and to people who cannot play the audio. Text transcripts are usually created by hand but may be generated on the fly (e.g., by voice-to-text converters). See also the definitions of captions and collated text transcripts.
- time parameters
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
This document includes requirements (see checkpoints 2.4, 4.4, 4.5, and 4.9) for control of some time parameters. The requirements are for time parameters that the user agent recognizes and controls. This document does not include requirements for control of time parameters managed on the server.
- user agent
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
In this document, the term "user agent" is used in two ways: The software and documentation components that together, conform to the requirements of this document. This is the most common use of the term in this document and is the usage in the checkpoints.Any software that retrieves and renders Web content for users. This may include Web browsers, media players, plug-ins, and other programs — including assistive technologies — that help in retrieving and rendering Web content.User agent default styles are style property values applied in the absence of any author or user styles. Some markup languages specify a default rendering for content in that markup language; others do not. For example, XML 1.0 [XML] does not specify default styles for XML documents. HTML 4 [HTML4] does not specify default styles for HTML documents, but the CSS 2 [CSS2] specification suggests a sample default style sheet for HTML 4 based on current practice.
- user agent default styles
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
User agent default styles are style property values applied in the absence of any author or user styles. Some markup languages specify a default rendering for content in that markup language; others do not. For example, XML 1.0 [XML] does not specify default styles for XML documents. HTML 4 [HTML4] does not specify default styles for HTML documents, but the CSS 2 [CSS2] specification suggests a sample default style sheet for HTML 4 based on current practice.
- user control of every user interface component
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
This document distinguishes user interface features that are part of the user agent user interface and those that are part of content. Some checkpoints (e.g., those in guideline 5) require user control over rendering and behavior that is driven by content only. This document does not always explicitly require the same control over features of the user agent user interface. Nevertheless, this document (see checkpoint 7.3) does require user agents to follow software usability guidelines. The UAWG expects such usability guidelines to include requirements for user control over user interface behavior.Note: It is more difficult for users to distinguish content from user interface when both are rendered as sound in one temporal dimension, than it is when both are rendered visually in two spatial dimensions. Thus, the UAWG encourages developers of user agents that include audio output or synthesized speech output to apply the requirements of this document to both content and user agent components.
- user interface, user interface,
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
For the purposes of this document, user interface includes both: the user agent user interface, i.e., the controls (e.g., menus, buttons, prompts, and other components for input and output) and mechanisms (e.g., selection and focus) provided by the user agent ("out of the box") that are not created by content.the "content user interface," i.e., the enabled elements that are part of content, such as form controls, links, and applets. The document distinguishes them only where required for clarity. For more information, see the section on requirements for content, for user agent features, or both. The term "user interface control" refers to a component of the user agent user interface or the content user interface, distinguished where necessary.
- user styles
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
User styles are style property values that come from user interface settings, user style sheets, or other user interactions.
- video
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
This content type label refers to all of the requirements related to video for the following checkpoints: 2.5, 2.6, and 3.2. When this label is part of a conformance profile, the user agent must implement at least one video format. Furthermore, when this label is part of a profile, the user agent must satisfy the requirements of checkpoint 3.2 for all implemented video formats, not just those identified in a conformance profile. The video requirements apply to video content that is recognized as distinct and that, according to the encoding format, may be rendered as a coherent unit.
- view, viewport
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
The user agent renders content through one or more viewports. Viewports include windows, frames, pieces of paper, loudspeakers, and virtual magnifying glasses. A viewport may contain another viewport (e.g., nested frames). User agent user interface controls such as prompts, menus, and alerts are not viewports. Graphical and tactile viewports have two spatial dimensions. A viewport may also have temporal dimensions, for instance when audio, speech, animations, and movies are rendered. When the dimensions (spatial or temporal) of rendered content exceed the dimensions of the viewport, the user agent provides mechanisms such as scroll bars and advance and rewind controls so that the user can access the rendered content "outside" the viewport. Examples include: when the user can only view a portion of a large document through a small graphical viewport, or when audio content has already been played.When several viewports coexist, only one has the current focus at a given moment. This viewport is highlighted to make it stand out.User agents may render the same content in a variety of ways; each rendering is called a view. For instance, a user agent may allow users to view an entire document or just a list of the document's headers. These are two different views of the document.
- visual track
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
A visual object is content rendered through a graphical viewport. Visual objects include graphics, text, and visual portions of movies and other animations. A visual track is a visual object that is intended as a whole or partial presentation. A visual track does not necessarily correspond to a single physical object or software object.
- visual-only presentation
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
A visual-only presentation is content consisting exclusively of one or more visual tracks presented concurrently or in series. A silent movie is an example of a visual-only presentation.
- visualText
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
This content type label refers to all of the requirements related to visually rendered text for the following checkpoints: 3.3, 4.1, 4.2, and 4.3. If a user agent renders text visually, it must satisfy these requirements in order to conform, and this label must appear in a conformance profile. Furthermore, the user agent must satisfy these requirements for all implemented formats that produce visually rendered text, not just those identified in a conformance profile. An audio-only or tactile-only user agent is not required to satisfy the requirements associated with this label.
- voice
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
This input modality label refers to all of the generic input device requirements of this document as well as those specific to the keyboard, except for the requirements of checkpoint 11.4. This label is an indication that these requirements have been satisfied for voice input.
- voice browser
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
From "Introduction and Overview of W3C Speech Interface Framework" [VOICEBROWSER]: "A voice browser is a device (hardware and software) that interprets voice markup languages to generate voice output, interpret voice input, and possibly accept and produce other modalities of input and output."
- web resource
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
The term "Web resource" is used in this document in accordance with Web Characterization Terminology and Definitions Sheet [WEBCHAR] to mean anything that can be identified by a Uniform Resource Identifier (URI); refer to RFC 2396 [RFC2396].