Prototype Implementations for a Universal Remote Console

20 downloads 0 Views 175KB Size Report
that can be used to control any electronic and information technology device .... tion on a computer via Bluetooth and UPnP, and a Compaq. iPAQ controlling a ...
CHI

Demonstrations

changing the world, changing ourselves

Prototype Implementations for a Universal Remote Console Specification Gottfried Zimmermann Ph.D., Gregg Vanderheiden Ph.D., Al Gilman Sc.D. Trace R&D Center, Univ. Wisconsin-Madison 5901 Research Park Blvd., Madison, WI, 53719 USA [email protected], [email protected], [email protected] Abstract A “Universal Remote Console” (URC) is a personal device that can be used to control any electronic and information technology device (target device/service), such as thermostats, TVs, or copy machines. The URC renders the user interface (UI) of the target device in a way that accommodates the user’s preferences and abilities. This paper introduces the efforts of user groups, industry, government and academia to develop a standard for “Alternate Interface Access” within the V2 technical committee of the National Committee for Information Technology Standards (NCITS). Some preliminary design aspects of the standard in work are discussed shortly. Keywords Universal usability, disability access, assistive technology, remote control, wireless computing, mobile devices, device independence, modality-independent user interface, standards development. INTRODUCTION With the growing pervasiveness of electronic technologies, more and more devices at home, in the office, at school, and in public places are equipped with digital processors controlling their user interfaces. Some of these devices come with dedicated remote controls for the convenience of the user (e.g. home equipment such as TVs, VCRs and stereos). However, these remote controls can only serve for a specific target device, and are usable only for a certain user group with “mainstream abilities” such as the ability to see clearly, and a certain degree of manual dexterity. At the same time, people with different types of disabilities find it difficult or impossible to directly use electronic devices, because the built-in user interface cannot accommodate the needs of different user groups (such as users with visual, hearing, or mobility impairments) in their standard user interface (UI). People with disabilities therefore often have to rely on devices that are especially designed for them. However, relying on “special devices” rather than being able to use standard devices has several disadvantages: First, it is expensive for those who have special needs, because their special devices are produced in small Copyright is held by the author/owner(s). CHI 2002, April 20-25, 2002, Minneapolis, Minnesota, USA. ACM 1-58113-454-1/02/0004.

510

numbers. Second, specialized devices are not manufactured in the same variety as their mainstream counterparts. This means, that people with disabilities do not have the same range of choices, and often must put up with devices implementing older technologies. Third, this approach doesn’t work for devices in public places (e.g. ATMs, and information kiosks), as it is not reasonable to install an exhaustive array of devices, each offering the same service, but tailored for a different user group. V2 UNIVERSAL REMOTE CONSOLE STANDARD A better approach for many products would be the development of a standard for allowing a separate device to be used as an alternate interface, an alternate “console” that could be used to control the standard devices that people encounter at home, at work and in their communities. In order to define a standard for flexible and replaceable user interfaces for electronic devices and services, NCITS has established a technical committee called V2 [2]. Members of this committee include representatives from user groups, industry, government, and academia. V2 is currently working on a “Universal Remote Console” (URC) specification as an essential part of a to-be-developed “Alternate Interface Access” standard. The URC approach is simple though powerful: A person carries their own “personal” device which can act as a remote console to other products. This personal device is tailored to their specific needs. It may involve graphical user interfaces, voice interfaces, braille-based interfaces, switch-based input methods, etc., or any combination of these. Typically, the personal remote console would be a mobile device like a PDA, a cell phone, or an inconspicuous wearable computer. The personal remote console is also a “universal” remote console, in that it would let the user control any target device or service, from the thermostat at home to the copy machine in the office, that supported the standard. The target device would simply transmit an abstract (i.e. modality-independent) user interface to the URC which would take care of providing the particular input and output mechanisms that are appropriate for its user. The URC approach means that it is not the target device manufacturer who is responsible for devising the different user interfaces suitable for all types of users. Instead, the device manufacturer need only supply the “interface needs” of their product in the standard format. The user would bring their own interface with them.

minneapolis, minnesota, usa • 20-25 april 2002

