D-RFP_Attach3-SOW_2022-06-17.pdf

STATEMENT OF WORK (SERVICES)

(SOW)

GENERAL INFORMATION

Title of Project:

NCATS Clinical and Translational Science Awards (CTSA) Program: Coordination, Communication and Operations Support (CCOS)

Statement of Need and Purpose:

The purpose of this contract is to provide coordination, communication and operations support to create and promote effective collaboration among CTSA Consortium participants.

Background Information and Objective:

The National Center for Advancing Translational Sciences (NCATS) at the National Institutes of Health (NIH) was established to transform the translational process so that new treatments and cures for disease can be delivered to patients faster. The development and implementation of clinical interventions is a complex, iterative, and time-consuming process that takes years before discoveries in biomedical research result in health benefits for patients and communities. NCATS conducts and supports research in the science of translation to discover the operational principles of the intervention development and dissemination processes, thereby providing the scientific foundation for improvements in translational efficiency that will accelerate the realization of interventions that improve human health. The NCATS Clinical and Translational Science Awards (CTSA) Program is one component of the NCATS Strategic Plan to advance clinical and translational science (CTS); it is designed to develop and implement innovative solutions that will improve the efficiency, quality, and impact of the process for turning observations in the laboratory, clinic, and community into interventions that improve individual and public health.

The CTSA Program is a national consortium of medical research institutions, called ‘hubs’, that collaborate locally and regionally to catalyze innovation in training, research tools and processes to improve the translational research process; it includes other CTSA Program initiatives as well. As one of the largest NIH clinical and translational science programs and an exemplar for team science, NCATS envisions the CTSA Program progressing towards a standards-based, interoperable network in a cloud environment.

