National Committee for Information Technology Standards Information Technology Access Interfaces Technical Committee (NCITS V2) ANNUAL REPORT
As of this report, NCITS V2 has 17 member organizations of record; has held 5 Plenary meetings and 20 informal working meetings. The committee has a preliminary draft specification for the Alternative Interface Access Protocol (AIAP). Several organizations are currently developing or are looking at developing reference implementations of the protocol.2. Projects
a. Project Number and Title:
1464 - D; Alternative Interface Access Protocol (AIAP).
b. Original, previous and current target date for initial public review
(Milestone 4) reflected in month and year.Original target date: March, 2002
Previous target date: N/A
Current target date: March, 2002
c. Project Description:
The protocol will provide for access to both standalone and networked systems and devices. With suitable intermediaries, AIAP will permit interaction with workstations, with embedded devices (environmental controls, intelligent appliances, and consumer electronics), or with applications via home networking and/or the Internet. The protocol optionally will convey information about user interface functionality, preferences, and capabilities to another system with which the user intends to interact. Alternative interfaces can then be accommodated or constructed, in real-time if necessary, to provide fundamental access to computing services and information regardless of any limitation of the user.There are 4 ways that AIAP is currently envisioned to provide a means for users to change the user interface:
- By using an alternate user interface component instead of the native user interface component.
- By allowing a person to use a complete alternate user interface (which includes its own alternate input, control and display mechanisms) instead of the native input, control and display mechanisms on the product (a "Remote Console").
- By allowing the user to cause their characteristics or user interface preferences to be communicated to the target product (either directly or by providing a code which the device uses to look up the user preference or characteristics) where the target product changes its own user interface behavior based on the user preferences or needs.
- By allowing the user to cause new user interface software to be determined and downloaded onto the target device directly or indirectly.
d. Publications During Past Year:
"Auxiliary Interface Access Protocols (AIAP) for Assistive Technology: Controlling Next Generation Technologies from Assistive Technologies," June, 2001 Presentation to the Assistive Technologies Industry Association Annual Meeting by Gregg Vanderheiden
e. Statement of Progress and Current Status:
The V2 has decided to divide the AIAP four approaches, each of which will have a detailed specification. We are currently concentrating on the Remote Console varient (described under bullet 2 from the project description, 2.c., above, AIAP-RC). We have a working draft of the AIAP-RC specification being used to support the reference implementations.Two participating organizations have initial reference implementations. Two other organizations have indicated interest in developing such implementations. These implementations use different technologies and are used to ensure that the specifications are implementable and generic.
a. Previous Year's Meetings:
- October 11 - 13, 2000; Washington, DC
- December 7 - 8, 2000; Gaithersburg, MD
- February 7 - 8, 2001; Gaithersburg, MD
- May 7 - 8 & 11, 2001; Washington, DC
- July 30 - 31, 2001; Madison, WI
b. Next Year's Planned Meetings:
6. November 27 - 28, 2001; Redmond, WA
7. March 3 - 5, 2002; Nashville, TN
8. June ? - ?; St. Petersburg, FL
9. August ? - ?; Washington, DC
AFB
Principal
Janina Sajka
American Foundation for the Blind
Governmental Relations Group
820 First Street, N.E., Suite 400
Washington, DC 20002
janina@afb.net
voice: (202) 408-8175AT&T
Principal
Mike Burks
5212 Covington Bend Dr.
Raleigh, NC 27615
mburks952@att.net
voice: (919) 870-8788AT&T
Alternate
Chris Smith
Director Special Programs
Enterprise Systems
GRCI 1900 Gallows Rd.
Vienna, Va. 22182
smith@grci.com
voice: (703) 506-5172; mobile: (703)626-3908Compaq Computer Corp.
Principal
Rex Lint
Program Manager
Industry Standards and Consortia Group
110 Spit Brook Road
Nashua, NH 03062
ATTN: ZKO2-2/K27
rex.lint@compaq.com
VOICE: (603) 884-3759; FAX: (603) 884-0120Dept. of Commerce
Principal
Sharon Laskowski
NIST, 100 Bureau Dr., MS 8940
Bldg. 225, Rm A216
Gaithersburg, MD 20899-8940
sharon.laskowski@nist.gov
voice: (301) 975-4535Dept of Commerce/ Census
Alternate
Bill LaPlant
Census, Rm 3000-4
Washington DC 20233-9150
bill.laplant@census.gov; blaplant@mindspring.com
voice: (301) 457-4887ERIM
Principal
James Kindrick
3600 Green Ct. Suite 550
Ann Arbor, MI 48105
jkindrick@erim.org
voice: (734) 623-6514; fax: (734) 623-2501GSA
Principal
Karl Hebenstreit, jr.
1800 F Street, NW, Rm. 5240
Washington, DC 20405
karl.hebenstreit@gsa.gov
voice: (202) 275-0540GSA
Alternate
Susan Turnbull
18 & F Sts., NW.
Washington DC 20405
susan.turnbull@gsa.gov
voice: (202) 501-6214IBM
Principal
Shari Trewin
30 Saw Mill River Road
Hawthorne, NY 10532
trewin@us.ibm.com
voice: (914) 784-7616IBM
Alternate
Peter Fairweather
IBM, T.J. Watson Research Center, Route 134
Yorktown Heights, NY 10532
pfairwea@us.ibm.com
voice: (914) 945-2138MICROSOFT
Principal
Nasser Ghazi
1 Microsoft Way
Redmond, WA 98052
nasserg@microsoft.com
voice; (425) 705-4406MICROSOFT
Alternate
Masahiko Kaneko
1 Microsoft Way, 21/2033
Redmond, WA 98052
mkaneko@microsoft.com
voice: (425) 703-7539National Industries for the Blind
Principal
Joe Roeder
1901 N. Beauregard St., Suite 200
Alexandria, VA 22311
jroeder@nib.org
voice: (703) 578-6524ORACLE
Principal
Connie Myers
500 Oracle Parkway
Redmond Shores, CA 94065
connie.myers@oracle.com
voice: (650) 506-4171PSINET, Inc.
Principal
Mark D. Urban
7105 Sandringham Dr.
Raleigh, NC 27613
mark.urban@psinetcs.com
Voice: (919) 395-8513; toll free: (800) 547-5602; fax: (919) 783-6852PSINET, Inc.
Alternate
Cynthia Waddell
Metamor
Accessibility Center of Excellence
PO BOX 5456
San Jose, CA 95150-5456
Cynthia.Waddell@PSINetCS.com
voice: (800)547-5602; fax: (919)783-6852RERC on Communication Enhancement
Principal
Kevin Caves
Director
Clinical Associate, Department of Surgery
Duke University Medical Center
DUMC 3887
Durham, NC 27710
kevin.caves@duke.edu
voice: (919) 684-3540; fax: (919) 681-9984SHARE INC
Principal
John A. Chapman
844 S. Madison Street
Hinsdale, IL 60521-4363
Jchapman@Share.org
voice: (630) 325-3081; fax: (630) 325-3081SHARE INC
Alternate
Dave Thewlis
2301 C Street
Eureka CA 95501-4108
dthewlis@dcta.com
voice: (707) 442-0547; fax: (707) 442-9342 faxTHE MITRE CORPORATION
Principal
Margot Peet
1820 Dolley Madison Blvd., MS W622
MCLEAN, VA 22102
mpeet@mitre.org
voice: (703) 883-7596; fax: (703) 883-6708THE MITRE CORPORATION
Alternate
James W. Moore
1820 Dolley Madison Blvd., W534
McLean, VA 22102
James.w.moore@ieee.org
voice: (703) 883-7396; fax: (703) 883-5432TRACE CTR UNIV OF WISC
PRINCIPAL
Gregg Vanderheiden
5901 Research Park Blvd.
Madison, WI 53719
GV@trace.wisc.edu
voice: (608) 263-5788; fax: (608) 262-8848; cell: (608) 213-7770TRACE CTR UNIV OF WISC
ALTERNATE
Gottfried Zimmermann
5901 Research Park Blvd.
Madison, WI 53719
Zimmer@trace.wisc.edu
voice: (608) 265-2720Unisys Corporation
Principal
Joy Relton
12010 Sunrise Valley Dr.
Reston, VA
joy.relton@unisys.com
voice: (703) 620-7145fax: (703) 620-1404Unisys Corporation
Alternate
Arnold F. Winkler
Unisys B203-14
2476 Swedesford Road
Malvern, PA 19355
Arnold.winkler@unisys.com
voice: (610) 648-2055; fax: (610) 695-5473XEROX
Principal
Michele Cahn
1401 H St., NW
Suite 200
Washington, DC 20005
mailto:Michele.L.Cahn@usa.xerox.com
voice: (202) 414-1288; fax: (202) 414-1217XEROX
Alternate
Kathleen O'Reilly
1401 H St., #200, NW
Suite 200
Washington, DC 20005
mailto:Kathleen.M.OReilly@usa.xerox.com
voice: (202) 414-1295; fax: (202) 414-1217LIAISON MEMBERS (1)
IEEE/ STANDARD 2001
Earl Meiers
5301 Glen Green Court
Alexandria, VA 22315
mailto:skip@ieee.org
voice: (703) 808-3005; fax: (703) 808-3474
e. Liaison Activities:
- IEEE Web Engineering Best Practices Guideline (P2001). Based on common interest in accessibility of data and information. The IEEE WEBPG Committee has agreed to work jointly on Web accessibility needs and preferences issues and vocabulary. We have established a formal liason with this committee.
- W3C/WIA. Common interest in needs and preferences based selection of services or rendering. Maintain continuing exchange of information through overlapping membership.
- The Accessibility Forum. Common interest in AT / E & IT iteroperability. Maintain continuing exchange of information through overlapping membership.
- UPnP Consortium. Common interest in selection of services or features. Maintain continuing exchange of information through overlapping membership.
f. Administrative Matters of Note:
We would like to thank the Secretariat staff for their outstanding support of our working Web site.
g. Procedural Matters of Note:
none.
h. Recommendations (optional):
i. Market Impact
There is a burgeoning market already for personalization of content and appearance on the World Wide Web, with regard to small handheld devices and for commercial sales purposes. Companies such as IBM, ATG and Vignette, among many others, have products and services for this explicit purpose. This market is expected to grow considerably in the next 2 to 3 years. There is also a movement in the Web to provide sites of interest to people with disabilities (e.g., HalfthePlanet, WeMedia, CanDo) and the aging population (e.g., SeniorNet), and attempts to bring the W3C WAI recommendations into these. Alternative interfaces to meet these needs, whether pre-constructed, adapted or constructed on the fly, are a form of personalization.Another rapidly emerging segment of technology is that of pervasive computing, whereby intelligent devices of all sorts are distributed into the living environments of home, shopping, and other activities involving mobile systems. Of particular note are the numerous offerings in:
This follows the burgeoning of wireless technology from companies such as Qualcomm, Nokia, Ericsson, and Motorola, to mention but a few, as well as activities such as the Wireless Application Protocol Forum (WAPForum) and the Salutation Consortium in promoting applications for wireless devices. Handheld devices such as the 3Com Palm and the Pocket PC are targeted at the mobile computing environment. Another important factor in the wireless environment is the Bluetooth RF infrastructure for which a very substantial number of manufacturers are building compatible devices.
- Unified messaging/mobile computing (eFax, Hotmail), providing a central information net-access point for one's messaging needs;
- Net-based information stores for people's core documents/pictures (Freespace, Apple iTools);
- Transcoding/reformatting services for various devices (Everypath, YahooMobile, IBM);
- Home automation & multi-access point management (Sony, Echelon, Microsoft, IBM);
- Personalization of content & related marketing data (Vignette, NetPerceptions).
Whereas these services look towards increasing access for user's critical information, they rely on end-users to configure, change, or maintain configurations for their access. In addition, the burden of incorporating multiples of these offerings into a daily regimen is taxing on the user, and certainly highly error-prone. The key shortfall, however, rests in the personalization of the user's interaction with each of these separate systems, and the changes and dynamics that individual users' will need to effectively coordinate and use these services effectively. This can be made especially difficult for a user with a disability or who is aging.
To make these systems truly usable, service providers must bridge the user's networks (office, mobile, home); the user's devices (phone, web-pad, computer); and the user's information spaces (email, documents, news/information).
Key to interaction across devices and information spaces is the ability toprovide the solution in a ubiquitous form factor. Two related initiatives are needed:
The AIAP is seen as the integrating factor for these initiatives. Moreover, the AIAP will be a major factor in providing preference and capability transfer in non-networked, non-mobile uses as well. The Composite Capabilities and Preferences Profiles (CC/PP) effort in W3C is aimed at standard representation of the capabilities and preferences for users and devices. The WAPForum has been using the CC/PP to describe the features and capabilities of some wireless devices such as smartphones.
- Spreading the user preference initiators throughout devices and information systems via involvement by system-on-a-chip manufacturers, device manufacturers, and mobile code technology.
- Appending additional services onto application servers or platforms to provide a richer, personalized user experience.
There are at least two organizations, Trace R & D Center and Microsoft, Inc., that are already building systems based around the draft documents that the NCITS ITA SG and V2 have produced so far. They expect to have public demonstration of their implementations in the summer of 2002.
Moreover, there is an abundant market for third-party developers to build products that will carry out interface transformations for content, appearance and user controls and to build applications that lend themselves to interface selection or transformation. Many of these already exist. Netscape has released its Versions 6 browser which permits widespread modification of both its operating interface and the content appearing on it, through a language called XUL (extensible User interface Language). There is also another language called User Interface Markup Language that uses Sun Microsystemsâ Java Swing for modifying rendering of interface elements. Both of these languages are compatible with and expressible by the W3C language XML. Sun is also pushing its Jini connection technology as a means of mediating access to alternative interfaces (the AIAP would run over Jini). Other venues for the AIAP include the Salutation Consortiumâs Salutation architecture, HomeAPI/Universal Plug and Play, and HomeRF.
The AIAP is also being seen as part of the solution for meeting the Access Board procurement standards for electronic and information technology, pursuant to the provisions of Section 508 of the 1998 amendments to the1973 Rehabilitation Act. Thus, some equipment procured by the Government could have the AIAP specified as meeting some of the requirements of the 508 procurement standards.
Numbers from analysts range up to 1 billion wireless devices shipped by 2004; 10 million digital homes by 2004; and 41 million telecommuting/ SOHO workers by 2003. The total addressable market of an enabling technology such as interaction personalization can be estimated at 100 million people in North America & Europe within 3 years. Related investments in wireless data, personalization, and unified services are in the multi-billion dollar area. There are 70 million adults aged 50+; this is expected to grow to 115 million in the next 25 years. Of the present 70 million, 13 million have Internet access (SeniorNet and Charles Schwab), or 16.5% of total online population, and they spend 30 hours per month online, 47% higher than the national average. A significant portion of these users has difficulty in using a mouse and navigating the Web, and operating other applications. About 8% of the total U. S. population has a disability that limits their ability to use a computer or to have effective access to the Internet. People with disabilities are under-represented in the work force and make up a considerable portion of the population that is at low-income levels.
Metadata - This project will establish the data elements needed to support data registries for Assistive Technology Services and for User Needs and Preferences Specification. We intend to make use of ISO/IEC 11179, the data registries standard maintained and being developed by NCITS L8. AT / E & IT Application Program Interface - The Accessibility Forum is in the preliminary stages of developing requirements for AT / IT Interoperability. If their requirements include an API, they may seek NCITS V2 assistance in its development.
V2 - Information Technology Access Interfaces
(Revised 10/05/01 )
Title: Alternative Interface Access Protocol (AIAP)
None at this time.
None at this time.