A SAMPLE SCENARIO To illustrate consider the following brief scenario: Clarissa uses a braille note-taker, a device a bit smaller than a hardcover book that has a braille display and keyboard and can be used by those who are blind or deafblind. Clarissa enters a building with an ATM, a building directory, and an elevator. As she enters the foyer, the braille note-taker displays a list of available V2 compatible services (ATM, Building Directory, and Elevator). Clarissa first selects ATM in order to get some cash. After reading the location on her braille display, she approaches the ATM and it prompts her for her PIN (on her braille display). She enters the PIN using her braille keyboard. Note that she does not have to swipe her credit card because she has authorized her note-taker to store that number for her and send it in encrypted form to the ATM. The ATM sends lists of selections to Clarissa as the different screens are displayed. She selects the menu items “withdraw money,” and “from checking account” sequentially on her braille device as well as entering the amount of money she wants. After taking her money from the ATM she again asks for the list of items around her, accesses the information from the electronic building directory to find the office she needs to visit. She then uses her device to operate the elevator and monitor its progress to her floor. DESIGN CONSIDERATIONS V2 is currently working on the definition of an XML-based language to convey an abstract UI description from the target device/service to the Universal Remote Console (URC). The abstract UI description can then be rendered on any URC device with varying concrete details allowing adapted access to all functions of the target device and service. The XML-based language defines a variety of abstract UI elements (called “abstract interactors”) for input and output operations. On the URC an abstract interactor is mapped to a “concrete interactor” available on its platform. The top priority for the design of this language is the preservation of access to all operations of the target across diverse modalities (sensory renderings and input techniques) on concrete URC platforms. The ability to tune the concrete UI for particular sensory presentations for esthetic reasons may be incorporated so long as they do not lead to the embedding of semantics which would not be present in all different renderings (or drive up the resource requirements on the URC). The standard is layered on existing communication and network standards such as 802.11, Bluetooth, Universal Plug and Play (UPnP), Java/Jini, and Salutation. The use of existing standards and gateways allows for the V2 work to be communication and network technology independent. PROTOTYPICAL IMPLEMENTATIONS In order to support the work of the V2 technical committee, the Trace Center has developed prototypical implementa-

Demonstrations

tions for the URC specification in work. The goals of this activity are (a) to explore the usefulness of different existing technologies for implementing the standard, (b) to identify the requirements of a URC specification regarding its underlying network environment, (c) to provide a testbed for the development of an XML-based language specification, and (d) to provide proof-of-concept implementations for the URC specification. Current prototypes (which will be shown at the demonstration) include a Handspring Visor controlling a TV simulation on a computer via Bluetooth and UPnP, and a Compaq iPAQ controlling a TV simulation via 802.11b and Jini. RELATED WORK The idea of a “universal remote controller” is inherent to a multitude of research and development projects. Some of these include Trace input emulation efforts [5] and the Universal Remote Console Communication (URCC) Protocol [6]; the Pebbles project at Carnegie Mellon University [3]; the Total Access System [4] from Stanford University and Sun’s work with Jini technology and remote control [1]. CONCLUSIONS The V2 standardization effort is an ongoing activity of user groups, industry, government and academia, under the auspices of NCITS. The emerging V2 standard which is expected in 2002/2003 will address the alternate interface connection needs of people with and without disabilities. The URC specification will enable people using their personal URC devices to control electronic devices and services in their environment. ACKNOWLEDGMENTS This work was funded by the National Institute on Disability and Rehabilitation Research (NIDRR), US Dept. of Education under grant H133E980008. Opinions expressed are those of the authors and not the funding agencies or V2. REFERENCES 1. Beard, M., & Korn, P. (2001). What I Need is What I Get: Downloadable User Interfaces via Jini and Java. CHI 2001 Extended Abstracts, pp. 15-16. 2. NCITS V2 - Standards Development Committee on Information Technology Access Interfaces. www.ncits.org/tc_home/v2htm/V2docs/v201011.htm. 3. Nichols, J., & Myers, B.A. (2001). Studying The Use of Handhelds To Control Everyday Appliances. www-2.cs.cmu.edu/~pebbles/papers/pebblespuc.pdf. 4. Scott, N.G., & Gingras, I. (2001). The Total Access System. CHI 2001 Extended Abstracts, pp. 13-14. 5. Vanderheiden, G. (1981). Practical Applications of Microcomputers to Aid the Handicapped. Computer, IEEE Computer Society, January. 6. Vanderheiden, G. C. (1998). Universal remote console communication protocol (URCC). Proceedings of the 1998 TIDE Conference, Helsinki, Finland: Stakes.

511