75P00120P00168_BASE_SIGNED.pdf

ORDER FOR SUPPLIES OR SERVICES

3. ORDER NO. 4. REQUISITION/REFERENCE NO.

PAGE OF PAGES

5. ISSUING OFFICE (Address correspondence to) b. STREET ADDRESS

IMPORTANT: Mark all packages and papers with contract and/or order numbers. 1

1. DATE OF ORDER 2. CONTRACT NO. (If any) 6. SHIP TO:

a. NAME OF CONSIGNEE

c. CITY d. STATE e. ZIP CODE

7. TO:

a. NAME OF CONTRACTOR

f. SHIP VIA

8. TYPE OF ORDER

b. COMPANY NAME

c. STREET ADDRESS

d. CITY e. STATE f. ZIP CODE

9. ACCOUNTING AND APPROPRIATION DATA

a. PURCHASE b. DELIVERY

REFERENCE YOUR:

Please furnish the following on the terms and conditions specified on both sides of this order and on the attached sheet, if any, including delivery as indicated.

Except for billing instructions on the reverse, this delivery order is subject to instructions contained on this side only of this form and is issued subject to the terms and conditions of the above-numbered contract.

10. REQUISITIONING OFFICE

11. BUSINESS CLASSIFICATION (Check appropriate box(es))

a. SMALL b. OTHER THAN SMALL c. DISADVANTAGED d. WOMEN-OWNED

13. PLACE OF

a. INSPECTION b. ACCEPTANCE

14. GOVERNMENT B/L NO. 15. DELIVER TO F.O.B. POINT

ON OR BEFORE (Date)

16. DISCOUNT TERMS

17. SCHEDULE (See reverse for Rejections)

09/28/2020

75P00120P00168 ACL259082

DHHS/PSC/AMS/DAM

7700 Wisconsin Avenue

8th Floor

Bethesda MD 20814

MICHELLE

MASSACHUSETTS INSTITUTE OF TECHNOLOGY 100706

MASSACHUSETTS INSTITUTE OF TECHNOLO

77 MASSACHUSETTS AVE

CAMBRIDGE MA 021394301

2020.2996007.25102

12. F.O.B. POINT

Administration for Community Living

Administration for Community Living 330 C Street, SW; Room 1318A

Washington DC 20024

DARNELL MARY DELL (ACL)

ITEM NO.

(a)

SUPPLIES OR SERVICES

(b)

QUANTITY

ORDERED

(c)

UNIT

(d)

UNIT

PRICE

(e)

AMOUNT

(f)

QUANTITY

ACCEPTED

(g)

X

X

Destination Destination

Washington DC 20024

f. SERVICE-DISABLED

VETERAN-OWNED

e. HUBZone

g. WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOSB PROGRAM

h. EDWOSB

Tax ID Number: 04-2103594 DUNS Number: 001425594 Web - Based Accessibility Initiative (WAI)

This is a Firm-Fixed Price award

Continued ...

19. GROSS SHIPPING WEIGHT18. SHIPPING POINT 20. INVOICE NO.

21. MAIL INVOICE TO:

a. NAME

b. STREET ADDRESS

(or P.O. Box)

c. CITY d. STATE e. ZIP CODE

SEE BILLING

INSTRUCTIONS

ON REVERSE

17(h)

TOTAL

(Cont.

pages)

17(i)

GRAND

TOTAL

$500,000.00

22. UNITED STATES OF

AMERICA BY (Signature)

23. NAME (Typed)

TITLE: CONTRACTING/ORDERING OFFICER

DAVID D. MORGAN

$500,000.00

OPTIONAL FORM 347 (Rev. 2/2012)

Prescribed by GSA/FAR 48 CFR 53.213(f)

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION NOT USABLE

PSC/FMS

PSC_invoices@psc.hhs.gov

DATE OF ORDER

ORDER FOR SUPPLIES OR SERVICES

SCHEDULE - CONTINUATION

CONTRACT NO.

AMOUNTUNIT

PRICE

UNITQUANTITY

ORDERED

SUPPLIES/SERVICESITEM NO.

IMPORTANT: Mark all packages and papers with contract and/or order numbers.

ORDER NO.

QUANTITY

ACCEPTED

09/28/2020 75P00120P00168

PAGE NO

(a) (b) (c) (d) (e) (f) (g)

For any issues relating to this contract please contract Frank Barnett at frank.barnett@psc.hhs.gov or 301-492-5354

The Contract Officer's Representative (COR) for this award is Mary Darnell at mary.darnell@hhs.gov

Appr. Yr.: 2020 CAN: 2996007 Object Class: 25102

Period of Performance: 09/29/2020 to 09/28/2021

1 Web - Based Accessibility Initiative (WAI) 500,000.00

2 Option 1 0.00

Web - Based Accessibility Initiative (WAI)

Amount: $500,000.00(Option Line Item)

Period of Performance: 09/29/2021 to 09/28/2022

3 Option 2 0.00

Web - Based Accessibility Initiative (WAI)

Amount: $500,000.00(Option Line Item)

Period of Performance: 09/29/2022 to 09/28/2023

