- at user option
-
From Extensible Markup Language (XML) 1.1 (2004-02-04) | Glossary for this source
Conforming software MAY or MUST (depending on the modal verb in the sentence) behave as described; if it does, it MUST provide users a means to enable or disable the behavior described.
- at user option
-
From Extensible Markup Language (XML) 1.0 (2000-10-06) | Glossary for this source
Conforming software may or must (depending on the modal verb in the sentence) behave as described; if it does, it must provide users a means to enable or disable the behavior described.
- explicit user request
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source
In this document, the term "explicit user request" refers to any user interaction through the user agent user interface (not through rendered content), the focus, or the selection. User requests are made, for example, through user agent user interface controls and keyboard bindings.Some examples of explicit user requests include when the user selects "New viewport," responds "yes" to a prompt in the user agent's user interface, configures the user agent to behave in a certain way, or changes the selection or focus with the keyboard or pointing device.Note: Users make mistakes. For example, a user may inadvertently respond "yes" to a prompt instead of "no." In this document, this type of mistake is still considered an explicit user request.
- 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.
- functional user experience
-
From Glossary of Terms for Device Independence (2005-01-18) | Glossary for this source
- harmonized user experience
-
From Glossary of Terms for Device Independence (2005-01-18) | Glossary for this source
- user
-
From Web Characterization Terminology & Definitions Sheet (1999-05-24) | Glossary for this source
The principal using a client to interactively retrieve and render
resources or resource manifestations.
- user
-
From Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 1.0 (2004-01-15) | Glossary for this source
An individual or group of individuals acting as a single
entity. The user is further qualified as an entity who uses a
device to request content and/or resource from a server.
- user
-
From Glossary of Cascading Style Sheets, level 2 CSS2 Specification (1998-05-12) | Glossary for this source
A user is a person who interacts with a user agent to view, hear, or otherwise use a document and its associated style sheet. The user may provide a personal style sheet that encodes personal preferences.A user agent is any program that interprets a document written in the document language and applies associated style sheets according to the terms of this specification. A user agent may display a document, read it aloud, cause it to be printed, convert it to another format, etc.
- user
-
From Voice Extensible Markup Language (VoiceXML) Version 2.0 (2004-03-16) | Glossary for this source
A person whose interaction with an
implementation
platform
is controlled by a
VoiceXML interpreter
.
- user
-
From Glossary of Terms for Device Independence (2005-01-18) | Glossary for this source
A human who perceives and
interacts
with the web
- user
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16) | Glossary for this source
An individual (or group of individuals acting as a single entity) on whose behalf a service is accessed and for which personal data exists. P3P policies describe the collection and use of personal data about this individual or group.A program whose purpose is to mediate interactions with services on behalf of the user under the user's preferences. A user may have more than one user agent, and agents need not reside on the user's desktop, but any agent must be controlled by and act on behalf of only the user. The trust relationship between a user and his or her agent may be governed by constraints outside of P3P. For instance, an agent may be trusted as a part of the user's operating system or Web client, or as a part of the terms and conditions of an ISP or privacy proxy.
- user agent
-
From XHTML 1.0: The Extensible HyperText Markup Language (Second Edition) (2000-01-26) | Glossary for this source
A user agent is a system that processes XHTML documents in accordance with this specification. See User Agent Conformance for more information.
- user agent
-
From Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 1.0 (2004-01-15) | Glossary for this source
A program, such as a browser, running on the device that acts
on a user's behalf. Users may use different user agents at
different times.
- user agent
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source
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
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03) | Glossary for this source
A "user agent" is software that retrieves and renders Web content. User agents include browsers, plug-ins for a particular media type, and some assistive technologies.
- user agent
-
From Web Content Accessibility Guidelines 1.0 (1999-05-05) | Glossary for this source
Software to access Web content, including desktop graphical browsers, text browsers, voice browsers, mobile phones, multimedia players, plug-ins, and some software assistive technologies used in conjunction with browsers such as screen readers, screen magnifiers, and voice recognition software.
- user agent
-
From Glossary of Terms for Device Independence (2005-01-18) | Glossary for this source
Browsers are examples of
user agents,
as are web robots that automatically traverse the web collecting
information.
- user agent
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16) | Glossary for this source
A program whose purpose is to mediate interactions with services on behalf of the user under the user's preferences. A user may have more than one user agent, and agents need not reside on the user's desktop, but any agent must be controlled by and act on behalf of only the user. The trust relationship between a user and his or her agent may be governed by constraints outside of P3P. For instance, an agent may be trusted as a part of the user's operating system or Web client, or as a part of the terms and conditions of an ISP or privacy proxy.
- user agent
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15) | Glossary for this source
The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user tools.