From 2011 to 2017, support for the coordinating activities of the national collaborative consortium that comprises the CTSA Program was provided by the CTSA Consortium Coordinating Center (C4) under a grant to Vanderbilt University (U54TR000123). In 2017, the CTSA Program Center for Leading Innovation & Collaboration (CLIC - https://clic-ctsa.org/about/clic) continued the coordinating activities under a grant to the University of Rochester (U24TR002260). CLIC support includes coordination of consortium activities; data coordination services to collect, analyze and transform CTSA Program data into actionable insights that accelerate patient impact; provision of a dynamic ecosystem that supports collaboration and team science across the consortium, including innovative collaboration tools;

transparent communication; and dissemination of information to make the progress and impact of translational science visible to internal and external stakeholders.

NCATS requires a contractor to continue providing the coordination, communication and operations support to create and promote effective collaboration among CTSA Program

ATTACHMENT 3 RFP Number 75N95022R00054 https://clic-ctsa.org/about/clic https://clic-ctsa.org/about/clic participants. Anticipated activities include implementing innovative approaches to the collection, analysis, use and dissemination of various types of data to assess the impact of the CTSA Program; fostering effective communication to support CTSA Program activities; and strengthening collaboration and team science among the participants and stakeholders. The contractor will be expected to work closely with the CTSA Program hubs, centers, external partners, stakeholders, and NIH staff in order to accomplish these goals.

For information technology (IT) related areas, the NCATS Information Technology Resource Branch (ITRB) is responsible for the operating system(s), databases, applications, system architecture, server and the security infrastructure provided and/or hosted by NCATS, while the contractor will be expected to be knowledgeable about and support these tasks and/or responsibilities in collaboration with ITRB as specified in the SOW.

Period of Performance:

The anticipated period of performance is as follows:

Base Period: August 25, 2022 – August 24, 2023 (12 months) Option Period 1: August 25, 2023 – August 24, 2024 (12 months) Option Period 2: August 25, 2024 – August 24, 2025 (12 months) Option Period 3: August 25, 2025 – August 24, 2026 (12 months) Option Period 4: August 25, 2026 – August 24, 2027 (12 months)

SCOPE OF WORK

General Requirements:

Independently and not as an agent of the Government, the Contractor shall furnish all the necessary services, qualified personnel, material, equipment, and facilities, not otherwise provided by the Government as needed to perform the below specific requirements:

Specific Requirements:

Provide coordination and operations support to the CTSA Program through:

1. Collection, analysis, and management of data to assess the impact of the CTSA Program hubs and the CTSA Program Consortium, including:

a. Provide appropriate expertise and leadership for collecting, analyzing, and displaying data related to the strategic management of the CTSA Program.

b. Develop a transparent system to collect, curate, analyze, visualize and archive data from CTSA Program hubs and publicly available resources.

c. Provide a secure method for transmitting raw data files to and from the CTSA Program hubs.

d. Mine publicly available resources for data relevant to CTSA Program participants.

e. Store all data in NCATS cloud environment.

f. Design, implement, analyze, and archive surveys and interviews of CTSA

Program participants with the guidance of NCATS Subject Matter Experts.

ATTACHMENT 3 RFP Number 75N95022R00054

g. Train and provide technical assistance to personnel at the CTSA Program hubs to ensure accurate reporting and quality control of the data.

h. Provide scientific programmatic analyses and reports required for oversight and strategic coordination of the CTSA Program, including stories of CTSA investments and impact for dissemination.

2. Fostering effective communication to support internal CTSA Program activities and engage key external stakeholders, including:

a. Establish and make available a web portal using the established NCATS web environment, for shared communication and dissemination of information which includes both public and restricted access sections. Provide links to other public databases and resources hosting relevant information. Examples of items for posting on the web portal include:

i. News, events, publications and statistics about the CTSA Program;

ii. Activities and information of general interest to all CTSA Program participants and NCATS staff;

iii. Tools, methods, training modules, and best practices for clinical and translational science;

iv. Results of surveys, as directed by NCATS;

v. Available resources (e.g., the NCATS Streamlined, Multisite, Accelerated

Resources for Trials (SMART), such as the IRB Reliance Platform tools);

vi. CTSA Program innovations (e.g., https://clic-ctsa.org/ctsa-program-projects-initiatives) to promote translational science;

vii. Standard operating procedures, policies and resources developed by other members of the CTSA Program.

b. Ensure information on web portal is accurate, timely, and updated.

c. Organize and conduct formal and informal meetings (in-person and/or virtual) of the members of the CTSA Program Consortium and external stakeholders, as appropriate. Responsibilities include operational and logistics support for meetings of steering committees, CTSA Program participants, discussion forums, work groups, consortium groups, task forces and other ad hoc events such as periodic elections.

i. Annual Fall CTSA Program Meeting and Annual Spring CTSA Program Group Meetings (Exception: For the base year of this contract the contractor will only need to conduct the Spring 2023 meeting)

1. In-person

2. Non-federal space

3. Fall: 2-3 days between Oct-Dec annually;

Spring: 2-3 days between Mar-Apr annually

4. 325-400 attendees each meeting

ii. Periodic Meetings for working groups, planning, consortium groups, etc.

1. Virtual/Webinars

2. No space required

3. Monthly, bi-weekly, bi-monthly, quarterly, and ad hoc meetings which average to seventy (70) total meetings per month.

4. 10-200 attendees each meeting

d. Collect information from various stakeholders within the CTSA Program and create, review, and disseminate the CTSA Program Newsletter; content will be pre-approved by NCATS prior to publication.

e. Coordinate and manage all aspects of periodic solicitations such as white papers, consensus documents, announcements, reviews, votes and notifications, for CTSA Program participants.

f. Provide virtual workspace on the established NCATS web environment for CTSA Program discussion forums.

g. Create and disseminate information via social media platforms, including video-based media.

h. Facilitate communication with other key stakeholders that may include, but are not limited to: other NIH institutes, government agencies (e.g., Food and Drug Administration), research organizations (e.g., PCORI), research and disease foundations, the biotechnology or pharmaceutical industry, the research community, patients and families, and patient advocacy groups.

i. Place all relevant activity and project materials into the public domain concordant with governance policies and protocols.

j. Coordinate development of manuscripts describing results, interpretations, and conclusions of CTSA Program activities.

3. Strengthening collaboration and team science, including:

a. Support collaboration efforts to advance the strategic goals of the CTSA

Program.

b. Identify translational science research gaps and disseminate information on translational science successes.

c. Disseminate education and training resources and materials, including workshops, externship offerings, conferences and courses, and provide education and training on their use and application.

4. Final Transition, including:

a. The Contractor shall design and implement an approved Final Transition Plan prior to the expiration of the contract. The Final Transition Plan shall provide for the efficient, orderly and safe transition of contract activities, data systems, documents and other information to the successor contractor or to the Government, without loss of time or interruption to the conduct of ongoing CTSA Program activities.

GOVERNMENT RESPONSIBILITIES

All required deliverables and reports will be inspected for acceptance by the Contracting Officer’s Representative (COR). Specified newsletters and items being posted to the consortium will be reviewed by the COR and subject matter experts (SMEs) as needed.

NCATS will provide the platform for which the contractor will perform web-based activities (hosting website, collecting stories and data from hubs, etc.). The COR will coordinate with the contractor on items in the SOW, as needed/required.

DELIVERY OR DELIVERABLES

See REPORTING REQUIREMENTS below for a description of the following deliverables and reports. In the below table, the term “days” means calendar days:

Item Description Format & Delivery Method Delivery Schedule

(1) Website Development and Milestones

Link and electronic copy of metrics via email to COR

Within 5 days after the end of each quarter

(2) CTSA Groups’ Meetings and Minutes

Link emailed to COR Within 48 hours after each meeting

(3) Newsletter Electronic copy via email to COR First Thursday after the end of each month.

(4) Biannual Program Meeting Plans Electronic copy via email to COR Within 5 days after the end of each month

(5) Social Media Strategy Electronic copy via email to COR Within 90 days after contract award

(6) Technical Writing and Manuscript Coordination Support Activities

Electronic copy via email to COR Within 5 days after the end of each quarter

(7) Survey Strategy and Design Electronic copy via email to COR Within 90 days after contract award and for each survey 10 days prior to survey release

(8) Database of Educational Offering Across the Consortium

Electronic copy via email to COR Within 5 days after the end of each quarter

(9) Plan for Consortium Data for Impact Strategy and Analysis

Electronic copy via email to COR Within 90 days of contract award, and annually on award anniversary date

(10) Consortium Data for Impact Strategy and Analysis Report

Electronic copy via email to COR Within 5 days after the end of each quarter

(11) Survey Results and Storage Electronic copy via email to COR Within 10 days prior to survey results being posted

(12) Report of Discussion Forum Activity

Electronic copy via email to COR Within 5 days after the end of each quarter

(13) Ad Hoc Meetings/Workshop Plan Electronic copy via email to COR Within 90 days of contract award and annually on award anniversary date

(14) Meeting Report Electronic copy via email to COR Within 30 days after each meeting

(15) Other Consortium-wide Activities Report

Electronic copy via email to COR Within 90 days of contract award and updated quarterly

(16) Monthly Progress Report Electronic copy via email to COR Within 5 days after the end of each reporting period

(17) Annual Progress Report Electronic copy via email to COR Annually within 5 days after award anniversary date

(18) Final Report Electronic copy via email to COR Due by contract expiration date

REPORTING REQUIREMENTS

All reports required herein shall be submitted in electronic format. All electronic reports submitted shall be compliant with Section 508 of the Rehabilitation Act of 1973. Additional information about testing documents for Section 508 compliance, including guidance and specific checklists, by application, can be found at: http://www.hhs.gov/web/508/index.html under "Making Files Accessible."

1) Website Development and Milestones: A website that not only communicates consortium activities, but will be used to intake information from the hubs, manage registrations, and other consortium activities in a bi-directional way. As the website is developed,we expect milestones to be completed to meet our designated timeline.

2) CTSA Groups’ Meetings and Minutes: There are a number of consortium groups that meet bi-weekly, monthly, bi-monthly, quarterly, annually, and it is expected that these meetings will be run by the contractor and minutes will be posted online in a timely fashion and reported to the COR according to the reporting requirements.

