Thread Subject: Thought on sevices

Return to this mailing list's archives

From: Li, Alex
Date: Tue, Feb 20 2007 12:30 PM
Subject: Thought on sevices

Hi all,

Despite the fact that services are covered under 508, I don't think we need to do anything special because of the following:

Service has to be something either between "machine" and human OR human and human. "Machine" to "machine" services do not need accessibility features.

All "machine" to human interactions must already be covered by some combination of software and hardware. We have this one covered.

Direct human to human interactions, such as medical services or fire rescue, cannot be E&IT. Thus, we should not cover such services in 508 & 255.

Long distance or remote human to human interactions, by definition, require E&IT. Thus, some sort of software and hardware must be involved. Texhnically speaking, long distance or remote services are "machine" to human services. We are covered.

The only thing I can think of that falls outside of the above calculation would be printed material. I don't know if the government is obligated to provide electronic version of all printed material. § 1194.1 suggest that there is an obligation to provide accessible version of all information and data. If the accessible alternative of printed material takes the form of electronic material, it will again be covered.

My conclusion: everything looks watertight and that services are covered, by default, from using products that meet the hardware and software requirements.

All best,

Alex Li
Manager, Accessibility Standards and Policies
SAP Labs, Inc.
3410 Hillview Ave
Palo Alto, CA 94304
T (650) 687-4770
F (610) 492-2961
M (202) 492-4592
mailto: = EMAIL ADDRESS REMOVED =
http://www.sap.com <http://www.sap.com/>
THE BEST-RUN BUSINESSES RUN SAP
This e-mail is confidential and may contain privileged information. If you are not the addressee it may be unlawful for you to read, copy, distribute, disclose or otherwise use the information in this e-mail. If you are not the intended recipient please notify us immediately.

From: Yamada@TOYO-UNIV
Date: Wed, Feb 21 2007 4:40 AM
Subject: Re: 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

From: David Poehlman
Date: Wed, Feb 21 2007 5:15 AM
Subject: Re: Thought on sevices

While I agree in principle with this, the second case is already
covered in software provisions where it is mandated that any controls
needed for operation are accessible meeting standards inn other
words. 255 includes service in a slightly different way since
telecommunications services are a slightly different model which can
dictate accessibility or not depending on how they handle their
activities and what they allow or do not allow to happen. For
instance, let's say that service a enjoys the richness of all that
can be done via the phone. Let's say that service b only allows
basic activities. Let's further say that service b will not allow
through its policies and practices of infrastructure development the
connection of a call from service a through to service b. Here we
have a classic example of service accessibility deterrence since for
instance, if I live in the area of service b and My daughter lives in
the area, even though she has and can use a tt device, she cannot
place tt calls to me either through directly or via relay because I
cannot receive them through my service.

I also think that service is a general term which could easily be
miss enterpretted.

Thanks!

On Feb 21, 2007, at 6:34 AM, Yamada@TOYO-UNIV wrote:

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

From: Truesdell Nick
Date: Wed, Feb 21 2007 6:55 AM
Subject: Re: 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
= EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >

From: terry.weaver@gsa.gov
Date: Wed, Feb 21 2007 9:35 AM
Subject: Re: Thought on sevices

We have been including services under Section 508 in regards to Federal
procurements since the majority of procurements are actually more than the
simple acquisition of an E&IT item.

The Buy Accessible Wizard walks government buyers through the steps to
define what it is that they are requiring and how Section 508 applies
since many people don't realize that there is actually E&IT-related
deliverables in the contract they are looking to award.

Let me offer a quick example. An agency's human resources (HR) office
issues a request for proposal (RFP) that seeks the services of a company
to help devise new employee satisfaction goals for the agency in regards
to the physical workplace or policies or hiring practices or work
schedules or whatever. The agency first wants the company to establish a
baseline on how employees feel about these issues before the company can
propose new solutions by surveying the employees. The survey, to be
conducted via the agency's intranet, is a service that has Section 508
considerations - it must meet the Standards regarding the web. If the
products delivered by the company will be posted on-line, they too must
meet Section 508 Standards.

The Wizard can help identify these different deliverables and the related
Section 508 requirement. I have cut and pasted information from the
Wizard below:



E&IT-related Service
A contracted service that may produce a deliverable which is or relates to
Electronic and Information Technology. Types of services related to E&IT
include:
General Information Services- expertise, consultation, research or other
knowledge-based services that deliver information content in many
different forms
E&IT Development Services- generally the design and development of custom
E&IT product deliverables. This includes the development of custom
software, web-enabled applications and customized websites, as well as
development of custom E&IT hardware components, telecommunications
equipment, including associated information, documentation and support.
Also includes specific enhancements to existing E&IT hardware / software.
E&IT Integration Services - composing various E&IT components into a
custom E&IT system deliverable
E&IT Operations and Maintenance Services- providing management, operations
and support of ongoing E&IT functions, including the delivery of E&IT
functionality for end users, system performance, maintenance, monitoring
and management of E&IT-related activities. Developing new E&IT is beyond
the scope of typical Operations and Maintenance Services.
E&IT Testing / Validation Services- delivering quality assurance and
remediation for existing E&IT.
Training Services- develop or provide training.
On-Site Support Services- providing on-site management, operations and
support of ongoing and new E&IT functions including design, development,
and delivery of E&IT functionality for end users, E&IT system performance
assurance, maintenance, monitoring and management of E&IT-related
activities.
The basic types of E&IT-related Service deliverables are identified.

E&IT-related Service Deliverable
Information Content Deliverable- Delivering information content in many
different formats, including delivered documents, reports, videos, and
multimedia productions.
Custom E&IT Product- Delivery of E&IT product functionality developed to
specification, including design and development of integrated E&IT systems
or solutions.
E&IT Task Performance Deliverable - Delivering task performance on
specified E&IT-related activities, including operation, maintenance and /
or support of ongoing E&IT activities.

E&IT Task Performance Deliverable
Delivering tasks performance on specified E&IT-related activities,
including operation, maintenance and / or support of ongoing E&IT
activities.

From: David Poehlman
Date: Wed, Feb 21 2007 10:00 AM
Subject: Re: Thought on sevices

True, As I understood it though, the question was about standards.

From: Gregg Vanderheiden
Date: Fri, Feb 23 2007 11:30 AM
Subject: Re: Thought on sevices

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