Search results

Term entries in the full glossary matching "device"

W3C Glossaries

Showing results 1 - 5 of 5

application programming interface (API), conventional input/output/device API),

From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source

An application programming interface (API) defines how communication may take place between applications. Implementing APIs that are independent of a particular operating environment (as are the W3C DOM Level 2 specifications) may reduce implementation costs for multi-platform user agents and promote the development of multi-platform assistive technologies. Implementing conventional APIs for a particular operating environment may reduce implementation costs for assistive technology developers who wish to interoperate with more than one piece of software running on that operating environment.A "device API" defines how communication may take place with an input or output device such as a keyboard, mouse, or video card.In this document, an "input/output API" defines how applications or devices communicate with a user agent. As used in this document, input and output APIs include, but are not limited to, device APIs. Input and output APIs also include more abstract communication interfaces than those specified by device APIs. A "conventional input/output API" is one that is expected to be implemented by software running on a particular operating environment. For example, the conventional input APIs of the target user agent are for the mouse and keyboard. For touch screen devices or mobile devices, conventional input APIs may include stylus, buttons, and voice. The graphical display and sound card are considered conventional output devices for a graphical desktop computer environment, and each has an associated API.
device

From Glossary of Terms for Device Independence (2005-01-18) | Glossary for this source

An apparatus through which a user can perceive and interact with the Web
device independent

From Web Content Accessibility Guidelines 1.0 (1999-05-05) | Glossary for this source

Users must be able to interact with a user agent (and the document it renders) using the supported input and output devices of their choice and according to their needs. Input devices may include pointing devices, keyboards, braille devices, head wands, microphones, and others. Output devices may include monitors, speech synthesizers, and braille devices.Please note that "device-independent support" does not mean that user agents must support every input or output device. User agents should offer redundant input and output mechanisms for those devices that are supported. For example, if a user agent supports keyboard and mouse input, users should be able to interact with all features using either the keyboard or the mouse.
device-independence

From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source

In this document, device-independence refers to the desirable property that operation of a user agent feature is not bound to only one input or output device.
glossary of terms for device independence (version used forDevice

From Glossary of Terms for Device Independence (2005-01-18) | Glossary for this source

Glossary of Terms for Device Independence , Rhys Lewis, 2003. W3C Working Draft available at: http://www.w3.org/TR/2003/WD-di-gloss-20030825/

The Glossary System has been built by Pierre Candela during an internship in W3C; it's now maintained by Dominique Hazael-Massieux

Copyright © 2000-2003W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.