3) Newsletter: A monthly newsletter reporting out important activities from the consortium and NCATS. This is a cross-cutting newsletter that includes all of the consortium.

4) Biannual Program Meeting Plans: There are two program meetings hosted each year, and the meeting planning begins after the other ends, or before. The contractor is http://www.hhs.gov/web/508/index.html expected to manage these meeting planning and be actively engaged in the planning process.

5) Social Media Strategy: A strategy for how the contractor will use social media to share CTSA Program stories, highlights, and activities to keep the public and the consortium engaged, and measure uptake of strategies.

6) Technical Writing and Manuscript Coordination Support Activities: Any publication support to working groups, or other consortium groups should be reported according to the schedule above.

7) Survey Strategy and Design: The contractor will be asked to collect information from the consortium ad hoc and an experienced survey designer is expected to be available to provide a strategy for needed support for the most succinct survey to prevent multiple surveys or unnecessarily long surveys.

8) Database of Educational Offering Across the Consortium: Maintenance of the educational offerings the CTSA Program has built and offers to consortium or the public.

9) Plan for Consortium Data for Impact Strategy and Analysis: Plan for data collection, data analysis, results, and reporting of consortium wide activities and information to evaluate impact from publicly available and other sources.

10) Consortium Data for Impact Strategy and Analysis Report: Data collection, data analysis, results, and reporting of consortium wide activities and information to evaluate impact from publicly available and other sources (e.g., RePORTER, surveys, Clinical Trials.gov).

