User Interface Sample Clauses

User Interface. The Publisher shall comply with the level A of the Web Accessibility Initiative (WAI) Guidelines of the World Wide Web Consortium (W3C) and use all best efforts to comply with the level AA of the WAI Guidelines of W3C.
User Interface. The target Uptime Percentage for User Interface shall be Ninety Nine Percent (99%) (the “Uptime Commitment”). Subject to the exclusions described in Section III (3) below, the “Uptime Percentage for User Interface” is calculated by subtracting from 100% the percentage of 1-minute periods during any quarterly cycle (i.e., 3 calendar months) in which Customer’s ability to access the Qubit online user interface is Unavailable out of the total number of minutes in that quarterly cycle. “Unavailable” and “Unavailabilitymean that, in any 1-minute period, all connection requests made by Customer to access the Qubit online user interface were unsuccessful (each a “Failed Connection”); provided, however, that no Failed Connection will be counted as a part of more than one such 1-minute period (e.g. a Failed Connection will not be counted for the period 12:00:00-12:00:59 and the period 12:00:30-12:01:29). The Uptime Percentage for User Interface shall be measured based on the industry standard monitoring tools Qubit uses.
User Interface. Our current SAV prototype includes an administrative user interface that lets a manager examine and modify the reposi- tory. In general, the goals for such an interface are as follows:1. The user must be able to locate specific digital objects in the repository, even if the repository contains large numbers of objects.2. The user must be able to easily perform structuringoperations on objects, such as grouping related objects into sets, and to view the topology of object structures.3. The user must be easily able to set configuration parameters of the system. This includes defining replication agreements.4. The interface module must not significantly detract from the performance of the rest of the system. The best way to achieve these goals is to provide specialized types of views into the repository:objects view: A general view which can display any object in the archive.structure views: Views that display common objects struc- tures, such as sets or version chains.configuration views: Views which allow a user to configure the system and its replication agreements.Our SAV prototype currently includes four different views, and will be extended to include others. Due to space lim- itations, in this section we only briefly illustrate two of the views. For a complete discussion, which covers performance issues related to the user interface, please see [4].Figure 8 is a screen shot of our set interface (an example of a structure view). The objects that participate in sets can be Figure 8: The Sets view viewed through a more generic interface (not shown here), but the set interface is especially tailored to show sets and their members clearly.In the set view, only sets and their members are shown. A set is represented by the “stacked document” icon, and a set member is represented by the “single document” icon. The default view shows all of the sets in the repository and a descriptive string.4 The filter window (bottom of Figure 8) can be used to restrict which sets are shown (using regular expressions). Set objects can be expanded (by clicking on the icon) to show the set members. If one of these members is another set, that set can be further expanded to show its members. The “View” button on the left lets one view the contents (label, value pairs) of a selected digital object. (A separate, specialized view window is opened.)Because a structure view is specific to a particular object structure, it can also be used as an interface for constructing that particu...
User Interface. Display: 4-character LCD Alphanumeric display • Panel Indicators: • Actual Temp LEDSetpoint Temp LED • Alarm LED • Keypad: • 4 buttons, glass-reinforced epoxy laminate faceplate • Next, Up, Down, Menu
User Interface. The Publisher shall use all best efforts to comply with the Web Accessibility Initiative (WAI) Guidelines of the World Wide Web Consortium (W3C).
User Interface. 5.1.1 Manufacturers are encouraged to design products in accordance with the user interface standard, IEEE P1621: Standard for User Interface Elements in Power Control of Electronic Devices Employed in Office/Consumer Environments. For details, see http://energy.lbl.gov/controls/.
User Interface. AOL reserves the right to review and approve the user interface and site design prior to launch of the Promotions and to conduct focus group testing to assess compliance with respect to such consultation and with respect to DigitalWork's compliance with the preceding sentence.
User Interface. 6 [ ] Interface...........................................7