4 Option 3 0.00

Web - Based Accessibility Initiative (WAI)

Amount: $500,000.00(Option Line Item)

Period of Performance: 09/29/2023 to 09/28/2024

5 Option 4 0.00

Web - Based Accessibility Initiative (WAI)

Amount: $500,000.00(Option Line Item)

Period of Performance: 09/29/2024 to 09/28/2025

The total amount of award: $2,500,000.00. The obligation for this award is shown in

Continued ...

Prescribed by GSA FAR (48 CFR) 53.213(f)

OPTIONAL FORM 348 (Rev. 4/2006)AUTHORIZED FOR LOCAL REPODUCTION

PREVIOUS EDITION NOT USABLE

TOTAL CARRIED FORWARD TO 1ST PAGE (ITEM 17(H)) $500,000.00

DATE OF ORDER

ORDER FOR SUPPLIES OR SERVICES

SCHEDULE - CONTINUATION

CONTRACT NO.

AMOUNTUNIT

PRICE

UNITQUANTITY

ORDERED

SUPPLIES/SERVICESITEM NO.

IMPORTANT: Mark all packages and papers with contract and/or order numbers.

ORDER NO.

QUANTITY

ACCEPTED

09/28/2020 75P00120P00168

PAGE NO

(a) (b) (c) (d) (e) (f) (g) box 17(i).

Prescribed by GSA FAR (48 CFR) 53.213(f)

OPTIONAL FORM 348 (Rev. 4/2006)AUTHORIZED FOR LOCAL REPODUCTION

PREVIOUS EDITION NOT USABLE

TOTAL CARRIED FORWARD TO 1ST PAGE (ITEM 17(H)) $0.00

SECTION B - Supplies or Services and Prices/Costs

B.1 BRIEF DESCRIPTION OF SERVICES

Web Accessibility Initiative (WAI) Core

B.2 TYPE OF CONTRACT

The contract type awarded is a Firm-Fixed Price Award

B.3 SEVERABLE SERVICES

The services acquired under this contract are severable services. Funds are only available for use for the contract line item (CLIN) to which they are obligated. Unused funds from one CLIN may not rollover for use in other periods.

B.4 CONSIDERATION AND PAYMENT (Fixed Price – Severable Services)

In consideration of satisfactory performance of the work as described throughout this contract, the Contractor shall be paid a fixed price for each CLIN (if exercised). If the options are exercised, funding will be obligated by modification to the contract. The base period and option periods are priced as follows:

Contract Period Fixed Price CLIN 1 Base Period $500,000.00 CLIN 2 Option Period 1 $500,000.00 CLIN 3 Option Period 2 $500,000.00 CLIN 4 Option Period 3 $500,000.00 CLIN 5 Option Period 4 $500,000.00 TOTAL Potential Value inclusive of all

CLINS

$2,500,000.00

SECTION C - Description/Specifications/Statement of Work

Introduction

Essential role and expanding scope of the Web. The World Wide Web is key to full participation in society, and a powerful resource for all. The Web is an essential means of accessing information, news, education, employment, commerce, health care, government services, civic participation, social networking, entertainment, and more. When accessible to people with disabilities, the Web can unlock access to information and interactions that previously were difficult or impossible because of barriers in the built environment, in printed media, in audio and visual information, and in social interactions.

More recently, the Web has taken on an expanded scope, as old and new technologies converge onto the Web as a central infrastructure for reaching billions of users. Most new digital technologies have Web interfaces, whether as a primary or secondary interface. Because of the accessible architecture that we have developed for the Web, we can often ensure that the Web interface is more accessible than other interfaces. Web standards work therefore now encompasses not only the desktop Web, but standards that enable mobile applications, digital publishing, payments, online learning, television and entertainment, Web/Internet of things, automotive, smart cities, augmented and virtual reality, and more. When developers are pushing to get these new technologies out the door, W3C’s role is key in ensuring that accessibility issues are addressed.

Critical need for accessibility. It critical that the Web and the innovative technologies built upon it are inclusive of the millions of people in the United States with disabilities, and the billion people with significant disabilities worldwide. Many disabilities can affect access to, and benefit from, the Web and the technologies built upon it, and can benefit from the use of these technologies. Accessibility of the Web can affect people with auditory, cognitive, physical, neurological, and visual disabilities, and people with combinations of these disabilities.

Accessibility is likewise important to those with accessibility needs due to aging. An accessible Web also benefits people who do not have disabilities but who are experiencing situational barriers such as small screens, low bandwidth, low literacy levels, and language differences.

Impact of accessibility barriers. The complexity and rapid evolution of Web technologies, sometimes still without regard to accessibility, means that people with disabilities frequently encounter barriers when trying to participate in daily activities. Barriers can be simple yet pervasive, for instance lack of alternative text for images, captions for audio, and descriptions for video; or can include more complex barriers such as insufficient programmatic access to dynamic and interactive information generated through content management systems, and lack of interoperability between mainstream browsers or authoring tools on the one hand, and assistive technologies used by some people with disabilities on the other hand. Given the role of the Web in so many life activities, the impact of these barriers on the lives of people with disabilities can be immense. Therefore there is an ongoing need for updated technical and educational support materials that project managers and Web designers and developers can use to address existing and new barriers across the Web, including in the expanded scope of the Web described above.