11) Survey Results and Storage: Survey results are expected to be returned to the those surveyed and the results stored for NCATS and CTSA Program future planning.

12) Report of Discussion Forum Activity: Discussion forums are a primary way the consortium uses asynchronous communication. A report on the DF activity is expected according to the schedule above.

13) Ad Hoc Meetings/Workshop Plan: The consortium activities vary and some times ad hoc groups come up to solve a roadblock or workshops are hosted. The contractor shall host and engage in the planning of these activities with a report to the COR as above.

14) Meeting Report: A report of the bi-annual meetings is expected as above.

15) Other Consortium-wide Activities Report: The CTSA Program is a cross-cutting, dynamic program and in order to stay aware of activities as they go on, the contractor is expected to be report on activities of interest to NCATS.

16) Monthly Progress Report: The Monthly Progress Report shall include a description of the activities during the reporting period, and the activities planned for the ensuing reporting period. The first reporting period consists of the first full month of performance plus any fractional part of the initial month. Thereafter, the reporting period shall consist of each calendar month. The report is due on or before the 15th of the month following each reporting period. The report must also include the following sections:

a. Introduction: A section covering the purpose and scope of the contract effort.

b. Progress report: A section describing overall progress for each task or segment of work listed in the Statement of Work on which effort was expended during the reporting period.

c. Personnel changes: A section covering any changes in personnel.

d. Problems and solutions: A section describing technical or performance problems encountered and corrective action taken. An explanation of any differences between planned and actual progress shall be included.

As part of your monthly report, the following stand-alone reports shall also be submitted when applicable:

e. Proposed revisions to the Project Management Plan

f. Proposed Web Portal posting

g. Proposed Consortium information for transfer to the public domain

h. Proposed CTSA Program Surveys

i. Proposed CTSA Program Newsletter publications topics? (not a draft)

j. Proposed revisions to the Transition Plan

k. Summary of meetings, collaborations, and other communications supported

l. Updates to database of educational offerings across the consortium

m. Any Technical Writing Support provided

n. Report of manuscript coordination activities

o. Consortium Data collection and analysis Reports

p. Report of stories collated

q. Social media summary

r. Updates to website

A Monthly Progress Report shall not be due when the Annual Progress Report is due.

17) Annual Progress Report: On or before the anniversary date of the contract, the Contractor shall submit an Annual Progress Report. This report includes a summation of the results of the entire contract work for the period covered. This report shall include all of the sections provided in the Monthly Progress Report, an additional section to summarize all work conducted during the reporting period, and a section to address the anticipated work plan and budget for the coming year. An Annual Progress Report will not be required for the period when the Final Report is due.

18) Final Report: On or before the expiration date of the contract, the Contractor shall submit a comprehensive Final Report. This report is to include a summation of the work performed and the results obtained for the entire contract period of performance. This report shall be in sufficient detail to describe comprehensively the results achieved. A draft of this report is due sixty (60) days prior to the Final Report.

OTHER CONSIDERATIONS

Travel:

Travel to at least one annual meeting of the CTSA Consortium by required number of contractors to perform meeting management duties for the Fall and Spring meetings in the Washington, DC Metro area for 2-3 days.

Key Personnel:

Principal Investigator: PhD, MPH, MBA, and/or PMP: Will provide overall leadership and direction for the contract team. Experience with oversight of large consortium contracts is required.

