RFI

Document Sample
RFI Powered By Docstoc
					    The Regents of the University of California

              REQUEST FOR INFORMATION
                # UCOP-WATT-RFI 2007

                                   FOR

          Web Accessibility Testing Tools
                 Date Issued: November 26th, 2007

           Due Date for Responses: January 11th, 2008




        Issued By:           The Regents of the University of California

        RFI Administrator: Brian N. Agius
                           Contract Administrator
                           University of California, Office of the President
                           1111 Franklin St., 10th Floor
                           Oakland, CA 94607




1
     RFI #UCOP-WATT-RFI 2007                                                      Web Accessibility Testing Tools




                                         Table of Contents


I.    Overview ............................................................................................................ 4

II. Instructions to Respondents .................................................................................... 5

III. Response Signature Page ..................................................................................... 8

IV. About the University of California........................................................................... 9

V. Anticipated Minimum Requirements ..................................................................... 10

VI. RFI Response Section ......................................................................................... 12




                                                             2
        RFI #UCOP-WATT-RFI 2007                                           Web Accessibility Testing
                                                                                              Tools


I. Overview


A. Purpose of the Request for Information

The purpose of the Request for Information (the ―RFI‖) is to identify and select qualified suppliers
of automated tools for testing and retrofitting Web sites for accessibility.

B. Objectives of Sourcing Initiative

The overall objective of this RFI process is to select suppliers to assist the University of California
in building, deploying, testing, and maintaining accessible Web sites. The University seeks
information about (1) desktop testing tools, which can be used by the individual Web
developer/designer for a single page or local site, and (2) enterprise testing tools, which can be
used for centralized testing of entire Web domains.


C. Participating University of California Locations

         The campuses – UC Berkeley (UCB), UC Davis (UCD), UC Irvine (UCI), UC Los Angeles
          (UCLA), UC Merced (UCM), UC Riverside (UCR), UC San Diego (UCSD), UC San
          Francisco (UCSF), UC Santa Barbara (UCSB), and UC Santa Cruz (UCSC)
         Five medical centers – UCD Medical Center located in Sacramento, UCI Medical Center,
          UCLA Medical Center, UCSD Medical Center and the UCSF Medical Center
         The remote offices associated with each campus including the UC teaching and
          administrative offices located in Sacramento, CA; Washington, D.C.; and the agricultural
          field stations throughout California.
         The Office of the President located in Oakland, CA


This RFI will serve to inform and educate the University-wide team regarding a possible future
Request for Proposal (RFP). In any such RFP, the University anticipates soliciting bids and then
selecting one or multiple suppliers to provide web accessibility tools to the University, although it
reserves the right to select none at all or to add suppliers at a later date. Until a Web Accessibility
RFP is issued, if it is issued, the University will not project a time line for RFP or any resulting
contract.




THE REMAINDER OF THIS PAGE IS INTENTIONALLY LEFT BLANK.




4
        RFI #UCOP-WATT-RFI 2007                                             Web Accessibility Testing
                                                                                                Tools

II. Instructions to Respondents


A. Issuing Office and University Contact Information
This RFI is issued for the Regents of the University of California by the UCOP Strategic Sourcing
Department which shall be the University’s sole point of contact with respondents for matters
regarding the RFI. The UCOP Strategic Sourcing Department is the only office authorized to
change, modify, or clarify the specifications, terms, and conditions set forth in this RFI and to
issue any follow-on RFP and award any contract(s) which may later result from any RFP. All
communications concerning this RFI should be addressed in writing to the following University
Contact:

               Brian N. Agius
               Contract Administrator
               University of California, Office of the President
                                     th
               1111 Franklin St., 10 Floor
               Oakland, CA 94607

                PH: (510) 987-0271
                Email: brian.agius@ucop.edu

B. RFI Schedule
Resellers interested in submitting responses in response to this RFI should do so according to
the following schedule. The University reserves the right to modify this schedule as its best
interests may appear.

                              EVENT                                 TIME              DATE
                                                                    (PST)
    RFI release date                                                                11/26/2007
    Last day for respondents to submit questions                   4:00 pm          12/5/2007

    Deadline for submission of Information                         4:00 pm          1/11/2008