W3C WAI’s expertise in building accessibility solutions. The World Wide Web Consortium (W3C) is an international community where Member organizations, an expert staff, and the public work together to develop the standards upon which the Web and an increasing number of technologies are based. Founded by Web inventor Tim Berners-Lee, and led by CEO Jeffrey Jaffe, W3C is the international standards body for the Web. W3C has over 400 Member organizations worldwide. W3C uses an open, transparent, and robust standards development process, with opportunities for accessibility review of standards throughout all stages of development.

W3C has hosted the Web Accessibility Initiative (WAI) since 1997. W3C and WAI are both headquartered at MIT’s Computer Science and Artificial Intelligence Lab (CSAIL). Judy Brewer, WAI Director, directs a coordinated set of accessibility activities uniquely feasible within W3C. This includes coordinating accessibility activities among the three other W3C Hosts, in Europe, Japan, and China. This coordinated accessibility program facilitates an international perspective on W3C standards development, international uptake of W3C standards, and coordinated international technical and educational work on accessibility.

W3C WAI objectives and activities in support of an accessible Web.

WAI addresses cross-disability accessibility of the Web and related technologies through a breadth of activities leveraging the unique setting of W3C:

Ensuring that Web standards support accessibility. At any given time, there are more than a hundred technical specifications under development in W3C working groups, and hundreds of W3C Community Groups incubating pre-standardization work. These specifications cover technical needs on the Web, such as support for graphics, media, math, speech, privacy, security, virtual reality, immersive captions, automotive navigation, and application programming interfaces needed for interoperability with screen readers. All need accessibility review to ensure that they enhance rather than become barriers to accessibility;

and all accessibility issues raised must be addressed to the extent possible before a specification can be completed.

Developing accessibility guidelines for Web content and applications, user agents, authoring tools. These guidelines must be carefully developed and vetted by representatives from all stakeholder groups, including industry, disability communities, research, education, and government, to develop consensus solutions. They must address accessibility needs for all disability groups impacted by accessibility barriers in Web-based digital technologies, and tested in diverse industries and applications, ranging from financial sector to the automotive sector. They must be well supported by implementation techniques and supporting explanatory material.

Developing resources to improve the quality and efficiency of Web accessibility evaluation processes and tools. Assessment of Web accessibility is manually intensive, with challenges in inter-rater reliability. WAI activities support improvements in automation of assessment, to increase efficiency of future assessment capabilities.

Development of educational and outreach resources to improve awareness and implementation of Web accessibility. Uptake of Web accessibility depends on an ecosystem of well-vetted, authoritative resources explaining the need for Web accessibility, and providing frequently updated detail on how to implement accessibility guidelines across many different situations.

Coordinating with research and development into new technologies that may impact future accessibility of the Web. As vastly different types of Web technologies emerge, there is a need to track and to promote research regarding accessibility needs and potential barriers in these new technologies. This work includes description of use cases and user scenarios based on this research, to help engineers understand accessibility requirements for the industries and environments that they are designing for.

Promotion of harmonized uptake of accessibility standards and guidance for the Web.

To make progress in Web accessibility, it is important to have unified accessibility standards for the Web, and technologies based upon the Web, so that resources can be used for increasing the uptake and implementation of Web accessibility rather than for developing, maintaining, and updating potentially conflicting sets of guidelines.

Outlook on accessibility needs for the Web and related technologies

Looking ahead to the next five years, there is an increasing number of issues that must be addressed to ensure an accessible Web and related technologies. A defining characteristic of the Web is its ability to grab on to emerging technologies and make them available through the Web infrastructure to billions of users. All too often, without WAI, in the rush to get these technologies out the door there is inattention to accessibility needs. Example areas where WAI has begun to address such emerging technologies include augmented and virtual reality, Web/Internet of things, and emerging needs in industries that are transitioning to a nearly fully digital mode, such as digital publishing. WAI is expanding accessibility guidance for these areas, and exploring how to apply artificial intelligence and machine learning to accelerate development and evaluation of website accessibility.

WAI is positioned to be able to respond in a timely way to the following needs and more:

Develop next generation guidelines for Web accessibility, that are more easily implementable, by a broader range of audiences, and that address the latest Web technologies.

Continue development of technical materials to support implementation of WAI guidelines, including implementation of Section 508 standards.

Expand accessibility guidance for digital technologies that are emerging onto the Web, including guidance tailored to industries that are more recently emerging onto the Web.

Develop more efficient processes for review of mainstream Web standards, including accessibility barrier identification and negotiations to address these barriers when identified during the continually accelerating process of agile standards development, including through further development of the Framework for Accessible Specification of Technologies

(FAST).

Increase automation of tools, and processes for producing accessible content, and in accessibility conformance testing across diverse environments ranging from small to very large websites. For instance, accessibility-supporting authoring tools and practices are needed for STEAM curriculum (Science, Technology, Engineering, Math, and the Arts).

