[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Systems integration support database requirement designed into 508 standards.
I recently sent a message asking that any reader interested in:
"discussing the advantages/disadvantages of including a requirement to
create and maintain an "assistive technology systems integration support
database" as a 508 standard."
PLEASE write to me... or post your thoughts. My original post is attached
below, FYI.
One last note. Anyone sending me an e-mail message with the words, "508
Systems Integration Support Resource Discussion" in the subject field will
automatically receive an e-mail mesage with comments received on the
integration issue thus far.
Your support and involvement is appreciated.
Sincerely,
Steve Jacobs
Enabling Advocacy Link (IDEAL) at NCR
NCR Corporation
1529 Brown St. EMD-5
Dayton, Ohio 45479
(937)445-6396 Voice
(937)445-2468 Fax
(800)855-2880 TTY
steve.jacobs@daytonoh.ncr.com
www.ncr.com
> -----Original Message-----
> From: Jacobs, Steve I
> Sent: Tuesday, October 20, 1998 8:24 AM
> To: 'eitaac@trace.wisc.edu'
> Subject: Contribution to the develpment and maintainence of a Systems
> Integration Support resource should be designed into 508 standards.
>
> Private industry is able to develop, procure, maintain (support) and use
> electronic and information technology and, at the same time, ensure that
> it's customers are able to successfully access and use the intended
> information and data is by creating support knowledge bases which are
> accessible to the consumer, customer, systems integrator, software
> developer and all support people. Microsoft (R) TechNet is but one
> example of this.
>
> Ensuring that electronic and information technology, purchased by the
> federal government is accessible to and usable by individuals with
> disabilities is no different.
>
> Let's move one step closer to a developing a set of 508 standards that
> foster success by creating a subcommittee focused on defining how best to
> include systems integration support into our standards. I will volunteer
> time to chair this subcommittee.... but only if there is support for this
> idea.
>
> If you are not a member of our EITAAC and wish to express an opinion on
> the benefits (or lack thereof) of including standards in support of
> developing and maintaining a Federal Systems Integration Support Resource
> as part of our 508 standards you can send your comments directly to me. I
> will then include them ALL in an e-mail message that can be retrieved by
> anyone sending me an e-mail message with the words, "508 Systems
> Integration Support Resource Discussion" in the subject field. I will, on
> occasion, post the full contents of the cumulative "e-mail" to our EITAAC
> listserve. Thank you for your interest in supporting our EITAAC.
>
>
> Sincerely,
>
>
> Steve Jacobs
> Enabling Advocacy Link (IDEAL) at NCR
> NCR Corporation
> 1529 Brown St. EMD-5
> Dayton, Ohio 45479
>
> (937)445-6396 Voice
> (937)445-2468 Fax
> (800)855-2880 TTY
> steve.jacobs@daytonoh.ncr.com
> www.ncr.com
>
>
> -----Original Message-----
> From: Gregg Vanderheiden [SMTP:po@trace.wisc.edu]
> Sent: Monday, October 19, 1998 8:29 PM
> To: Multiple recipients of list
> Subject: looking forward
>
>
> Steve Berger wrote
>
> >The reason I think this information will be important is that we
> should
> want
> >to assure that our work gives a lot of attention to the most
> commonly
> >purchased types of equipment.
>
>
> GV:
> While I agree with this, we need to be careful to also look forward
> and be
> sure that we address the next, and next next generation
> technologies, since
> these guidelines/rules will be around a lot longer than the
> increasingly
> short lived technologies we are using today.
>
>
> I also believe that we should look carefully at the systems
> integrator. It
> is a purchased service and may be the most critical component for
> ensuring
> access of the packages or systems as they are experienced by the
> federal
> employee.
>
> Gregg