C. How to Submit Questions Regarding the RFI
It is mandatory that all inquiries and requests for clarification regarding this RFI be addressed in
writing to the University Contact. A list of all questions received by the University (without
identifying the source of the question) and the corresponding University responses will be
distributed by email to all known respondents. The question and answer (Q & A) listing will also
be posted on the UCOP webpage at http://www.ucop.edu/purchserv/rfp/welcome.html. All
inquiries should include:
         Company name, address, and phone number
         A clear and concise question
         Reference to specific section or requirement within the RFI.

Questions are due by the date specified in the RFI schedule above by e-mail (preferred) or fax.
Reference to the RFI number should appear on all correspondence.
D. Amendments to the RFI
The University may issue revisions or addenda to the RFI at any time prior to the deadline for
submitting responses, and, at its own discretion, may extend the submission deadline. Any



5
     RFI #UCOP-WATT-RFI 2007                                           Web Accessibility Testing
                                                                                           Tools

changes to the RFI will be in the form of written amendment issued by the UCOP Strategic
Sourcing Department. Any such amendments will be sent by email to all known respondents.
Amendments           will      also         be        posted      on       the       website      at
http://www.ucop.edu/purchserv/rfp/welcome.html. Amendments will be clearly marked as such.
Each amendment will be numbered consecutively and will become part of this RFI. Respondents
are advised to refer to the website periodically to check for posted amendments. The University
shall not be responsible for failure of any respondent to receive all publicly posted documentation
related to this RFI. Except as stated in this paragraph, no one is authorized to amend any part of
this RFI, in any respect, either in writing or by oral statement.
E. Instructions for Submitting Responses
One (1) signed original and one electronic copy in Microsoft Word® format of the response must
be received by the UCOP Strategic Sourcing Department no later than the response submission
deadline specified in the RFI Schedule shown above. The electronic copy may be submitted as
CD-ROM or other widely accepted media. The contact for all submissions is below:

              Brian N. Agius
              Contract Administrator
              University of California, Office of the President
                                    th
              1111 Franklin St., 10 Floor
              Oakland, CA 94607

              PH: (510) 987-0271
              Email: brian.agius@ucop.edu


Responses must be sealed and marked with the RFI number. Responses sent via facsimile
(FAX) will not be accepted.
F. Simplicity of Preparation
Responses should be prepared simply and economically, providing a straightforward, concise
description of the reseller’s capability to satisfy the requirements of the RFI. Special bindings,
color displays, promotional materials etc. are not desired.
G. Errors and Omissions
If the responder discovers any discrepancy, ambiguity, error, or omission in this RFI or any
related documents, the responder should notify the University immediately and request
clarification or correction. Any such errors or omissions, if verified by the University, will be
corrected by written addendum to the RFI.
H. Preparation Costs
All costs incurred in the preparation and submission of responses and related documentation,
including will be borne by the Respondent.
I. Clarifications
The University may, at its sole discretion, seek clarification from any Respondent regarding
submitted information and may do so without notification to any other Respondent.
J. Disclosure of Records
All responses, supporting materials, and related documentation will become the property of
University.

All information submitted must be open to public inspection (except items clearly marked as
―trade secrets‖ and considered trade secrets under the California Public Records Act). Should a
request be made of the University for information that has been designated as confidential by the



6
     RFI #UCOP-WATT-RFI 2007                                          Web Accessibility Testing
                                                                                          Tools

respondent, and on the basis of that designation, the University will deny the request for
information; the respondent shall be responsible for all legal costs necessary to defend such
action if the denial is challenged in a court of law.
K. Conflict of Interest
By submitting a response to this RFI, the respondent certifies that no officer or employee of the
University who may be in a position to review the submission has any financial interest, direct or
indirect, in the responding firm. Any question, which may arise during the performance of this
agreement regarding a possible conflict of interest, shall be referred to the University for
adjudication.