Increase automation of browsers and other user agents in support of transforming inaccessible content to accessible content, without the need for designers and developers to have explicitly followed content accessibility guidelines and techniques.

Increase coverage of accessibility support for the broad range of cognitive disabilities, including the neurodiversity community, wounded warriors including those with traumatic brain injuries, and people with memory impairments.

Leverage AI advances for personalized accessibility support, while also avoiding AI bias in accessibility data training sets and personalized accessibility accommodations.

Expand awareness and educational materials to support awareness of accessibility advances, including broadening outreach to opinion leaders and to more specifically targeted audiences.

Broaden promotion of the benefits of international harmonization of digital accessibility standards, to increase alignment of standards supporting implementation and evaluation resources for accessibility.

Leverage the foundation of accessible Web technologies to support best practices and guidance for accessible remote collaboration, including through accessibility-supported videoconferencing, and where possible for technologies such as online learning, and telemedicine, all of which have become more critical given the current health situation.

W3C WAI work approach in support of these goals and objectives.

WAI work is conducted through W3C structures and W3C Processes, facilitated by staff who are leading accessibility experts in their fields. WAI staff associated with the work described here are based in several locations, and coordinate via a virtual workspace, using a variety of different strategies including teleconferencing and Web-based collaboration spaces. This virtual workspace is supplemented by face-to-face meetings where possible, and otherwise through extended videoconferencing with additional international WAI staff. WAI relies on remote collaboration to facilitate participation in working groups and to leverage contributions from hundreds of accessibility experts, developers and engineers, including representatives of industry, disability organizations, research and government, within the United States and internationally.

Authority.

Title II of the Rehabilitation Act of 1973, as amended, states that NIDILRR is authorized to "...provide for research, demonstration projects, training, and related activities to maximize the full inclusion and integration into society, employment, independent living, family support, and economic and social self-sufficiency of individuals with disabilities of all ages..."

Since WAI was first established in 1997, NIDILRR has supported core WAI activities, sustaining a multi-stakeholder forum that brings together perspectives and contributions from industry, the disability community, research, and government from around the world, to develop consensus-based accessibility solutions for the Web. NIDILRR’s support has been essential in ensuring accessibility of the evolving Web and related digital technologies that are the foundation for accessible Web-based government services, and for access to employment, independent living, family support, and economic and social self-sufficiency of individuals with disabilities.

2. Unique qualifications of W3C WAI to develop Web accessibility solutions, standards, guidelines and resources

The Web Accessibility Initiative (WAI) is uniquely qualified to develop Web accessibility solutions, standards, guidelines, and authoritative supporting resources that the US Department of Health and Human Services, other US federal agencies, industry and the public rely upon for intergovernmental communications and interactions.

The Web Accessibility Initiative (WAI) Core develops standards, guidelines and resources to help make the Web accessible for people with disabilities. WAI is regarded as the authoritative international resource on Web accessibility, and its solutions and resources are used throughout the United States and the world. WAI develops guidelines for accessibility of key Web component, and these guidelines must be updated periodically to keep pace with new Web technologies.

WAI’s activities in support of the goal of an accessible Web include reviewing accessibility issues in Web standards under development, and developing accessibility standards such as Accessible Rich Internet Applications (WAI-ARIA) to address accessibility of the dynamic interactive Web applications that have changed the face of the Web in recent years. WAI develops technical and educational resources to support implementation and conformance evaluation of WAI guidelines, resources that also must be kept updated to support the latest Web development practices. In recent years WAI has been updating its processes as well as the scope of its work to address the latest technologies that are converging onto the Web, and to do so in a way that keeps pace with the increasingly agile development process of the evolving digital technology industry.

The unique qualifications of W3C/WAI to develop Web accessibility solutions, standards, guidelines and resources include the following:

1. Impact on the development of Web technologies from the design stage onwards.

Accessibility of the Web requires support for accessibility in all mainstream Web technologies.

WAI has unique access from the earliest stage onwards to the development of over one hundred W3C technologies. WAI sets requirements for accessibility support across all W3C technologies;

participates as needed with W3C Working Groups in development and negotiation of technology-specific accessibility solutions; and monitors incorporation of support for accessibility into Web technologies.

2. Authoritative status of W3C’s standards and guidelines.

To be able to impact a global information network, accessibility solutions need to have high levels of quality, credibility, and visibility. Being situated within W3C allows WAI’s work on accessibility standards and guidelines to benefit from the cross-technology international expertise within the unique W3C setting, from W3C’s authoritative role in defining standards for the Web, from high visibility in W3C media coverage, and from W3C outreach through W3C international offices and nearly 400 W3C Member organizations.

3. Development of accessibility standards and guidelines that are consistent with the technical architecture and standards for the Web.

To be successfully implemented across the Web, Web accessibility standards and guidelines must be harmonized with the architecture of the Web, compatible and interoperable with other Web standards, and forward-compatible with constantly evolving Web technologies. WAI’s position within W3C uniquely ensures that accessibility solutions are compatible with other Web technologies, so that they are relevant and applicable across the entire Web.

