Thread Subject: Re: Thought on sevices

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: Gregg Vanderheiden
Date: Fri, Feb 23 2007 11:30 AM

Good comment.



We should take all areas of E&IT, all products, all deliverables and think
about what is needed to make them accessible. Then see if there is anything
missing from the general list we already have. If there is, it is a
candidate new item. If not, the product would just be a column with
checkboxes for each of the provisions that cover it.




Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.






_____


From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Truesdell Nick
Sent: Wednesday, February 21, 2007 7:49 AM
To: TEITAC General Interface Accessibility Subcommittee
Subject: Re: [teitac-general] Thought on sevices

As I noted on the conference call yesterday a great majority of services
actually have embedded EIT deliverables. Currently all of these deliverables
would be required to conform to the respective provisions. In some case this
is obvious. (such as where the service is for software or web development).
In other cases it is not as immediately clear. Referencing the example of a
service for use of CPU clock cycles, the actual processing time itself may
not have any 508 implications but perhaps the service comes with a web
interface where a user would upload a binary job to be processed.



Before breaking out a separate category for services I think care should be
taken to ensure that the items we are looking to address are not already
covered elsewhere.



Nick Truesdell
Information Technology Accessibility Center - ITAC
Information Resources Accessibility Program - IRAP
Desk: 202-283-5536
<mailto: = EMAIL ADDRESS REMOVED = > = EMAIL ADDRESS REMOVED =






_____


From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
Yamada@TOYO-UNIV
Sent: Wednesday, February 21, 2007 6:35 AM
To: 'TEITAC General Interface Accessibility Subcommittee'
Subject: Re: [teitac-general] Thought on sevices

Dear all, dear Alex,



Yesterday I raised a question at the conference call whether we need a
category of "service" in the product list
(http://trace.wisc.edu/semipub/filter/ByProductType.html) or not.



I have several reasons to include "service" in the list.



First of all, 508 Technical Specifications already included "service." See
the definition in 1194.4.

Information technology. Any equipment or interconnected system or subsystem
of equipment, that is used in the automatic acquisition, storage,
manipulation, management, movement, control, display, switching,
interchange, transmission, or reception of data or information. The term
information technology includes computers, ancillary equipment, software,
firmware and similar procedures, services (including support services), and
related resources.



Second, In Section 255 of 1996 telecommunications act, we can find terms
such as "telecommunications service," "satellite service," "cable service,"
and others, in addition to "telecommunications relay services."

Even if we realize accessibility at the interface between human-being and
telecommunications terminal, if a telecom operator providing a
telecommunications service blocks the accessibility-related information flow
through its network, users cannot enjoy the telecommunications service. This
is the reason that Section 255 includes a lot of terms of "service."



Third reason. A service is realized by integration of components (hardware
and software.) Therefore, it is enough to determine accessibility
requirements of software and hardware to develop a service. I agree
conditionally with these basic thoughts because I think accessibility of
service depends on not only accessibility of components but also the design
on the service.

Let us consider the following cases both of which provides sound and verbal
information:in the course of performing its service. (Case 1) Sound level
can be increased by turning the (physical) volume in headset. (Case 2) Sound
level can be increased by turning the on-screen volume. Do you think which
one is more accessible?

It is therefore necessary to consider "accessibility of service" when an
agency procures the service.



I look for your comments.



Hajime Yamada

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