Note

This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional and up-to-date details on the updates to section 508 and section 255 can be found at the Access Board web site.

HW Draft Standard Connections Language

Link back to Hardware Draft Language EWG Format


2.1.C Standard Connection

2.1.C "Where user interface connection capabilities are provided, whether wired or wireless, at least one connection shall comply with publicly available industry standards and all of the product functionality that is controllable by the user through the non-standard connection(s) shall be controllable by the user via the standard connection using industry standard protocols for that type of input or output."

Discussion or Rationale

There has been a large degree of conversation regarding this provision. The original language was from the Desktops and Portable section. In this revision, it has been applied across all projects. Attempts were made to create language that did not stifle innovation and allowed for proprietary connections. Care needs to be taken in any "guidelines" to ensure that the intent of this provision, to provided a means of connection is clear.

A second debate regarding who is responsible for "adapters" was not resolved.

There has been discussion on the listserv relative to how this language addresses the responsibility of driver development, especially with KIOSK (closed) system interaction.

The context of the language relative to Hardware is that it is to ensure that the "the connection" can be made from the "physical" perspective.


One interpretation from the listserv of the language is:

  • IF a company provides I/O functionality on a proprietary connector
  • THEN it must provide same functionality on a std connector.
  • This provision does not require that any AT drivers be provided.
  • It doesn't require that any standard connector be provided. ( a wireless connection would suffice if standard)
  • It doesn't require that any standard connection be provided UNLESS there are I/O functions on a proprietary connector.
  • IF there is an I/O function on a proprietary connection, it DOES require a driver that provides I/O function on the standard connection.


  • Source: {508} 1194.26(d)
  • Subcommittee: Hardware
  • Impact:
  • External Reference:
  • Testability
  • Metadata
    • Disabilities: All disabilities
    • User Activities: Conversations, data analysis, document sharing and reviewing, media (audio/video) creation and editing.
    • Product Characterisics: Physical controls or connectors, touchscreen or touch sensitive buttons.
    • Product Types: Hardware, telephone, telephone system, audiovisual equipment, public information terminal, desktop computer system, portable computer system, copier, printer, scanner, other simliar peripheral

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University