4. Leveraging of technical expertise from W3C staff and W3C Member organizations.

To address the full spectrum of accessibility issues across different Web environments, and to develop and negotiate technically sound solutions to these issues, it is necessary to have access to engineering expertise in the latest Web technologies. WAI’s accessibility solutions are continually informed by and reviewed by hundreds of leading Web technologists from around the world. This ongoing review by Web experts ensures the technical soundness of WAI’s work, and facilitates acceptance of Web accessibility solutions within the Web community.

5. Leveraged implementations in web applications and websites

To make the Web accessible, it is necessary to not only develop accessibility solutions, but also to ensure that these are implemented in products and services successfully. WAI uses the “Candidate Recommendation” stage of the W3C standards process, which requires implementation of a draft standard tested in multiple applications and/or websites before finalization, to leverage development of test suites and implementation experience for WAI standards and guidelines within the Web community and industry, before specifications and guidelines become final standards.

6. A structure and commitment to multi-stakeholder process

Accessibility solutions need to meet the requirements of people with disabilities, but also to meet the requirements of developers and implementers across the Web community, to ensure that accessibility solutions are feasible. W3C’s standards process enables participation by and consensus-building among international representatives of industry, disability organizations, research, government, education, and other stakeholders in Web accessibility who have perspectives and skills to contribute.

7. Transparency and accountability of an open standards process.

To ensure that accessibility solutions are responsive to the needs of government, industry and the user community, accessibility solutions for the Web need to be developed through a transparent and accountable process. WAI develops accessibility standards and guidelines within W3C’s well-documented open standards process, which allows broad public review, and transparency and accountability of comments processing. W3C is also a signatory to the Open Stand Principles.

8. Ability to impact accessibility of technologies that are newly converging onto the Web.

To be able to influence the accessibility of the Web also requires the ability to influence a continually expanding range of technologies, industries, and markets that are converging onto the Web; for instance, mobile, digital publishing, augmentative and virtual reality, television and entertainment, real time communications, automotive, smart cities, and Web of things, all of which are developing Web standards within W3C. Influencing accessibility of new areas of standardization, while presenting a challenge of scale, creates opportunities to map existing accessibility guidance to these new areas, resulting in harmonized accessibility approaches that facilitate industry uptake and implementation.

9. Access to a broad network of standards organizations with which W3C maintains liaisons.

WAI benefits from W3C’s broad circle of liaisons with other technology consortia and standards organizations, which supports dialog on harmonization of Web standards. This network provides WAI an opportunity to promote early awareness of the need for accessibility, and to influence the development of accessibility solutions within additional technologies as they become part of the broader Web community.

10. Ability to respond to emergent issues in technology innovation and uptake, based on a comprehensive foundation of accessible Web infrastructure.

Integration of accessibility considerations into W3C’s standards development process has resulted in a uniquely comprehensive set of accessible technologies which serve as the foundation for today’s information society and economy, and upon which new technology innovations can be developed with confidence that they can support accessibility. One such example is the W3C’s Real Time Communications (RTC) protocol, which provides support for cross-disability accessible communications in remote applications such as emergency communications, videoconferencing, online education, telehealth, and other applications that have become essential in the time of COVID-19.

4. Scope of New WAI-Core Work

The duration of this contract shall be five years. Tasks shall include the following work, in order to enable ongoing improvement of accessibility in mainstream Web technologies; to develop updated accessibility guidance, and technical and educational support materials, to coordinate with emerging standards that may impact on accessibility of the Web; and to report to NIDILRR monthly and annually on working group activities and accessibility issues addressed. The following tasks are uniquely feasible within the Web Accessibility Initiative at the World Wide Web Consortium, headquartered at the Massachusetts Institute of Technology.

Task 1: Review comments on accessibility support in Web standards under development, and develop specifications addressing accessibility gaps

Needs addressed. This task addresses the need to review evolving Web standards, and technologies that are newly emerging onto the Web, in order to identify and address potential accessibility barriers in standards being developed within the international standards body for the Web. These reviews need to ensure consideration for the full range of user needs throughout the development of new standards and technologies, so that accessibility barriers do not arise that could block the use of the Web for education, employment, healthcare, personal and commercial finance, and more. This task addresses the need for accessibility experts to be embedded within W3C to ensure that all new technical specifications for the Web will support accessibility. This task also addresses the need for accessibility reviews in the context of an increasingly “agile” development process, where technical standards are continually being updated, since this approach increases the frequency of requests for accessibility reviews and increases the need for subsequent negotiation of complex accessibility issues identified through this process.

Work approach. The work approach for Task 1 involves providing expert W3C WAI staff support within a working group of Web accessibility experts knowledgeable about the latest Web technologies under development at W3C, and also knowledgeable about the W3C standards development process. These WAI staff support a multi-stakeholder forum of accessibility experts who document a consensus of their expert opinions as input into reviews of Web technologies with accessibility barriers. The W3C Process defines a rigorous system of technical development in Working Groups, vetting by technical organizations and the public, consensus-seeking, and resolution of comments received. Work may also include recruitment of public comments on draft technical reports from W3C Interest Groups and Community Groups, and reviewing this input and incorporating it into the consensus expert opinion.