L. Marketing References
Making any reference to the University in any literature, promotional material, brochures, or sales
presentations without the express written consent of a University officer with the appropriate
delegated authority in accordance with University of California policy regarding the use of the
University’s Names, Seals, and Trademarks is strictly prohibited.
M. Ethics and Conduct of Respondents
Respondents shall comply with University policies on gifts and gratuities. Respondents shall
exercise reasonable care and diligence to prevent any action or conditions that could result in a
conflict with the University's interest.
N. University of California Terms and Conditions
Appendix A, University of California Terms and Conditions of Purchase, shall be applicable to any
contract award resulting from a future Software Reseller RFP. Additional terms and conditions will
apply if Federal Contract or Grant funds are utilized. Respondents may wish to review these in
advance of any RFP at: http://www.ucop.edu/ucophome/policies/bfb/bus43.html




THE REMAINDER OF THIS PAGE IS INTENTIONALLY LEFT BLANK.




7
          RFI #UCOP-WATT-RFI 2007                                                                              Web Accessibility Testing
                                                                                                                                   Tools




                                            III. Response Signature Page


    RFI NUMBER: UCOP-WATT-RFI 2007
    ISSUE DATE: 11/26/2007
    Response SOLICITED FOR: Web Accessibility Testing Tools
    Response DUE DATE & TIME: 1/11/2008 4:00pm
                             Responses MUST BE RECEIVED ON OR BEFORE THE DUE DATE SHOWN ABOVE.

                                                   LATE RESPONSES WILL NOT BE ACCEPTED.


SUBMIT RFI RESPONSES TO:                                                                   IF FURTHER INFORMATION IS REQUIRED, PLEASE
                                                                                           CONTACT:


Brian N. Agius                                                                             Brian N. Agius
Contract Administrator                                                                     Contract Administrator/UCOP
University of California, Office of the President                                          PH: (510) 987-0271
                      th
1111 Franklin St., 10 Floor                                                                Email: brian.agius@ucop.edu
Oakland, CA 94607


    RESPONDENTS MUST SIGN WHERE INDICATED BELOW AND SUBMIT THIS SHEET AS THE COVER PAGE IN ORDER TO
    VALIDATE THEIR RESPONSE.

    As a supplier of goods and services to the University of California I/we certify that racially segregated facilities will not be maintained nor provided
    for employees at any establishment under my/our control, and that I/we adhere to the principals set forth in Executive Order 11246 and 11375, and
    undertake specifically to maintain employment policies and practices that affirmatively promote equality of opportunity for minority group persons
    and women, to take affirmative steps to hire and promote women and minority group persons at all job levels and in all aspect s of employment, to
    communicate this policy in both English and Spanish to all persons concerned within the company, with outside recruiting services and the minority
    community at large to provide the University on request a breakdown of our total labor force by ethnic group, sex, and job category, and to discuss
    with the University our policies and practices relating to our affirmative action program.


    Company Name and Address


    Signature of company representative


    Printed name of company representative



    Title


    Date


    Tel. No.                                    Fax No.                                           email address




8
                      RFI #UCOP-WATT-RFI 2007                                                    Web Accessibility Testing
                                                                                                                     Tools

                IV. About the University of California


                  A. University of California Employment and Enrollment Summary
                The table below summarizes the ―total enrollment‖ and ―total employees‖ of the University of
                California. Total enrollment figures include all Full- and Part-time students, and both
                Undergraduate and Graduate students. Total employment figures include all Full- and Part-time
                employees.

                       University of California Facts in Brief: Population of Students and Faculty/Staff

            UCD      UCB       UCSF      UCSC      UCM*      UCSB       UCR       UCLA       UCI       UCSD       UCOP       LBNL     TOTAL

Students    30,475   33,933     4,326    15,364     1,286    21,082    16,875     38,218    25,871     26,868                          214,298

                                                                                                                  2,145
Faculty                                                                                                            Plus
            27,568   21,418   20,852      7,414     1,038    10,019      7,240    38,018    16,961     24,677                3,800   178,838***
and Staff                                                                                                        1,488 in
                                                                                                                 DANR**
                *UC Merced opened in Fall 2005
                **DANR = Department of Agriculture and Natural Resources
                *** The Total University Employment figure does not include the employees of Lawrence Berkeley Lab
                Data Sources:
                April 2007 Personnel Tables (view at http://www.ucop.edu/ucophome/uwnews/stat/headcount_fte/apr2007/welcome.html)
                Fall 2006 Statistic Summary of Students and Staff (view at: http://www.ucop.edu/ucophome/uwnews/stat/)
                “About Lawrence Berkeley Lab” (view at: http://www.lbl.gov/LBL-PID/LBL-Overview.html)



                B. University of California’s Commitment to Accessibility:

                The University of California is committed to providing an electronic environment that is accessible
                to everyone, including individuals with disabilities. This currently includes voluntary roll-out of
                standards for web accessibility, consistent with Section 508 of the Rehabilitation Act. (For more
                information, please see: http://www.ucop.edu/irc/itaccessibility/resources/standards.html).




                THE REMAINDER OF THIS PAGE IS INTENTIONALLY LEFT BLANK.




                9
      RFI #UCOP-WATT-RFI 2007                                            Web Accessibility Testing
                                                                                             Tools

V. Anticipated Minimum Requirements
The University anticipates the following to be among the minimum requirements suppliers must
certify they are able to meet or exceed in any future RFP response.


     A. We require a desktop testing tool, which can be used by the individual Web
        developer/designer for a single page or local site.

     B. We require an enterprise testing tool, which can be used to spider through and test entire
        Web domains.

     C. The enterprise tools should allow for the inclusion/exclusion of particular directories.

     D. Tools should be able to test Web-based applications (including ERPs such as
        Oracle/Peoplesoft), in addition to static Web sites, for accessibility.

     E. It should be clear how tools are meant to function: from a Web site, as an extension to a
        browser, as part of a Web authoring tool, or installed on a hard drive or server.

     F. Tools should test the sites against common Web accessibility standards—Section 508 of
        the US Rehabilitation Act and/or Web Content Accessibility Guidelines 1.0 (WCAG 1.0).

     G. The tool should allow the user to select a level of compliance testing (just 508, just
        WCAG priority 1, priorities 1-2, or priorities 1-3; or both 508 and WCAG).

     H. Tools should assess accessibility on a variety of levels, including usability based on
        vision, motor, and aural impairments.

     I.   Tools should check for standards compliance (i.e., HTML, XHTML, CSS, semantic
          markup checks, correct use of embed/object tags) as well as accessibility.

     J. The interface of the tools should be accessible and Section 508 compliant, as
        demonstrated through a completed VPAT:
        http://www.itic.org/archives/articles/20040506/faq_voluntary_product_accessibility_templ
        ate_vpat.php

     K. Tools should be easy to use and well supported.

     L. Tools should issue comprehensive evaluation reports that provide information about
        errors and interactive guidance on correcting them by means of prompts and
        explanations and, where possible, an automatic correction of the source code including
        automatic coding of complex tables.

     M. Enterprise tools should allow for the distribution of reports to site owners or others
        involved in compliance issues.

     N. Tools should have the ability to automatically assess Web sites on a set schedule (daily,
        weekly, etc.)

     O. Tools should save page/site settings for reevaluation.

     P.        Tools needs to have an ability to accept a username and password for testing
          password-protected or other sites that require another method of authentication (UC net
          ID).




10
      RFI #UCOP-WATT-RFI 2007                                           Web Accessibility Testing
                                                                                            Tools

     Q. Tool should be able to assume or ―spoof‖ an IP address specified by the user to access
        domain-restricted sites.

     R. Tools should allow null alt attributes to be defined for images but should identify them as
        empty with a user check. In other words, alt attributes without content should not be
        automatically labeled as errors.

     S. Tools should allow a user distinction between layout and data tables.

     T. Tools should allow a user to specify whether or not Javascript on a given page needs a
        <noscript> element. Some pages with Javascript elements function fine without
        Javascript enabled on the client browser, others don’t. The evaluator should be allowed
        to make the decision but be notified.

     U. Tools should be able to be integrated into content management systems.




THE REMAINDER OF THIS PAGE IS INTENTIONALLY LEFT BLANK.




11
     RFI #UCOP-WATT-RFI 2007                                          Web Accessibility Testing
                                                                                          Tools


VI. RFI Response Section
Respondents are asked to fill in their response within this document in the right-hand column of
the table below. Each row should include the question exactly as it now appears as published
from the University and the respondent’s corresponding answer.

Should additional supporting information or visual representation be required, please refer to and
attach supporting materials in as logical and clear a manner as possible. Any supporting
materials must be included in electronic form together with the RFI response.

DO NOT MODIFY THIS TABLE OR THE ORDER OF YOUR RESPONSES.

Questions                                             Responses
A. Can the tools you offer be used by the
individual web developer/designer for a single
page or local site?
B. Do you offer an enterprise testing tool which
can be used to spider through and test entire
Web domains? If yes, explain in details.

C. Do the enterprise tools you offer allow for
the inclusion/exclusion of particular directories?
If yes, explain in details.
D. Are the tools you offer able to test Web-
based applications (including ERPs), in
addition to static Web sites, for accessibility? If
yes, explain in details.

E. Is it clear how your tools are meant to
function: from a Web site, as an extension to a
browser, as part of a Web authoring tool, or
installed on a hard drive or server? If yes, state
how they are meant to function in details.
F. Do the tools you offer test the sites against
common Web accessibility standards—Section
508 of the US Rehabilitation Act and/or Web
Content Accessibility Guidelines 1.0 (WCAG
1.0)? Explain in details.

G. Do the tools you offer allow the user to
select a level of compliance testing (just 508;
just WCAG priority 1, priorities 1-2, or priorities
1-3; or both 508 and WCAG)? Explain in
details.

H. Do the tools you offer assess accessibility
on a variety of levels, including usability based
on vision, motor, and aural impairments?
Explain in details.
I. Do the tools you offer check for standards
compliance (i.e., HTML, XHTML, CSS,
semantic markup checks, correct use of
embed/object tags) as well as accessibility?
Explain in details.




12
     RFI #UCOP-WATT-RFI 2007                        Web Accessibility Testing
                                                                        Tools

J. Are the interfaces of the tools you offer
Section 508 compliant, as demonstrated
through completion of a VPAT?

K. Are the tools you offer easy to use and well
supported? Explain in details.
L. Do the tools you offer issue comprehensive
evaluation reports that provide information
about errors and interactive guidance on
correcting them? Do they automatically correct
source code, including the code of complex
tables? If yes, attach sample reports to
demonstrate.
M. Do the enterprise tools you offer allow for
the distribution of reports to site owners or
others involved in compliance issues?
N. Do the tools you offer have the ability to
automatically assess Web sites on a set
schedule (daily, weekly etc.)?
O. Can the tools you offer save page/site
settings for reevaluation?
P. Do the tools you offer have the ability to
accept a username and password for testing
password-protected or other sites that require
another method of authentication? Explain in
details.
Q. Can the tool you offer assume or ―spoof‖ an
IP address specified by the user to access
domain-restricted sites?
R. Alt attributes without content should not be
automatically labeled as errors. Do the tools
you offer allow null alt attributes to be defined
for images but identify them as empty with a
user check?
S. Do the tools you offer allow a user
distinction between layout and data tables?
T. Some pages with Javascript elements
function fine without Javascript enabled on the
client browser, others don’t. The evaluator
should be allowed to make the decision but be
notified. Do the tools you offer allow a user to
specify whether or not Javascript on a given
page needs a <noscript> element?
U. Can the tools you offer be integrated into
content management systems?
V. What is your company’s experience in
providing comprehensive and satisfactory web
accessibility products and services in a
university environment?
W. Provide company information including
organization chart, company history, a copy of
the company's annual financial report. In the
event that your company is privately-held,
please provide your requirements for executing
a Non-Disclosure Agreement.



13
     RFI #UCOP-WATT-RFI 2007                       Web Accessibility Testing
                                                                       Tools

X. What other elements or functionalities of the
web accessibility tools would you suggest the
University include in consideration of any
potential RFP?


/end of document




14

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:124
posted:11/25/2011
language:English
pages:13