Project Manager: MPH, MBA, and/or PMP: Will oversee day-to-day operations and ensure activities are within scope, on budget, and on time. Experience with managing large consortium operations contracts is required.

Publications and Publicity:

Contractor will not write and publish articles with original data.

IT Accessibility Requirements

Section 508 of the Rehabilitation Act, as amended by the Workforce Investment Act of 1998 (P.L. 105-220) requires that when Federal agencies develop, procure, maintain, or use information and communication technology (ICT), it shall be accessible to people with disabilities. Federal employees and members of the public who have disabilities must have access to, and use of, information and data that is comparable to people without disabilities.

1. Products, platforms and services delivered as part of this work statement that are ICT, or contain ICT, must conform to the Revised 508 Standards, which are located at 36 C.F.R. § 1194.1 & Apps. A, C & D, and available at https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines

Item that contains ICT:

Electronic Content

Coordination Center Website

Technical Criteria:

• E205.1 General - Electronic content shall comply with E205.

• E205.2 Public Facing - Electronic content that is public facing shall conform to the accessibility requirements specified in E205.4.

• 602 Support Documentation -

• 603 Support Services -

• 302 Functional Performance Criteria -

Software

Survey software

Technical Criteria:

• E207.1 General - Where components of ICT are software and transmit information or have a user interface, such components shall conform to E207 and the requirements in Chapter 5

• E207.2 WCAG Conformance - User interface components, as well as the content of platforms and applications, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

ATTACHMENT 3 RFP Number 75N95022R00054 https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines http://app.buyaccessible.gov/ict-accessibility#e205_1_general http://app.buyaccessible.gov/ict-accessibility#e205_2_public_facing http://app.buyaccessible.gov/ict-accessibility#602__603__302 http://app.buyaccessible.gov/ict-accessibility#602__603__302 http://app.buyaccessible.gov/ict-accessibility#602__603__302 http://app.buyaccessible.gov/ict-accessibility#e207_1__e207_2__e207_2_1__e207_3 http://app.buyaccessible.gov/ict-accessibility#e207_1__e207_2__e207_2_1__e207_3

• E207.2.1 Word Substitution - When Applying WCAG to Non-Web Software For non-Web software, wherever the term “Web page” or “page” appears in WCAG 2.0 Level A and AA Success Criteria and Conformance Requirements, the term “software” shall be substituted for the terms “Web page” and “page”. In addition, in Success Criterion in 1.4.2, the phrase “in software” shall be substituted for the phrase “on a Web page.”

• E207.3 Complete Process for Non-Web Software - Where non-Web software requires multiple steps to accomplish an activity, all software related to the activity to be accomplished shall conform to WCAG 2.0 as specified in E207.2.

• E504.1 General - Where an application is an authoring tool, the application shall conform to 504 to the extent that information required for accessibility is supported by the destination format.

• E504.2 Content Creation or Editing - Authoring tools shall provide a mode of operation to create or edit content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) for all supported features and, as applicable, to file formats supported by the authoring tool. Authoring tools shall permit authors the option of overriding information required for accessibility.

• E504.2.1 Preservation of Information Provided for Accessibility in Format Conversion - Authoring tools shall, when converting content from one format to another or saving content in multiple formats, preserve the information required for accessibility to the extent that the information is supported by the destination format.

Exceptions:

• E501.1 Scope - Where Web applications do not have access to platform accessibility services and do not include components that have access to platform accessibility services, they shall not be required to conform to 502 or 503 provided that they conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

ICT Support and Services

Documentation

Technical Criteria:

• E208.1 General - Where an agency provides support documentation or services for ICT, such documentation and services shall conform to the requirements in Chapter 6.

• E601.1 Scope - The technical requirements in Chapter 6 shall apply to ICT support documentation and services where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

• E602.1 General - Documentation that supports the use of ICT shall conform to 602.

• E602.2 Accessibility and Compatibility Features - Documentation shall list and explain how to use the accessibility and compatibility features required by Chapters 4 and 5. Documentation shall include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