Review comments may consist of communications to other W3C Working Groups stating that a Web standard or other technical document under development has no accessibility barriers at a given stage in its development; or identification of barriers and suggested approaches for resolving these; or review of one or more approaches suggested by another working group and comments as to whether those approaches do or do not address accessibility barriers previously identified. Review comments may also consist of accessibility perspectives provided within the context of a consensus-oriented discussion between an expert accessibility working group and another W3C working group developing a Web standard; or it may consist of comments on supporting documents relevant for the development of a Web specification, including use cases, requirements documents, implementation guides, and implementation testing reports.

Examples. For instance, media formats must support captioning for people who are deaf or hard of hearing, and audio description for people who are blind or who have low vision. Digital publishing standards must support interactive content needed for educational testing. Privacy and security protocols must support accessible selection and display of user preferences. Real-time communication and television standards must support accessible emergency notifications.

Typically over 100 such standards are under development over the course of a year, and need accessibility reviews by a WAI working group with accessibility expertise in novel technical areas.

Deliverables. Work under Task 1 will include updating documentation of accessibility experts’ guidance on accessibility requirements, specification design consideration, and known gaps, drawing on experience gained from identifying, reviewing, commenting on, and negotiating resolutions to accessibility barriers in a wide range of technologies. This documentation serves as a general introduction to accessibility self-review by other W3C working groups, and facilitates the scaling of accessibility expertise to a larger number of W3C specification reviews, and potentially also to standards developed outside of W3C.As the need arises, work under Task 1 may include development of specifications to address accessibility needs that cannot be addressed in mainstream Web specifications, either because a more coordinated accessibility solution is needed across different technologies and platforms, or because crucial accessibility features cannot receive acceptance in mainstream technologies. An example of the former is Accessible Rich Internet Applications (WAI-ARIA), Specifications currently under development include Core Accessibility Application Programming Interface (API) mappings, and various technology-specific accessibility mappings potentially including, at time of writing, HTML, SVG, and/or digital publishing.

For Task 1, the contractor shall deliver:

Task 1A: Documentation of review comments representing a consensus accessibility expert opinion of potential barriers, and where available suggestions for solutions for identified accessibility barriers in W3C technical specifications and related materials, or reviews of solutions proposed by other W3C groups. Also where available, outcome of the comments offered. Expected number of reviews over the course of a year would be no less than twelve, and frequency may vary.

Task 1B: Updated guidance for ensuring accessibility support in specification design and development. The guidance in the Framework for Accessible Specification of Technologies (FAST) should be expanded as needed to match the scope of emerging technologies addressed as W3C expands.

Task 1C: Where applicable, specifications identifying accessibility gaps in W3C technologies. Since it is generally preferable to integrate accessibility support into mainstream standards, the preferred outcome is therefore a low number of accessibility-specific specifications, so no expected quantity of specifications is set. Drafts and final documents should be submitted to NIDILRR within 45 days of their issue date for inspection and acceptance.

Task 2: Web Accessibility Guidelines and Techniques Needs Addressed. This task addresses the need for development of authoritative guidance and associated technical support materials to keep pace with accessibility requirements for evolving Web standards, and for technologies that are newly emerging onto the Web. It addresses the need for quality, credible, and authoritative accessibility guidance, including guidelines and implementation support materials, for Web content, applications, browsers, mobile applications, digital publishing and more. This task addresses the need for updating guidance on an ongoing basis, to match the pace of technology evolution and innovation; and it addresses the need for guidance that is specific to the roles of different types of audiences, including developers, designers, managers, evaluators, educators, and others. This guidance needs to be closely coordinated with the development of widely accepted mainstream Web standards, and should itself meet a high standard of quality and acceptance among technical organizations and the public.

Examples. Work under Task 2 involves maintaining one or more multi-stakeholder Working Groups of Web accessibility experts, and through these groups, coordinating development of normative and informative guidance for accessibility of Web content and applications, including resolution of issues raised through public comment. This work will involve development of updated guidance and technical support materials on Web content and applications, authoring tools, browsers, mobile applications, and other Web-enabled applications, devices and services.

This guidance may be produced in standalone or modular format including as extensions of previous guidelines, or as combinations of previous guideline; and may include a series of updated and/or expanded implementation techniques and/or implementation reference examples for developers using existing WAI guidelines. Factors in determining the scope and format of the guidance and implementation support materials will include the needs of different developer audiences, and the maturity of accessibility guidance for particular platforms, devices, industries, and/or markets. As needed it may also include more extensive guidance and/or techniques for areas such as cognitive and learning disability, low-vision accessibility, and/or voice input accessibility. It may include normative or non-normative guidance, introduction and overview materials, and implementation reference materials, For Task 2, the contractor shall deliver:

Requirements, working drafts, working group notes, and/or final specifications of accessibility guidance and technical support materials for Web content, authoring tools, browsers, mobile, and technical specifications, to be submitted to NIDILRR within 45 days of their issue date for inspection and acceptance.

Task 3: Educational materials supporting implementation and harmonized uptake of international Web accessibility standards

