The V2 Information Technology Access Interfaces Project is developing
standards for an Alternative Interface Access Protocol (AIAP). This protocol
would complement and build on industry activity in home networking, wireless
networking, and metadata registries for discovery and interoperation of
devices. The aim is to make it easier to fulfill the alternate interface
connection needs of people with disabilities that are called for in recent
government regulations, such as Section 255 of the Telecommunications Act and
Section 508 of the Rehabilitation Act. The Alternative Interface Access
Protocol and related standards will enable IT products to be more
accommodating of the needs and preferences of the consumer by allowing for
alternative user interfaces. While addressing the special needs of people
with disabilities, the option to change interfaces will have a broader market
application. 

Background
Current practice in providing IT accommodation support for people with
disabilities involves tailoring or configuring assistive technology to meet
each individual's needs, abilities, and preferences, and integrating the
result with existing devices in the users' different environments. 
Frequently, assistive technologies need to be developed or adapted to work
with each device in the user's environment. The resulting systems are often
unique within the environment in which they are installed. Consequently,
those using these systems experience difficulties getting technical help, are
frequently ignored or experience inordinate delays when all other systems are
upgraded, and are not as mobile as others in accepting new job assignments
and promotions, or operating in different environments. There is a need for a
standard that simplifies or eliminates the customization required when
assistive technologies are connected to devices, and to provide industry with
a common means of interacting with a wide variety of assistive technologies. 

What is AIAP, technically?
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:

1. By using an alternate user interface component instead of the native user
interface component. 

2. 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").  

3. 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. 

4. By allowing the user to cause new user interface software to be determined
and downloaded onto the target device directly or indirectly. 

http://www.v2access.org/
http://www.ncits.org/tc_home/v2htm/V2docs/v201011.htm