Note: If you are a vendor and want to learn about the procurement accessibility process, visit the Information for Vendors page.

All Information and Communication Technology (ICT) products and services from third party vendors that are purchased or used at UO must be accessible to people with disabilities. This includes software, online services, multimedia, digital document creation, web development, hardware, and more. Procurements that go through Purchasing and Contracting Services (PCS) follow their accessibility review process before the product is purchased or contract is signed, and products that don't go through PCS (including use of free and/or open source products) can be submitted directly to the Digital Accessibility Architect for review and consultation.

The Procurement Accessibility Guide/FAQ provides an overview of how and why accessibility is included in procurement, and explains what you need to do.

Whenever possible, it's best to include accessibility in the early stages of the procurement process, for example when drafting an RFP or when exploring potential options to purchase. Leaving accessibility until the end of the procurement process makes it more likely that the purchase will be delayed. To avoid issues, submit a Request for Digital Accessibility Procurement Review or contact the Digital Accessibility Architect before you start working with PCS (the earlier, the better).

For any procurement including a contract or agreement, appropriate language regarding accessibility must be included. For procurements going through PCS, this is already integrated into the process.

In some qualifying circumstances, a product or service that is not fully accessible may need to be procured. In those cases, the department responsible for the procurement will be required to have an approved Equally Effective Alternative Access Plan (EEAAP).