Needs addressed. This task addresses the need for a broad range of awareness and educational materials to reinforce the importance of digital accessibility as new technologies emerge, and to ensure consideration of accessibility throughout the development process for products and services across the traditional Web as well as for emerging technologies on the Web. It addresses the need for resources appropriate for different communities and industries. This task addresses the continued need to promote unified uptake of accessibility standards, and to ensure internationally harmonized guidance for Web accessibility, in order to accelerate the implementation of accessibility guidance.

Work Approach. Work under Task 3 involves development of education and outreach materials relating to uptake and implementation of Web accessibility standards, and comments on draft standards, regulations, and policies as needed to support harmonized uptake of international accessibility guidelines

For Task 3, the contractor shall deliver:

Educational materials supporting implementation and harmonized uptake of internationally harmonized web accessibility standards, and documentation of liaison discussions with standards organizations and/or regulatory processes as needed to support harmonization of Web accessibility standards and guidelines, for NIDILRR’s inspection and acceptance.

Task 4: Monthly Reporting Task 4 addresses the need for ongoing oversight of WAI activities by NIDILRR. This task involves monthly reports of activities under Tasks 1 and 2, and activity plans for the next reporting period.

For Task 4, the contractor shall:

Submit a monthly report to NIDILRR, including a progress report of activities and accomplishments during the reporting period, by the 15th of the following month. This will include an update on activities under Tasks 1 and 2, and activities planned for the next reporting period, for NIDRR’s inspection and acceptance of contract activities as specified under Tasks 1 and 2.

Task 5: Annual Reporting

Task 5 addresses the need for an annual in-depth report of WAI activities to NIDILRR. This task involves preparation of an annual summary of activities under Tasks 1, 2, and 3.

For Task 5, the contractor shall:

Submit a comprehensive annual report of accomplishments to NIDILRR for inspection and acceptance, by the 52nd week of each annual reporting period. The report shall contain, but not be limited to, summaries of activities and accomplishments for Tasks 1, 2, and 3; WAI home page new items relating to activities of this contract, and lists of presentations relating to this contract.

Task 6: IT Security, Privacy, and Accessibility Task 6 addresses the need for WAI activities to meet or exceed Federal IT security, privacy, and accessibility requirements. This task applies to prior tasks.

For Task 6, the contractor shall:

The Contractor, at the direction of the COR and ACL Chief Information Security Officer (CISO), shall demonstrate that it operates systems and conducts security and privacy assessments in accordance with the Federal Information Security Modernization Act (FISMA), the NIST Cybersecurity Framework, and HHS and ACL policy and guidance. The Contractor shall notify the COR and ACL CISO within 24 hours concerning any loss of data integrity, any unauthorized disclosure of data, or any misuse of data. The contractor shall provide documentations, agreed upon by the COR and the ACL CISO, demonstrating the security and privacy practices it operates under. This is considered a formal deliverable due within (120 or negotiated) days of contract award.

This contract is subject to Section 508 of the Rehabilitation Act (the Act) of 1973 (29 U.S.C.

794d), as amended by the Workforce Investment Act of 1998, and the Architectural and Transportation Barriers Compliance Board (Access Board) Electronic and Information Accessibility Provisions (36 CFR Part 1194). Section 508 of the Act requires that, unless an exception applies, all communications products and services that require a contractor or consultant to produce content in any format that is specifically intended for publication on, or delivery via, a federally owned or federally funded website or intranet permit the following:

(1) Federal employees with disabilities to have access to and use information and data that is comparable to the access and use of information and data by federal employees who are not individuals with disabilities.

(2) Members of the public with disabilities seeking information or services from a federal agency to have access to and use of information and data that is comparable to the access and use of information and data by members of the public who are not individuals with disabilities.