ATTACHMENT 3 RFP Number 75N95022R00054 http://app.buyaccessible.gov/ict-accessibility#e207_1__e207_2__e207_2_1__e207_3 http://app.buyaccessible.gov/ict-accessibility#e207_1__e207_2__e207_2_1__e207_3 http://app.buyaccessible.gov/ict-accessibility#e504_1__e504_2__e504_2_1 http://app.buyaccessible.gov/ict-accessibility#e504_1__e504_2__e504_2_1 http://app.buyaccessible.gov/ict-accessibility#e504_1__e504_2__e504_2_1 http://app.buyaccessible.gov/ict-accessibility#e501_1_scope_exception http://app.buyaccessible.gov/ict-accessibility#e208_1_general http://app.buyaccessible.gov/ict-accessibility#e208_1_general http://app.buyaccessible.gov/ict-accessibility#e602_1_general http://app.buyaccessible.gov/ict-accessibility#e602_1_general

• E602.3 Electronic Support Documentation - Documentation in electronic format, including Web-based self-service support, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

• E602.4 Alternate Formats for Non-Electronic Support Documentation - Where support documentation is only provided in non-electronic formats, alternate formats usable by individuals with disabilities shall be provided upon request.

• E602.3 Electronic Support Documentation - Documentation in electronic format, including Web-based self-service support, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

• E602.4 Alternate Formats for Non-Electronic Support Documentation - Where support documentation is only provided in non-electronic formats, alternate formats usable by individuals with disabilities shall be provided upon request.

• E603.1 General - ICT support services including, but not limited to, help desks, call centers, training services, and automated self-service technical support, shall conform to 603.

• E603.2 Information on Accessibility and Compatibility Features - ICT support services shall include information on the accessibility and compatibility features required by 602.2.

• E603.3 Accommodation of Communication Needs - Support services shall be provided directly to the user or through a referral to a point of contact. Such ICT support services shall accommodate the communication needs of individuals with disabilities.

Functional Performance Criteria:

• 301.1 Scope - The requirements of Chapter 3 shall apply to ICT where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

• 302.1 Without Vision - Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.

• 302.2 With Limited Vision - Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision.

• 302.3 Without Perception of Color - Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color.

• 302.4 Without Hearing - Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.

• 302.5 With Limited Hearing - Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing.

• 302.6 Without Speech - Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.

• 302.7 With Limited Manipulation - Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations.

• 302.8 With Limited Reach and Strength - Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength.

• 302.9 With Limited Language, Cognitive, and Learning Abilities - ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.

ATTACHMENT 3 RFP Number 75N95022R00054 http://app.buyaccessible.gov/ict-accessibility#e602_1_general http://app.buyaccessible.gov/ict-accessibility#e602_1_general http://app.buyaccessible.gov/ict-accessibility#e602_3__e602_4 http://app.buyaccessible.gov/ict-accessibility#e602_3__e602_4 http://app.buyaccessible.gov/ict-accessibility#e603_1__e603_2__e603_3 http://app.buyaccessible.gov/ict-accessibility#e603_1__e603_2__e603_3 http://app.buyaccessible.gov/ict-accessibility#e603_1__e603_2__e603_3 https://buyaccessible.gov/ict-accessibility#e301_1 https://buyaccessible.gov/ict-accessibility#e302_1 https://buyaccessible.gov/ict-accessibility#e302_1 https://buyaccessible.gov/ict-accessibility#e302_1 https://buyaccessible.gov/ict-accessibility#e302_1 https://buyaccessible.gov/ict-accessibility#e302_1 https://buyaccessible.gov/ict-accessibility#e302_1 https://buyaccessible.gov/ict-accessibility#e302_1 https://buyaccessible.gov/ict-accessibility#e302_1 https://buyaccessible.gov/ict-accessibility#e302_1

Applicable Functional Performance Criteria: All functional performance criteria apply when using an alternative design or technology that achieves substantially equivalent or greater accessibility and usability by individuals with disabilities, than would be provided by conformance to one or more of the requirements in Chapters 4-6 of the Revised 508 Standards, or when Chapters 4-6 do not address one or more functions of ICT.

Applicable requirements for software features and components: All WCAG Level AA Success Criteria, 502 Interoperability with Assistive Technology, 503 Application

Applicable requirements for hardware features and components: All requirements apply

Applicable support services and documentation: All requirements apply

Functional Performance Criteria: