Thread Subject: Re: Proposed Standard Connections Language

Note

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

From: Randy Marsden
Date: Mon, Jun 18 2007 1:51 PM

Tom:

I think you have the interpretation backwards (if I¹m reading your post
right). The intention of the language is this: if an IT product is going
to use a proprietary connector (like a non-standard connector on a mobile
phone), then it could have an adapter that converted that proprietary
connector to something standard (like a USB or mini-USB connector) that AT
could readily connect to.

Of course, this all assumes that there are pins to support a standard port
(like USB) embedded within the proprietary connector. (Most do have USB now
days).

-Randy


------------------------------------------------
Randy Marsden, P.Eng.
President & CEO, Madentec Limited
ATIA Global Policy Chair

780-450-8926 ext. 223
= EMAIL ADDRESS REMOVED =

>
> From: "Tom Brett" < = EMAIL ADDRESS REMOVED = >
> Reply-To: "TEITAC desktop/portable (hardware) subcommittee"
> < = EMAIL ADDRESS REMOVED = >
> Date: Mon, 18 Jun 2007 05:34:44 -0400
> To: "'TEITAC desktop/portable (hardware) subcommittee'"
> < = EMAIL ADDRESS REMOVED = >
> Subject: Re: [teitac-hardware] Proposed Standard Connections Language
>

> The propose the language is:
>
>
>
> ³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 user interface functionality available on
> the non-standard connection(s) would be available on the standard connection.²
>
>
>
> The way I interpret this is that there is 7 pin connector for a new AT device.
> Using an adapter I am able to attach the device to a USB port on the Kiosk or
> PC. The device allows a person to control the cursor movement via facial
> muscle movement.
>
>
>
> Would the platform make provide the driver? If so would the driver need to be
> retrofitted to work with the new device?
>
>
>
> Or?does this say that the AT vendor is prohibited from developing devices that
> exceed the functionality of what is currently available until that AT vendor
> has developed the driver and convinced the platform maker to supply it with
> new operating system releases?
>
>
>
> As a buyer of Government hardware that provide user interface connection
> capabilities would it be permissible to buy a PC that does not have drivers
> for a 7 pin, 3 pin, 25 pin connection?
>
>
>
> Tom Brett
>
>
>
>
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Gregg
> Vanderheiden
> Sent: Sunday, June 17, 2007 10:42 PM
> To: 'TEITAC desktop/portable (hardware) subcommittee'
> Subject: Re: [teitac-hardware] Proposed Standard Connections Language
>
>
>
> Not sure I understand your question. If they provide user interface
> functionality on a non-standard connection, then they need to provide it on
> the standard connection. RE Drivers: they would use the drivers for that
> standard connection.
>
>
>
>
> Gregg
> -- ------------------------------
> Gregg C Vanderheiden Ph.D.
>
>
>>
>>
>>
>>
>> From: = EMAIL ADDRESS REMOVED =
>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Tom Brett
>> Sent: Sunday, June 17, 2007 5:23 PM
>> To: 'TEITAC desktop/portable (hardware) subcommittee'
>> Subject: Re: [teitac-hardware] Proposed Standard Connections Language
>>
>> ³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 user interface functionality available on
>> the non-standard connection(s) would be available on the standard
>> connection.²
>>
>>
>>
>> When it is written: all of the user interface functionality available on the
>> non-standard connection(s) would be available on the standard connection.²
>>
>>
>>
>> Does this mean that the platform makers would need to provide drivers to
>> allow the non standard user interface functionality to be available in the
>> standard connection. How would a platform maker know what drivers are
>> needed?
>>
>>
>>
>> Tom Brett
>>
>>
>>
>>
>> From: = EMAIL ADDRESS REMOVED =
>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Gregg
>> Vanderheiden
>> Sent: Sunday, June 17, 2007 3:08 PM
>> To: 'TEITAC desktop/portable (hardware) subcommittee'
>> Subject: Re: [teitac-hardware] Proposed Standard Connections Language
>>
>>
>>
>> Concur - but we need to clean it up.
>>
>>
>>
>> I think we agreed to put ?user¹ in front of ?interface¹ and ?user
>> interface¹ in front of connections.
>>
>>
>>
>> But I think we missed the "input or output connection capabilities".
>>
>> We do need to address it but "user interface input or output connection
>> capabilities" sounds very awkward and redundant (though it isn't)
>>
>>
>>
>> How about ³user interface connection capabilities².
>>
>>
>>
>> Does that leave anything out?
>>
>>
>>
>>
>>
>>
>> Gregg
>> -- ------------------------------
>> Gregg C Vanderheiden Ph.D.
>>
>>
>>>
>>>
>>>
>>>
>>> From: = EMAIL ADDRESS REMOVED =
>>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Jim Tobias
>>> Sent: Friday, June 15, 2007 6:26 PM
>>> To: 'TEITAC desktop/portable (hardware) subcommittee'
>>> Subject: Re: [teitac-hardware] Proposed Standard Connections Language
>>>
>>> i think we agreed on putting "user interface" in front of "input or output
>>> connection capabilities".
>>>
>>>
>>>
>>> ***
>>> Jim Tobias
>>> Inclusive Technologies
>>> +1.732.441.0831 v/tty
>>> +1.908.907.2387 mobile
>>> skype jimtobias
>>>
>>>
>>>>
>>>>
>>>>
>>>>
>>>> From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ]
>>>> Sent: Friday, June 15, 2007 3:42 PM
>>>> To: = EMAIL ADDRESS REMOVED = ; = EMAIL ADDRESS REMOVED =
>>>> Subject: [teitac-hardware] Proposed Standard Connections Language
>>>>
>>>> In today¹s Hardware subcommittee call, we discussed proposed language for
>>>> Standard Connections. This language was drafted to address the current
>>>> standard ports language.
>>>>
>>>> Proposed language:
>>>>
>>>> Where input or output connection capabilities are provided, whether wired
>>>> or wireless, at least one connection shall comply with publicly available
>>>> industry standards and all of the user interface functionality available on
>>>> the non-standard connection(s) would be available on the standard
>>>> connection.
>>>>
>>>> One element of discussion to which there was some difference in the
>>>> committee had to do with the inclusion of ³or provide an adapter².
>>>>
>>>> Please discuss.
>>>>
>>>> Rob
>>>>
>>>> Rob Nerhood | Experience Design Group | Ergonomics Engineer
>>>> Dell, Inc. | One Dell Way | Round Rock, Texas 78682 - 7000
>>>> direct 512.723.2763
>>>>
>>>> This communication and all attachments are confidential and may be legally
>>>> privileged. If you are not the intended recipient, (i) please do not read
>>>> or disclose any content to others, (ii) please notify the sender by reply
>>>> mail immediately, and (iii) please permanently delete this communication
>>>> from your system. Failure to follow this process may be unlawful and
>>>> subject to prosecution. Thank you for your cooperation.
>
>
>

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