(Note: Information about Section 508 of the Act is available at http://www.section508.gov/. The complete text of Section 508 can be accessed at https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh.)

Accordingly, regardless of format, all web content or communications materials specifically produced for publication on, or delivery via, HHS websites, including text, audio, or video, under this contract shall conform to applicable Section 508 accessibility standards. Remediation of any materials that do not comply with the applicable accessibility standards of 36 CFR Part 1194 as https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh set forth herein shall be the responsibility of the Contractor.

The following Section 508 accessibility standards apply to the content or communications material identified in this SOW or PWS:

• Access to Functionality

• Functional Performance Criteria

• Electronic Content

• Software

• Support Documentation and Services

Consistent with the revised Section 508 rule effective March 21, 2017, ACL requires contractors to use the Web Content Accessibility Guidelines 2.0/2.1 (https://www.w3.org/WAI/standards-guidelines/), and to design and develop digital content and systems for the AA success criteria, conformance to which will meet the current Section 508 criteria for accessibility.

Electronic content must be accessible to HHS acceptance criteria. Checklist for various formats are available at http://508.hhs.gov/, or from the Section 508 Coordinator listed at https://www.hhs.gov/web/section-508/additional-resources/section-508-contacts/index.html.

Materials that are final items for delivery should be accompanied by the appropriate checklist, except upon approval of the Contracting Officer or Representative.

http://508.hhs.gov/ https://www.hhs.gov/web/section-508/additional-resources/section-508-contacts/index.html

SECTION D - Packaging and Marking

D.1 PACKAGING AND MARKING

All deliverables shall be delivered to the Contracting Officer’s Representative (COR) identified in Section G and shall be marked as follows:

1. Name and address of the Contractor;

2. Contract Number;

3. Description of item contained therein; and

4. Consignee's name and address.

D.2 PAYMENT OF POSTAGE AND FEES

All postage and fees related to submitting information including forms, reports, etc. to the Contracting Officer or COR shall be paid by the Contractor.

SECTION E - Inspection and Acceptance

E.1 52.252-2 CLAUSES INCORPORATED BY REFERENCE. (FEB 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es):

http://www.acquisition.gov/far/

E.2 INSPECTION AND ACCEPTANCE

Pursuant to the appropriate inspection clause as provided below, all work described in the statement of work to be delivered under this contract is subject to final inspection and acceptance by an authorized representative of the Government. The authorized representative of the Government is the Government's COR, who is responsible for inspection and acceptance of all services, materials, or supplies to be provided by the contractor.

E.2.1 Inspection and Acceptance Criteria Final inspection and acceptance of all work performed, reports and other deliverables will be performed at the place of delivery by the COR.

E.2.2 General Acceptance Criteria General quality measures, as set forth below, will be applied to each work product received from the Contractor under this Statement of Work.

• Accuracy - Work Products shall be accurate in presentation, technical content, and adherence to accepted elements of style.

• Clarity - Work Products shall be clear and concise. Any/all diagrams shall be easy to understand and be relevant to the supporting narrative.

• Consistency to Requirements - All work products must satisfy the requirements of this

Statement of Work.

• Format - Work Products shall be submitted in electronic copy. The electronic copy must be in a format as indicated in the Deliverables Table.

SECTION F - Deliveries or Performance

F.1 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es):

http://www.acquisition.gov/far/

F.2 PERIOD OF PERFORMANCE – Severable Services

The period of performance shall be for a base period of 12 months with 4-12 month option periods, as follows:

Base Period: 09/29/2020 through 09/28/2021 Option Period 1: 09/29/2021 through 09/28/2022 Option Period 2: 09/29/2022 through 09/28/2023 Option Period 3: 09/29/2023 through 09/28/2024 Option Period 4: 09/29/2024 through 09/28/2025

Option periods may be exercised in accordance with FAR Clause 52.217-9 entitled "Option to Extend the Term of the Contract."

F.3 PLACE OF PERFORMANCE

Work will be performed at the Contractor’s primary place of performance at: TBD, but the contractor is not prohibited from allowing its employees to telework in accordance with the contractor’s policies if the work and required level of performance can be completed successfully in accordance with the contract requirements. The Contractor shall coordinate employee telework in advance with the Contracting Officer’s Representative.

F.4 REPORT(S)/DELIVERABLES AND DELIVERY SCHEDULE

The contractor shall submit all required report(s)/deliverables in accordance with the following schedule: All reports shall reference and cite the contract number.

Task Deliverable Due Date Task 1A Documentation of review comments 30 days after development for each contract year

Task 1B Guidance Updates 30 days after development for each contract year

Task 1C Accessibility Specifications 45 days after development for each contract year Task 2 Accessibility Guidance 45 days after issuance for each contract year Task 3 Educational Materials 45 days after development for each contract year Task 4 Monthly Report 15th day of following month for each contract year Task 5 Annual Report 52nd week of each annual reporting period

F.5 DELIVERY REQUIREMENTS

Pickup and delivery of items under this contract shall be accomplished between the hours of 8:30 a.m. and 4:00 p.m., Monday through Friday unless changed by mutual agreement between the COR and the contractor. No deliveries shall be made on Saturdays, Sundays, and days of government closure or Federal legal holidays found at:

http://www.opm.gov/operating_status_schedules.

SECTION G - Contract Administration Data

G.1 AUTHORITIES OF GOVERNMENT PERSONNEL

Notwithstanding the Contractor's responsibility for total management during the performance of this contract, the administration of this contract will require maximum coordination between the Government and the Contractor. The following individuals will be the Government's points of contact during the performance of this contract:

Contracting Officer Name: David Morgan Address: 7700 Wisconsin Ave, Room 8311B Bethesda, MD 20857 Phone: (301) 492-4655 Email: david.morgan@psc.hhs.gov

All communications pertaining to contractual and/or administrative matters under this contract shall be sent to:

Contract Specialist Name: Frank Barnett Address: 7700 Wisconsin Ave 7120C, Bethesda, MD Phone: 301-492-5354 Email: frank.barnett@psc.hhs.gov

Contracting Officer's Representative Name: Mary Darnell Phone: 202-795-7337 Email: frank.barnett@psc.hhs.gov

Note: The Contracting Officer is the only individual authorized to modify the contract.

G.2 CONTRACTING OFFICER'S REPRESENTATIVE (COR) AUTHORITY

(a) Performance of work under this contract must be subject to the technical direction of the Contracting Officer's Representative identified…